Skip to main content

HiBob

It also accepts webhooks from HiBob.

Connection

Setup

1
In HiBob, create a service user and a permission group for it, and copy the service user’s ID and token.
2
Give the permission group these permissions:
3
In the group’s Access data for condition, make sure Lifecycle status is set to Any. Without it, people who have left or haven’t started yet won’t sync, and Klef ends anyone it already has that HiBob stops returning.
4
Enter the service user’s ID and token in the connection’s settings and click the Save button. Turn on Sandbox only for a HiBob sandbox account.
When you add a custom field in HiBob, give the service user’s permission group View on it. Klef will only sync custom fields the group can view.
Klef reads every custom field the permission group can view. A custom field in Work or Employment belongs to the assignment, and any other custom field belongs to the worker. Make sure each custom field has a unique name, since a policy reads a custom field by name.

Apply terminations as they happen

Klef can apply a termination as soon as HiBob reports it, rather than waiting for the next plan. This needs the Standard or Enterprise plan.
1
Open the HiBob connection in Klef and copy its Webhook URL.
2
In Bob, add a webhook under Settings > Integrations > Automation > Webhooks. Enter the URL, choose version v2, and select the employee.left event.
3
Copy the webhook’s signing secret from Bob, enter it as the connection’s Webhook signing secret in Klef, and click the Save button.
4
In Klef’s workspace settings, turn on Apply HR webhook events automatically.
When HiBob reports that someone left, Klef reads them again from HiBob and applies only their termination, without approval. A plan still catches anything a webhook missed.
Choosing Revoke access immediately in Bob’s termination flow ends the person’s access to Bob only. Klef revokes their other access when the termination takes effect, as for any termination.

Settings

Fields

The worker model fields Klef fills from HiBob.