Set up the sync
Map people fields
Map HiBob’s fields onto Novaplan’s canonical people fields. Nova can suggest a mapping that
you review before saving.
Reconcile departments
Confirm that HiBob departments map to your canonical departments. Resolution is by ID, so an
upstream rename does not move people between departments.
Run the first sync
Run the sync, then confirm in Pipelines that people landed and curated
cleanly.
Field mapping
| Canonical field | Typical HiBob source |
|---|---|
| Employee ID | The HiBob person ID (the stable join key) |
| Name | First and last name |
| Job title | Job title |
| Department | Department, reconciled to a canonical department |
| Site | Work site or location |
| Start date | Hire / start date |
| End date | Termination date (when present) |
| Employment status | Active, terminated, on leave |
| Comp | Base salary and comp components |
Department is resolved by ID, never by name. A HiBob department rename keeps each person in the
right canonical department rather than re-bucketing them.
Common questions
How often does HiBob sync?
How often does HiBob sync?
People data is intended to refresh on a regular cadence (typically daily). Check the freshness
state in Pipelines to confirm the last successful sync.
A new hire is missing from my plan
A new hire is missing from my plan
Confirm the person exists in HiBob with a start date and an active status, then re-run the
sync. If the version is locked, the snapshot is frozen and a post-lock addition is handled
separately.
Troubleshooting
- Sync fails to authorize: the HiBob credential has likely expired or rotated. Re-authorize in Admin -> Integrations.
- Stale people data: a quiet daily feed is flagged in Pipelines; re-run rather than assuming the data is current.
- People landing in the wrong department: the department is mapping by name, not ID. Fix the department mapping in Dimensions.
- Comp is masked: salary and comp are sensitive fields. See Permissions.