Available Connectors
workforce.com HRIS Integration
workforce.com connector for Kombo’s HRIS API
This connector is in open beta. You can freely enable it in your account.
The workforce.com HRIS integration allows you to sync HRIS data between workforce.com and your application through Kombo’s unified API. The tool slug for this connector is workforcecom.
Guides and Resources
Supported Features & Coverage
Work Locations
Work Locations
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| address | |
| remote_data |
Employees
Employees
Only the primary employment’s work location is exposed via Kombo’s API. Workforce.com does not differentiate between the employee’s “work_email” and “personal_email”
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| employee_number | |
| first_name | |
| last_name | |
| display_full_name | |
| job_title | |
| work_email | |
| personal_email | |
| mobile_phone_number | |
| tax_id | |
| gender | |
| employment_status | |
| employment_type | When the employment type field is unavailable, the system uses fallback logic: If a yearly salary is provided, the type defaults to ‘FULL_TIME’; If an hourly rate is provided, it defaults to ‘CONTRACT’. |
| weekly_hours | |
| avatar | |
| work_location_id | |
| home_address | |
| bank_accounts | |
| date_of_birth | |
| start_date | |
| termination_date | |
| remote_created_at | |
| custom_fields | |
| integration_fields | |
| remote_data |
Employments
Employments
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| employee_id | |
| pay_rate | |
| pay_period | |
| employment_type | |
| effective_date | |
| remote_data | |
| custom_fields | |
| integration_fields |
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 |
Work Locations
Work Locations
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| address | |
| remote_data |
Employees
Employees
Only the primary employment’s work location is exposed via Kombo’s API. Workforce.com does not differentiate between the employee’s “work_email” and “personal_email”
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| employee_number | |
| first_name | |
| last_name | |
| display_full_name | |
| job_title | |
| work_email | |
| personal_email | |
| mobile_phone_number | |
| tax_id | |
| gender | |
| employment_status | |
| employment_type | When the employment type field is unavailable, the system uses fallback logic: If a yearly salary is provided, the type defaults to ‘FULL_TIME’; If an hourly rate is provided, it defaults to ‘CONTRACT’. |
| weekly_hours | |
| avatar | |
| work_location_id | |
| home_address | |
| bank_accounts | |
| date_of_birth | |
| start_date | |
| termination_date | |
| remote_created_at | |
| custom_fields | |
| integration_fields | |
| remote_data |
Employments
Employments
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| employee_id | |
| pay_rate | |
| pay_period | |
| employment_type | |
| effective_date | |
| remote_data | |
| custom_fields | |
| integration_fields |
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 |
| Feature | Notes |
|---|---|
| Connection Guide | |
| OAuth | |
| API Passthrough | |
| Group Types | |
| TEAM | |
| Custom Field Explorer | |
| Employees |