Available Connectors
Gusto HRIS Integration
Gusto connector for Kombo’s HRIS API
This connector requires a partnership with Gusto. Please contact us to get access.
The Gusto HRIS integration allows you to sync HRIS data between Gusto and your application through Kombo’s unified API. The tool slug for this connector is gusto
.
Supported Features & Coverage
Legal Entities
Legal Entities
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Work Locations
Work Locations
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Employees
Employees
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_number | |
first_name | |
last_name | |
job_title | |
work_email | |
personal_email | |
mobile_phone_number | |
employment_status | |
employment_type | |
work_location_id | |
legal_entity_id | |
manager_id | |
home_address | |
date_of_birth | |
start_date | |
termination_date | |
custom_fields | |
integration_fields | |
remote_data |
Employments
Employments
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_id | |
job_title | |
pay_rate | |
pay_period | |
employment_type | |
effective_date |
Groups
Groups
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
type | |
remote_data |
Employee <> Group
Employee <> Group
Field | Notes |
---|---|
employee_id | |
team_id | |
id | |
changed_at | |
remote_deleted_at |
Legal Entities
Legal Entities
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Work Locations
Work Locations
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Employees
Employees
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_number | |
first_name | |
last_name | |
job_title | |
work_email | |
personal_email | |
mobile_phone_number | |
employment_status | |
employment_type | |
work_location_id | |
legal_entity_id | |
manager_id | |
home_address | |
date_of_birth | |
start_date | |
termination_date | |
custom_fields | |
integration_fields | |
remote_data |
Employments
Employments
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_id | |
job_title | |
pay_rate | |
pay_period | |
employment_type | |
effective_date |
Groups
Groups
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
type | |
remote_data |
Employee <> Group
Employee <> Group
Field | Notes |
---|---|
employee_id | |
team_id | |
id | |
changed_at | |
remote_deleted_at |
Create employee
Create employee
Gusto requires a personal email address to create an employee. This personal email address needs to be submitted through the
work_email
field. Gusto requires an input for which company to add an employee to. Most instances we see have just one company. We will default to the first company we find if legal_entity_id
is not provided in the request body.Input Field | Notes |
---|---|
first_name | |
last_name | |
work_email | |
gender | |
job_title | |
home_address.street_1 | |
home_address.city | |
home_address.zip_code | |
home_address.country | |
date_of_birth | |
start_date | |
legal_entity_id |
Feature | Notes |
---|---|
OAuth | |
Group Types | |
DEPARTMENT |