The HiBob AirSync connector imports your HR data from HiBob (Bob) into DevRev. It keeps employee records, departments, time-off requests, attendance entries, payroll history, and all HR history data in sync so your team can work with up-to-date HR data directly in DevRev.
The connector reads data from your HiBob account and creates corresponding records in DevRev. After the initial full import, it runs incremental syncs that only pull in records that have changed since the last run — keeping your data fresh without redundant transfers.
The connector is read-only — it imports data from HiBob into DevRev and does not write changes back to HiBob.
The connector imports the following entities from HiBob
Entity | DevRev Type | Description |
|---|---|---|
Employees | Dev User | Employee identity records — used for DevRev user matching |
Employee Profiles | Custom Object | Full employee HR profiles with 41+ fields including contact info, address, employment details, and org chart data |
Departments | Group | Department records; employees are automatically added as group members |
Sites | Custom Object | Office site records with location details |
Tasks | Custom Object | HiBob task records |
Entity | DevRev Type | Description |
|---|---|---|
Time-Off Requests | Custom Object | Employee time-off requests and approvals |
Attendance Entries | Custom Object | Clock-in/clock-out attendance records per employee |
Time-Off Balances | Custom Object | Time-off policy balances per employee |
These records are linked to individual employees and represent the full history of changes over time:
Entity | DevRev Type | Description |
|---|---|---|
Salary History | Custom Object | Historical salary changes including base amount, currency, pay period |
Work History | Custom Object | Historical job title, department, site, and manager changes |
Employment History | Custom Object | Historical employment type and contract changes |
Equity Grants | Custom Object | Stock option and equity grant records |
Variable Pay | Custom Object | Bonus and variable compensation records |
Training Records | Custom Object | Training completions and certifications |
Lifecycle History | Custom Object | Hire, termination, and other employment lifecycle events |
Payroll History | Custom Object | Payroll payment records with gross/net amounts and deductions |
Before you install the connector, make sure you have:
A HiBob account with admin access (required to create a service user)
A DevRev account with permission to install snap-ins
The connector authenticates with HiBob using a service user ID and token — not a personal account login.
Log in to HiBob as an admin.
Navigate to Settings > Integrations > Service Users.
Click Add Service User, give it a name (for example, DevRev AirSync), and set appropriate permissions (read access to People, Time-Off, Attendance, Payroll, and HR history modules).
Copy the Service User ID and Service User Token — you need both during connector setup.
Go to the DevRev Marketplace and search for HiBob AirSync.
Click the connector listing and select Install.
Follow the on-screen prompts to complete installation.
Once installed, the connector appears in your DevRev snap-ins list.
After installation, connect the snap-in to your HiBob account.
In DevRev, navigate to Settings > Integrations > HiBob AirSync.
Click Add Connection.
Enter:
Service User ID — the service user ID from HiBob Settings > Integrations > Service Users
Service User Token — the token generated for that service user
Click Save. DevRev verifies the credentials against your HiBob account.
After configuration, click Start Sync to begin the first full import. The initial sync fetches all records from HiBob including all historical data for every employee. Depending on the size of your organization, this may take several minutes.
You can monitor sync progress from the connector's status panel. The sync shows a breakdown of records collected per entity type on the left and records created in DevRev on the right.
After the initial sync completes, the connector automatically runs incremental syncs. Each incremental run only fetches records that have changed in HiBob since the last sync — so subsequent syncs are significantly faster.
You can trigger a manual sync at any time by clicking Sync Now in the connector settings.
One of the key features of the HiBob connector is automatic department group membership. When the connector syncs departments, it:
Creates a DevRev group for each HiBob department.
Reads each employee's departmentId field.
Adds each employee as a member of their department's group.
This means you can use DevRev groups to filter, notify, or assign work to entire departments — and the membership always reflects your HiBob org chart.
The Employee Profiles custom object contains 41+ fields imported from HiBob:
Category | Fields |
|---|---|
Identity |
|
Contact |
|
Address |
|
Work |
|
Manager |
|
Employment |
|
Personal |
|
Org |
|
Financial |
|
State |
|
Use Employee Profiles for HR data. The employees entity maps to DevRev dev_users (identity only — 4 fields). All 41+ HR fields live in the employee_profiles custom object. Query employee profiles for HR data.
Keep your service user token secure. Regenerate your HiBob service user token immediately if it is ever exposed. Update the connection in DevRev after regenerating.
Do not share service user credentials across integrations. Create a dedicated service user in HiBob specifically for the DevRev connector. This makes it easier to revoke access without affecting other integrations.
Run a fresh full sync after org restructuring. If you reorganize departments in HiBob (rename, merge, or move employees), run a manual sync to keep DevRev groups in sync with your new structure.
Confirm your Service User ID and Token are correct and the service user has not been deactivated in HiBob.
Make sure the service user has read permissions for People, Time-Off, Attendance, Payroll, and HR history data in HiBob.
Check the sync results panel — each entity shows a collected count on the left. If it shows 0, the HiBob API returned no records (check that data exists in HiBob for that entity).
For per-employee history entities (salary, equity, training, etc.), data only exists if employees have entries in those modules in HiBob.
Confirm the sync completed successfully and Department Memberships was extracted (should show 40 records for 40 employees with departments).
Verify employees in HiBob have a departmentId set on their work profile.
Re-run a full sync to rebuild group membership.
The employees entity (dev_user) only contains identity fields. Look at the employee_profiles custom object for full HR data.
If specific fields like address or contact info are blank, verify the employee has those fields populated in HiBob.
The initial sync is expected to take several minutes for organizations with 40+ employees, especially with per-employee history entities (salary, work history, equity, payroll) which make one API call per employee per entity type.
Subsequent incremental syncs are much faster as they only fetch changes.
Does the connector support two-way sync? No. The HiBob connector is read-only — it imports data from HiBob into DevRev only. Changes made in DevRev are not written back to HiBob.
How often does the connector sync? Incremental syncs run on a schedule managed by DevRev. You can also trigger a manual sync at any time from the connector settings.
Why do I see both "Employees" and "Employee Profiles" in the sync results? They serve different purposes. Employees creates DevRev dev_user identity records (used for @mentions, assignments, etc.). Employee Profiles creates custom objects with all 41+ HR fields. Both are needed for full HR data access.
Can I sync specific departments only? The current connector imports all employees and departments from your HiBob account. Department filtering is not supported at this time.
What happens if HiBob is temporarily unavailable? The connector retries failed requests automatically. The sync state is preserved so the connector picks up where it left off rather than restarting from scratch.
Is employee data encrypted in transit? Yes. All communication between DevRev and HiBob uses HTTPS. Authentication uses HTTP Basic Auth with your service user credentials encoded in the Authorization header.