Skip to main content
The HiBob integration syncs employees and Bob departments into Pike members and teams, and approved time off into Pike time off by policy. Capacity and utilization in Pike match the people data in Bob.

Connect HiBob

  1. Go to Workspace settings → Integrations → HiBob.
  2. Click Add integration.
  3. Enter a HiBob service user ID and token.
Only workspace admins can connect or disconnect HiBob.

Import data

On the integration page, click Import data. The stepper runs entities in dependency order, so Pike reads departments before the employees who belong to them. It skips entities whose Read toggle is off, names them, and links to sync settings.

What syncs

Time off

Approved time off from HiBob creates Pike time off. Each Bob time off policy maps to a Pike time off type. Defaults: vacation to Vacation, sick to Sick, parental to Parental, and other types to Vacation. That removes those hours from capacity, so allocations and utilization stay correct. Pending or rejected requests do not sync.

Compensation

Sync compensation to cost profiles is off by default. Only admins and finance users can turn it on. When on, salary and pay period from HiBob set the member’s cost profile, with the effective date from HiBob.

Source of truth

Once a record is linked, HiBob owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. HiBob owns person fields.

Schedule

Pike reads employees from HiBob every 24 hours and time off every hour. Import data and Refresh always run on demand.

Sync settings

While HiBob is connected, the What syncs with HiBob card sits under the top button row on the integration page. Each entity has a Read toggle (HiBob to Pike). Toggles save immediately. New connections start with Read on for everything.

Synced records

Every synced record shows the HiBob marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.

Sync issues

Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. The integration never deletes Pike data on its own. A record removed in HiBob is marked “Removed in HiBob” in Pike, never deleted.

Disconnect

Disconnecting HiBob stops syncing and keeps all imported data. Linked records keep their history.

Permissions

Synced data respects Pike roles and private projects. A private project’s tasks never sync out to anyone who cannot see the project in Pike.

Limits

  • Pike does not write to HiBob.
  • Pending or rejected requests do not sync.
  • Compensation sync is off until an admin or finance user turns it on.