Velory’s HiBob integration enables automatic, one-way synchronization of employee data from HiBob into Velory. This ensures up-to-date user information while reducing manual work across IT and HR processes. Key employee attributes - such as name, employment status, department, and contact details - are continuously kept in sync, supporting efficient lifecycle management from onboarding to offboarding.
🧭 In this guide:
- How to activate the HiBob integration
- Data fields imported from HiBob
- How onboarding works
-
Automating offboarding with HiBob
How to activate the integration
To enable the integration, follow these steps:
-
Sign in to Velory as an Admin.
- Navigate to Settings > Integrations > HR System Sync
- In the dropdown menu, select HiBob.
- Follow the steps in the checklist:
- Add your Service user ID
- Add your Service user token
- Add your Service user ID
Once the credentials are submitted, the user synchronization will begin automatically.
The integration is successfully activated when the status changes to Active and user data has been synchronized.
Data fields imported from HiBob
Velory imports the following employee data fields:
| Field | Description |
| id | Unique user ID in HiBob |
| username | System-assigned username (usually the work email) |
| first_name / last_name | Employee’s first and last name |
| job_title | Job title |
| employee_number | Unique employee identifier, used to merge records across systems |
| department_name | Department (nullable) |
| division_name | Division (nullable) |
| employee_type | Type of employment (e.g., full-time, contractor) (nullable) |
| cost_center_name | Assigned cost center (nullable) |
| state | Employment status (e.g., active, inactive) |
| employment_start_date | Employment start date (YYYY-MM-DD) |
| employment_end_date | Employment end date (YYYY-MM-DD) (nullable) |
| manager_email / manager_id | Email and ID of the direct manager (nullable) |
Email information
Velory supports multiple email addresses per employee:
| Field | Description |
| emails[].type | Email type (work, personal, etc.) |
| emails[].value | Email address |
| emails[].primary | Is this the primary email? (boolean) |
| personal_email | Standalone personal email (nullable) |
Phone numbers
Multiple phone numbers can also be imported:
| Field | Description |
| phone_numbers[].type | Phone type (home, mobile, etc.) |
| phone_numbers[].value | Phone number |
| phone_numbers[].primary | Is this the primary phone? (boolean) |
Group and location data
| Field | Description |
| groups[].id / groups[].name | Group membership |
| office_location | Employee’s office location (nullable) |
| building_id | Building ID (nullable) |
Address data
| Field | Description |
| addresses[].type | Address type (home, work, etc.) |
| addresses[].street_address | Street name and number |
| addresses[].locality | City |
| addresses[].postal_code | ZIP or postal code |
| addresses[].country | Country |
| addresses[].primary | Is this the primary address? (boolean) |
| addresses[].raw_address | Full unstructured address string |
💡 In addition to the fields listed above, Velory can also import any attribute available via the HiBob or Directory sync API.
Learn more about combining HR and Directory sync in this article.
How onboarding works
When a new employee starts and the employee is added to HiBob, the employee data is automatically added to Velory.
How to enable or disable automatic distribution of invites sent
Even though the employee is added to Velory, it doesn’t mean that the employee is automatically invited to sign into Velory. There is a possibility for an Admin to automate the distribution of invites to the platform for any newly added user. This depends on if the email setting is enabled or disabled.
If a customer wants to automate the invitation triggered to a new employee, this can be made in Settings > Company > Details & Settings > Company Settings.
- With the setting turned on: Invitation emails will not be sent to employees automatically.
- With the setting turned off: Invitation emails will automatically be sent to any new employee that is added via HiBob.
Automating offboarding with HiBob
With the HiBob integration in place, offboarding workflows no longer need to be started manually.
When a termination date is set in HiBob:
- 📆 That date is automatically imported to Velory
- 🔄 The offboarding workflow is triggered based on your company’s offboarding settings
You can configure when offboarding begins under Settings > Company > Employee Offboarding.
This automation ensures timely actions—such as deactivating access and collecting devices—without manual follow-ups or data entry.