Capabilities
Gather HiBob credentials
1
In HiBob, navigate to Settings > Integrations > Automation >
Service Users and create a new service user.
2
Copy the Service user ID and Token. The token is shown once —
treat it like a password.
3
Add the service user to a permission group that can read employee data in
the root and work categories, plus the lifecycle status field.
To sync terminated
employees, the permission group’s Access data for setting must also
cover inactive (former) employees, not only employed ones.
4
Note your HiBob API URL. Production is
https://api.hibob.com/v1. If
HiBob has provisioned a sandbox for your company, the sandbox URL is
https://api.sandbox.hibob.com/v1 — sandbox access is granted by HiBob on
request, not self-serve.Configuration fields
Synced resource types
- Employees: people from HiBob’s people search. Each employee becomes a user. Terminated employees are included and synced with a disabled status; employees in every other lifecycle state (employed, hired, garden leave, leave, parental leave) are synced as enabled, with the exact state kept on the user profile.
- Departments: the company’s department list, including sub-departments.
Each department becomes a group with a single
memberentitlement. - Department membership: an employee is a member of the department named in the employee’s work data.
Special notes
- Provisioning is not supported. The connector reads employees and departments only.
- The connector authenticates with HTTP Basic credentials: the service user ID as the username and its token as the password.
- HiBob omits any field the service user is not permitted to read, without raising an error. If the permission group is missing a category, the connector’s validation step reports it when the connector is set up.
- An employee with no department is synced as a user but holds no department membership.
- HiBob reports an employee’s department as the ID of the department list
item, so the connector matches that ID to the department list. Older
departments that HiBob still reports by name are matched by name. The user
profile records the raw value as
department_id. - An employee’s manager is recorded on the user profile.
Configure the HiBob connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your HiBob connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for HiBob and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Paste the HiBob credentials into the relevant fields:
- HiBob API URL:
https://api.hibob.com/v1. - Service user ID: The ID of the service user you created in HiBob.
- Service user token: The token paired with the service user ID.
9
Click Save.
10
The connector’s label changes to Syncing, followed by
Connected. You can view the logs to ensure that information is
syncing.