> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# SAP SuccessFactors HRIS Integration
> SAP SuccessFactors connector for Kombo's HRIS API
The SAP SuccessFactors HRIS integration allows you to sync HRIS data between SAP SuccessFactors and your application through Kombo's unified API. The tool slug for this connector is `successfactors`.
## Guides and Resources
Step-by-step instructions to connect your SAP SuccessFactors account to Kombo.
## Supported Features & Coverage
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| address | |
| remote\_data | |
Only one home address is mapped. If preferred address type is set in integration settings, we use that type; otherwise the first address is used. For employees with multiple managers, we only expose the first one. We only support employment\_status ACTIVE and INACTIVE because other values can be complicated to find out (due to multiple employments etc.).
| 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 | |
| ssn | |
| gender | |
| ethnicity | |
| marital\_status | |
| employment\_status | |
| employment\_type | |
| weekly\_hours | |
| work\_location\_id | |
| legal\_entity\_id | |
| manager\_id | |
| home\_address | |
| bank\_accounts | |
| date\_of\_birth | |
| start\_date | |
| termination\_date | |
| remote\_created\_at | |
| custom\_fields | |
| integration\_fields | |
| remote\_data | |
| Field | Notes |
| ----------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| unit | |
| exact\_times\_supported | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| employee\_id | |
| start\_date | |
| end\_date | |
| start\_time | |
| end\_time | |
| amount | |
| unit | |
| status | |
| employee\_note | |
| type\_id | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| employee\_id | |
| job\_title | |
| pay\_rate | |
| pay\_period | |
| employment\_type | |
| pay\_currency | |
| effective\_date | |
| remote\_data | |
| custom\_fields | |
| integration\_fields | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| type | |
| parent\_id | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| employee\_id | |
| type\_id | |
| balance | |
| balance\_unit | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| employee\_id | |
| started\_at | |
| ended\_at | |
| timezone | |
| payable\_hours | |
| approval\_status | |
| comment | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| review\_cycle\_id | |
| reviewee\_id | |
| reviewer\_id | |
| type | |
| summary\_comment | |
| summary\_rating | |
| remote\_data | |
The we treat the form template as a performance review cycle.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| employee\_id | |
| team\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
Setting the approvalStatus might not be working consistently
| Input Field | Notes |
| ----------------- | ----- |
| employee\_id | |
| absence\_type\_id | |
| status | |
| start\_date | |
| end\_date | |
| start\_time | |
| end\_time | |
| Input Field | Notes |
| ----------- | ----- |
| absence\_id | |
SuccessFactors requires a native preferred language. We strive to find the best match, although it may not always be accurate. We will map the nationality into the country of birth.
| Input Field | Notes |
| --------------------- | ----- |
| first\_name | |
| last\_name | |
| work\_email | |
| gender | |
| date\_of\_birth | |
| mobile\_phone\_number | |
| nationality | |
| start\_date | |
For detailed information about [creating employees with form](/hris/implementation-guide/create-employee), please see the [**Create Employee with Form** tab](#create-employee-with-form) above.
| Input Field | Notes |
| -------------------- | ----- |
| staffing\_entity\_id | |
| properties | |
| Feature | Notes |
| --------------------- | ----- |
| Connection Guide | |
| Prerequisites | |
| Create credentials | |
| API Passthrough | |
| Additional Scopes | |
| Scope Testing | |
| Delta Syncs | |
| Group Types | |
| DEPARTMENT | |
| COST\_CENTER | |
| Custom Field Explorer | |
| Employees | |
It's possible when creating an employee, that it's a partial success, meaning some data might not be created or updated correctly. If this happens, you can use the Person ID to update the employee later with the form.
Some **optional** form fields are referencing the following data models:
* Employees
Consider enabling these in your [scope configuration](/hris/features/scopes).
**Person ID**
This is the ID of the person in SuccessFactors. Only provide this when updating an existing employee. Leave blank to create a new employee.
**User**
**First Name**
The first name of the employee
Unified field: `first_name`
**Last Name**
The last name of the employee
Unified field: `last_name`
**Work Email**
The work email address of the employee
Unified field: `work_email`
**Mobile Phone Number**
The mobile phone number of the employee
Unified field: `mobile_phone_number`
**Manager**
The manager of the employee
References `/v1/hris/employees?remote_model=employee`
**Person**
This entity contains the non-effective-dated biographical information such as date of birth, country of birth. It is commonly used as the main entity when doing employee master extracts.
**Country Of Birth**
**Special Date**
**Nick Name**
**Date Of Birth**
Unified field: `date_of_birth`
**Region Of Birth**
**Employment**
Contains all the employment related information for an employee.
**Benefits Eligibility Start Date**
**Change Reason**
**Test Custon Field**
**Eligible for Stock**
**Employee's First Employment**
**First Date Worked**
**Initial Option Grant**
**Initial Stock Grant**
**Contingent Worker**
**Original Start Date**
**Previous Employment ID**
**Professional Service Date**
**Seniority Start Date**
**Service Date**
**Hire Date**
Unified field: `start_date`
**Personal Information**
Contains personal information for an employee.
**Special Date**
**Nick Name**
**End Date**
**First Name**
Unified field: `first_name`
**Alt1 First Name**
**Gender**
Unified field: `gender`
**Last Name**
Unified field: `last_name`
**Alt1 Last Name**
**Marital Status**
**Middle Name**
**Alt1 Middle Name**
**Nationality**
Unified field: `nationality`
**Preferred Language**
**Preferred Name**
**Salutation**
**Event Date**
Unified field: `start_date`
**Suffix**
**Email**
Contains employee's email address.
**Email Address**
Unified field: `private_email`
**Email Type**
**Phone**
Contains information about an employee's phone numbers.
**Area Code**
**Country Code**
**Extension**
**Phone Number**
**Phone Type**
**Emergency Contacts**
Contains emergency contact information for an employee.
**eMail**
**Name**
**Phone**
**Relationship**
**Alt Phone**
**Address**
Contains information about address.
**Apartment**
**Bed Number**
**City**
**Street Number**
**Care Of**
**Municipality**
**Second Address Line**
**Camp**
**Building**
**Address Type**
**District**
Unified field: `home_address.city`
Unified field: `home_address.country`
**County**
**End Date**
**Province**
**Event Date**
Unified field: `start_date`
**State**
Unified field: `home_address.state`
Unified field: `home_address.zip_code`
## Integration Variants
**Current connector:** SAP SuccessFactors
For **SAP SuccessFactors**, we also offer the following other connector variants:
SAP SuccessFactors for the ATS category
SAP SuccessFactors for the Assessment category
SAP SuccessFactors for the LMS category