Connect HiBob to Ravenna using a HiBob service user. Ravenna authenticates directly against the HiBob API with Basic Authentication (username and password).Documentation Index
Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before you begin, ensure you have:- HiBob admin access
- Permission to create service users and manage API integrations in HiBob
Setup guide
Create a HiBob service user
Create a new service user
- Click New service user
- Enter a name (for example,
Ravenna) - Assign a permission group that grants read access to employees and groups, and write access to time-off (required for the Create Time-off Request workflow action)
- Save the service user
Add the integration in Ravenna
Select Basic Authentication
Click Connect, then select Basic Authentication as your authentication method.
What gets synced
- Employee profiles (name, email, job title, department, manager, status, hire date)
- Teams and departments
Troubleshooting
Authentication failed
Authentication failed
Cause: The username (service user ID) or password (token) is incorrect, or the service user has been disabled.Solution:
- Verify the ID and token were copied without extra spaces
- Confirm the service user is still enabled in HiBob
- Regenerate the token in HiBob if you cannot recover the original value, then update the credentials in Ravenna
Employees or groups missing
Employees or groups missing
Cause: The service user’s permission group does not grant access to the missing records.Solution:
- Open the service user’s permission group in HiBob
- Confirm it includes read access to employees and groups in scope
- Save the permission group and wait for the next sync, or trigger a manual reconnect
Create Time-off Request action fails
Create Time-off Request action fails
Cause: The service user is missing write access to time-off.Solution:
- Grant the service user’s permission group write access to time-off requests in HiBob
- Retry the workflow run after the change is saved