X4HR to ITSM
BambooHR to Xurrent integration: people with organisation and site, requests for joiners and leavers
With an integration between BambooHR and Xurrent, every employee from BambooHR is a person in Xurrent, with organisation, site and manager, and KoppelHet creates a request from the right template for every hire or end date. A leaver is only disabled in Xurrent once their offboarding request is completed.
What the integration does
Organisations that use BambooHR for HR and Xurrent for service management often load people into Xurrent with a periodic import. Someone hired between two imports cannot yet be requested for in a request, and a departure lingers until someone disables the person by hand.
- BambooHR reports a new employee or a change to a monitored field; KoppelHet fetches the employee.
- As soon as there is a work email, KoppelHet creates or updates the person, with BambooHR as source.
- The manager is looked up by their work email from BambooHR.
- Within the onboarding lead time a request follows from the onboarding template for the site's team.
- An end date produces an offboarding request; after completion the person is disabled.
What to watch for with BambooHR and Xurrent (4me)
- Xurrent refuses a person without a primary email address, and in BambooHR the work email is often still empty for a new hire. KoppelHet creates the person as soon as BambooHR reports a work email; until then the onboarding request is in the manager's name, with the new colleague in the description.
- A disabled person in Xurrent may no longer be linked to new records. KoppelHet therefore creates the offboarding request while the person is still active, and only disables them once that request is completed.
- Xurrent has a source and source ID per person. KoppelHet stores BambooHR and the BambooHR ID there, so IT can see in Xurrent which people come from HR and recognise a manual change to them.
- The job title may be at most eighty characters in Xurrent, while BambooHR allows longer titles. KoppelHet does not silently shorten a long title, but reports it to HR so the title stays the same in both systems.
- BambooHR has divisions and locations, Xurrent organisations and sites. KoppelHet converts the division to an organisation and the location to a site with time zone, so the right team gets the request and the completion date falls in local time.
- A request in Xurrent needs category, subject, requester, beneficiary and team. KoppelHet fills the requester with the supervisor from BambooHR, who is looked up as a person by their work email.
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 BambooHR integration?
We found none. Xurrent has a People Import and SCIM, but no ready-made BambooHR flow. KoppelHet uses the REST API.
Who may set the source marker?
According to Xurrent only an Account Administrator. The integration therefore gets its own user with that role, or leaves the marker out.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- BambooHR through event-based webhooks (employee.created, employee.updated with monitor fields and changedFields) and GET /api/v1/employees/changed?since=; then the employee record with employeeNumber, workEmail, jobTitle, division, location, supervisorEmail, hireDate and terminationDate.
- Xurrent through the REST API: /people (primary_email mandatory and unique, employeeID up to 128 characters, job_title up to 80, organization, site, manager, time_zone, disabled, source up to 30 and sourceID up to 128). Requests through POST /requests with category, subject, requested_by, requested_for, team, template and desired_completion_at.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BambooHR | Field in Xurrent (4me) | Notes |
|---|---|---|
workEmail | primary_email | Mandatory and unique |
employeeNumber | employeeID | |
id | source BambooHR en sourceID | |
jobTitle | job_title (maximaal 80 tekens) | |
division | organization | |
location | site en time_zone | |
supervisorEmail | manager | |
hireDate | desired_completion_at van het onboardingrequest |
Related
Ashby → BambooHR
Ashby to BambooHR integration: hire, changed start date and employment status in BambooHR
BambooHR → 4PS Construct
BambooHR to 4PS Construct integration: employees from BambooHR in the 4PS company of their location
BambooHR → Active Directory
BambooHR to Active Directory integration: accounts in your own domain from HR
BambooHR → ADP iHCM
BambooHR to ADP iHCM integration: salary, bonuses and commissions to Dutch payroll