SD Worx HRIS Integration

The SD Worx HRIS integration allows you to sync HRIS data between SD Worx and your application through Kombo’s unified API. The tool slug for this connector is 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

Models
Actions
Features
Create Employee with Form

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

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
address
remote_data

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

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

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

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

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

Create employee (v2)

For detailed information about creating employees with form, please see the Create Employee with Form tab above.

Input Field	Notes
staffing_entity_id
properties

Add document to employee

Input Field	Notes
employee_id
category_id
document.name
document.data_url
document.data

Feature	Notes
API Passthrough
Scope Testing
Per Model Tests
Connection Guide
Group Types
TEAM
DEPARTMENT
COST_CENTER

Some required form fields are referencing the following data models:

Groups

Additionally, there are some optional form fields that reference:

Legal Entities

Consider enabling these in your scope configuration.

date

required

Start Date
Start date of the employee. Also considered to be the hire date
Unified field: start_date

single_select

required

Organization

text

Person Number
The person number of the employee.

text

Citizen Service Number
The citizen service number of the employee. Use 0 to apply the next available number

text

The initials of the employee.

text

The prefixes of the employee.

text

Last Name
The last name of the employee
Unified field: last_name

text

First Name
The first name of the employee
Unified field: first_name

text

The nickname of the employee.

single_select

date

Date of Birth
The employee’s date of birth
Unified field: date_of_birth

text

required

Work Email
The email address of the employee
Unified field: work_email

single_select

required

Department
References /v1/hris/groups?types=DEPARTMENT

single_select

required

Function

number

required

Standard Employee
The number of the standard employee to use in SD Worx’ New Person workflow. You can find this in the ‘Manage default person’ task of the organization you want to create the employee in. Take a look at the guide here https://help.kombo.dev/hc/en-us/articles/35481610928785-SD-Worx-How-do-I-find-the-Standard-Employees-Default-Persons

single_select

Company
References /v1/hris/legal-entities?remote_model=legal_entity

General

Features

Guides

HRIS API Reference

Payroll API Reference

General API Reference

DATEV

SD Worx HRIS Integration

Guides and Resources

Connection Setup Guide

How to find your standard employees

Supported Features & Coverage

​Guides and Resources

Connection Setup Guide

How to find your standard employees

​Supported Features & Coverage

Guides and Resources

Supported Features & Coverage