Introduction
HiBob is an all-in-one platform for HR, payroll, and finance. It unifies your people data, automates workflows, and runs compliant payroll on a foundation built for growing US and Canadian teams.
The HiBob > Kallidus integration is a one-way sync that reads user data in HiBob to create and update users in Kallidus on a nightly basis. Here's what the integration does:
Create users: When a new employee is added in HiBob, they will be created in Kallidus as a new user
Update user attributes: When an employee is updated in HiBob, the corresponding user will be updated in Kallidus
Deactivate users: When an employee is terminated in HiBob, the corresponding user will be deactivated in Kallidus
Link existing users: Existing employees in HiBob will be linked to their existing users in Kallidus based on matching HiBob ID
How it works
Create users
- When a new employee is added in HiBob
- If your Kallidus instance is configured to create future starters, they will be created in Kallidus as a new inactive user and become active on their start date
- If your Kallidus instance is configured to not create future starters, they will only be created in Kallidus as a new active user on their start date
- This process runs on a nightly basis (between 11PM - 4AM UTC)
Update user attributes
- When an employee is updated in HiBob, the corresponding user will be updated in Kallidus
- This process runs on a nightly basis (between 11PM - 4AM UTC)
Deactivate users
- When an employee is terminated in HiBob, the corresponding user will be deactivated in Kallidus on their termination date
- This process runs on a nightly basis (between 11PM - 4AM UTC)
Link existing users
- Existing employees in HiBob will be linked to existing users in Kallidus based on matching HiBob ID
- Check out the Before enabling the integration section to get the most of the initial user linking when the integration is first enabled
Before enabling the integration
Getting started
For long-standing customers, please reach out to your Customer Experience Manager (CEM) to get started with this integration. For customers currently in implementation, you can reach out to your Services Consultant (SC) instead.
Please review the prerequisites below to ensure you have all required details.
HiBob API user required
Prior to the kickoff call, you need to create an API service user in HiBob and obtain the following details:
- ID
- Token
Check out the Setting up the integration section for how to create an API service user in HiBob.
Additional details required
During the kickoff call, you'll be consulted on the following setup details:
- Do you want to sync custom fields from HiBob to Kallidus?
- Yes or No
- Field mappings
- Check out the Supported fields section for which fields can be custom mapped
Linking existing users
If you have an existing employee in HiBob that already exists as a user in Kallidus, please ensure the chosen ID matches between the two systems. Otherwise, the existing employee in HiBob will be created as a new user in Kallidus.
If you have an existing user in Kallidus that has not been added as an employee in HiBob, please ensure to do so before enabling the the integration. Otherwise, the existing user in Kallidus will be excluded from the integration.
Setting up the integration
Part 1: Provisioning an API service user in HiBob
To provision an API service user, refer to this HiBob help centre article. Please note that you must be an admin.
When the API service user is initially provisioned, it will have no access rights in HiBob at all. Please continue following the previously linked article to ensure the API service user has sufficient read-only rights.
Part 2: Configuring the integration in Kallidus
When ready, our technical team will schedule a kickoff call to review setup details, field mappings, and any questions you may have. After the kickoff, our technical team will set up and test the integration for you.
Supported fields
We are continually expanding the range of fields that sync between HiBob and Kallidus. Here's what we currently support:
HiBob |
Kallidus |
Required for user |
Can be custom mapped |
First name |
First name |
Yes |
No |
Last name |
Last name |
Yes |
No |
Username |
Yes |
Yes |
|
Start date |
Start date |
Yes |
No |
- |
Status (auto-calculated) |
Yes |
No |
HiBob ID |
User import key |
No |
Yes |
No |
Yes |
||
Job title |
Job profile |
No |
No |
Manager ID |
Manager import key |
No |
No |
Termination date |
Termination date |
No |
No |
Any standard or custom field |
User fields 1-20 |
No |
Yes |
Frequently asked questions (FAQs)
How do I check if the integration is working as expected?
This integration feeds data into Kallidus' overnight batch import process, which covers user creation, updates, and termination. As such, you can validate whether the latest batch import process ran successfully using the User Import report.
How do I troubleshoot the integration if any issues arise?
This integration feeds data into Kallidus' overnight batch import process, which covers user creation, updates, and termination. Kallidus Support monitors this process very closely and they will reach out to you if any issues are found. Alternatively, you can reach out to Kallidus Support here.