The HiBob integration keeps Empuls aligned with your HiBob HR platform. New joiners flow in automatically, role and manager changes propagate without manual intervention, and exits trigger your Empuls exit policy. HiBob’s custom fields can also be mapped to Empuls UDF/URF fields so the data structures match. Open the integrations hub in your tenant atDocumentation Index
Fetch the complete documentation index at: https://empuls.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
https://<your-empuls-url>/home/integrations and click HiBob.
Before you start
- You must be a Super Admin in Empuls.
- You need a HiBob account with Service User permissions (the recommended path for app integrations).
- Generate a HiBob API token before configuring the integration in Empuls. The Empuls flow asks for this token.
Connect HiBob
Generate a HiBob service-user token
In HiBob, navigate to Settings → Integrations → Service Users, create a new service user, assign the read-only role needed for directory data, and save the API token.
Paste the HiBob API token
Empuls validates the token against the HiBob API. A successful response shows your company name and a directory preview.
Map fields
Default mapping covers standard HiBob fields. HiBob custom fields appear in the mapping screen — map them to Empuls UDF (text) or URF (relationship) fields as needed.
What syncs
| HiBob field | Empuls field |
|---|---|
| First name / Surname | First Name / Last Name |
| Work email | Email (primary identifier) |
| Department | Department |
| Job title | Designation |
| Site / Location | Site |
| Manager | Reporting manager |
| Lifecycle status | Active / Inactive |
| Custom fields | UDF / URF (mapped per field) |
Integration status
The integration tracks state through these values you’ll see on the integration page:- Status 0 / Status 2 — Not started or removed. Configure or re-enable to begin.
- Status 1 — Active. Sync is running on schedule.
- Status 3 — Process pending. Initial sync is in progress.
- Status 4 — Disabled. Manually paused by an admin.
- Status 5 — Auto-disabled. Empuls suspended sync due to repeated errors (most often an expired token). Reconnect to resume.
Sync history
The sync history page lists each run with records added, updated, and failed. Click into a failed row to see the per-record error.Limits and gotchas
- Empuls reads from HiBob; it does not write back. Edits in Empuls to a synced field are overwritten on the next sync.
- HiBob custom-field mappings must be re-applied if you rename the field in HiBob.
- HiBob API rate limits apply. Very large directories require multiple cycles to fully reflect.
Related
- HRMS integration overview
- Manage employees — Manual overrides when needed.