sdworx.
Guides and Resources
Connection Setup Guide
Step-by-step instructions to connect your SD Worx account to Kombo.
How to find your standard employees
Additional documentation and guides for SD Worx.
Supported Features & Coverage
Legal Entities
Legal Entities
SD Worx differentiates between companies and organizations. This integration only maps companies and does not interact with organizations in any way. If you need to access organization data, please contact the support team.
| 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 | |
| nationality | |
| display_full_name | |
| job_title | |
| work_email | SD Worx provides a list of email addresses for each employee, but does not provide a way to distinguish between personal and work email addresses. We only use the first one. |
| mobile_phone_number | SD Worx provides a list of phone numbers for each employee, but we only use the first one. |
| ssn | SD Worx provides a citizen service number for each employee, which can be roughly mapped to social security number or tax id. |
| tax_id | SD Worx provides a citizen service number for each employee, which can be roughly mapped to social security number or tax id. |
| gender | |
| marital_status | |
| employment_status | SD Worx does not provide a uniform way to query employment status. This integration assumes that all employees that are not currently employed are INACTIVE. |
| employment_type | SD Worx does not provide a uniform employment type. All employees in a fixed working contract with more than 32 hours per week are considered FULL_TIME. All employees with a contract with a defined duration are considered as CONTRACT employees. |
| weekly_hours | |
| work_location_id | |
| legal_entity_id | |
| manager_id | |
| home_address | |
| bank_accounts | |
| date_of_birth | |
| start_date | |
| termination_date | |
| custom_fields | |
| integration_fields | |
| remote_data |
Employments
Employments
| Field | Notes |
|---|---|
| id | |
| remote_id | Our system uses SD Worx’ employment history resource to generate employments. As this is generated on the fly by SD Worx, the remote_id is not stable and can change between runs. We use a compound key to ensure that the employment is upserted correctly. |
| changed_at | |
| remote_deleted_at | |
| employee_id | |
| job_title | |
| pay_rate | |
| pay_period | |
| employment_type | SD Worx does not provide a uniform employment type. All employees in a fixed working contract with more than 32 hours per week are considered FULL_TIME. All employees with a contract with a defined duration are considered as CONTRACT employees. |
| pay_currency | SD Worx does not provide a pay currency for employees. EUR is assumed for all employees |
| effective_date |
Groups
Groups
SD Worx’ Group resource is mapped as Kombo Teams SD Worx does not support getting cost centers without having access to companies. The legal entities scope must therefore be enabled to sync cost centers.
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| type | |
| remote_data |
Employee Document Categories
Employee Document Categories
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| remote_data |
Employee <> Group
Employee <> Group
SD Worx provides employee group associations through CurrentEmployment.DepartmentId, CurrentEmployment.CostCenterId, and ParticipantInGroups. Note that ParticipantInGroups requires additional permissions (GroupParticipant GET) and may not be available in all accounts.
| Field | Notes |
|---|---|
| employee_id | |
| team_id | |
| id | |
| changed_at | |
| remote_deleted_at |