X4HR to ITSM
HiBob to Xurrent integration: people per site and requests for joiners and leavers
With an integration between HiBob and Xurrent, every employee from Bob is a person in Xurrent, with organisation, site, time zone and manager, and KoppelHet creates a request for the right team when someone joins or leaves in HiBob. The HiBob ID is the fixed key, so a new email address does not create a second person in Xurrent.
What the integration does
Organisations with employees in Bob and a service desk in Xurrent often only get new colleagues as a person in Xurrent once they log in for the first time. Onboarding requests are then submitted by hand by the manager, and anyone going on garden leave keeps access until the formal end date.
- HiBob reports a new or changed employee; KoppelHet fetches department, site, job and manager.
- KoppelHet first creates new departments and sites in Xurrent, then the person with the HiBob ID as source key.
- Within the onboarding lead time KoppelHet creates a request for the new employee, submitted by the manager.
- A departure or garden leave produces an offboarding request with the last working day as desired date.
- Once the offboarding request is completed, KoppelHet disables the person in Xurrent.
What to watch for with HiBob and Xurrent (4me)
- Xurrent recognises a person by the primary email address, which is also the login name. A new surname in Bob changes that address. KoppelHet therefore records the HiBob ID as source key and updates the person on it, so old requests stay with the same person.
- Only an API user with the Account Administrator role may set or change source and source key in Xurrent. The integration user gets that role, and otherwise only the role that may create requests.
- A site in Bob becomes a site in Xurrent, and every person gets that site's time zone and language. A colleague at a site in another time zone then sees the desired date of their onboarding request on their own first working day.
- Garden leave counts as a departure in HiBob as soon as it starts. KoppelHet therefore creates the offboarding request on the first day of the garden leave, and not on the contract end date, which can be months later.
- A disabled person may no longer be related to records in Xurrent. KoppelHet only disables a leaver once the offboarding request is completed, so the team can still take in laptop and badge in their name.
- A request in Xurrent always requires a team. KoppelHet picks the team that belongs to the site in Bob, so a new colleague at a site abroad lands with that country's IT team straight away.
- On a change HiBob only reports which fields changed, not the new values. KoppelHet only updates the person in Xurrent if department, site, job or manager is among those fields, so a new home address in Bob does nothing in Xurrent.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does Xurrent have a HiBob integration?
We found none. Xurrent can receive people through SCIM from an identity provider, but that does not produce requests for joiners and leavers. KoppelHet builds on the APIs of both sides.
Who submits the onboarding request?
The manager from Bob is the requester, the new employee is the person the request is for. Questions from the service desk then reach the manager.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob through webhooks (employee events v2: employee.created, employee.updated with the IDs of changed fields, employee.left also on garden leave, employee.access.revoked.immediately) and POST /v1/people/search with fields and a filter on root.id.
- Xurrent through the REST API: /people (primary_email required and unique, job_title, organization, site, manager, locale, time_zone, disabled, source up to 30 characters, sourceID up to 128), /organizations and /sites. Requests through POST /requests with the required fields category, subject, requested_by, requested_for and team, plus template and desired_completion_at.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in Xurrent (4me) | Notes |
|---|---|---|
root.id | sourceID (source hibob) | Only an Account Administrator may set it |
root.email | primary_email | Also the login name in Xurrent |
root.firstName en root.surname | name | |
work.title | job_title | |
work.department | organization | |
work.site | site, time_zone en locale | |
work.reportsTo | manager | |
work.startDate | desired_completion_at van het onboardingrequest |
Related
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
Carerix → HiBob
Carerix to HiBob integration: successful match becomes a new employee in Bob
Greenhouse → HiBob
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob