HR to ITSM
BambooHR to Ivanti Neurons for ITSM integration: employees from BambooHR and service requests for joiners and leavers
With an integration between BambooHR and Ivanti Neurons for ITSM, every employee from BambooHR is an employee in Ivanti, with department, location and manager, and KoppelHet submits a service request from the Ivanti template for every new employee or end date in BambooHR. Departments and locations from BambooHR are translated to the list values Ivanti already knows.
What the integration does
Organisations that use BambooHR for HR and Ivanti Neurons for ITSM for the service desk, often with head office in another country, usually let employees in Ivanti come from the directory. Someone hired in BambooHR who has no account yet then does not exist in Ivanti, and the onboarding request waits for IT.
- BambooHR reports a new employee or a change to a monitored field; KoppelHet fetches the employee.
- KoppelHet translates department and location to the list values in Ivanti and looks up the manager by work email.
- The employee is created or updated on employee number.
- Within the onboarding lead time KoppelHet submits the onboarding request in the new employee's name.
- An end date produces an offboarding request; after that the employee in Ivanti becomes inactive.
What to watch for with BambooHR and Ivanti
- In Ivanti a validated field such as department or location comes with a second field holding the RecID of the list value. BambooHR supplies department and location as text; KoppelHet looks up the RecID and reports a BambooHR value that does not exist in Ivanti, instead of saving loose text.
- A BambooHR webhook for changes only fires on monitored fields. KoppelHet has exactly the fields monitored that Ivanti uses (name, work email, job title, department, location, supervisor, termination date), so a pay change causes no call to Ivanti.
- BambooHR also returns the supervisor as an email address. KoppelHet uses that address to find the employee in Ivanti and sets them as manager, so approvals in the service request reach the supervisor from BambooHR.
- A service request in Ivanti needs the RecID of the employee it is for. Because BambooHR reports a new employee as soon as HR adds them, the employee is in Ivanti before the onboarding request has to be submitted, even if the directory does not yet know the account.
- BambooHR retries a failed webhook a few times within about forty minutes and then stops. The daily run over the changed endpoint catches a missed notification, and reads Ivanti in pages of at most a hundred records.
- The BambooHR API key and the Ivanti REST key both work with the permissions of one user. KoppelHet asks for a dedicated user on both sides: in BambooHR without access to pay, in Ivanti with a role that may only manage employees and service requests.
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 Ivanti have a BambooHR connector?
We found none at Ivanti or BambooHR themselves. Third-party provisioning tools exist, but KoppelHet uses the standard APIs of both sides.
Can we connect only the Dutch entity?
Yes. KoppelHet filters on location or division in BambooHR; other employees stay out of Ivanti.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- BambooHR through a webhook created via the API (HTTPS only, SHA-256 HMAC in X-BambooHR-Signature with X-BambooHR-Timestamp, monitor fields required for changes, several employees per message) and GET /api/v1/employees/changed?since= as a safety net. Fields include employeeNumber, workEmail, jobTitle, department, location, supervisorEmail and terminationDate.
- Ivanti through the OData REST API on /api/odata/businessobject/employees: POST, PATCH on the RecID, $filter and $top (default 25, maximum 100), _Valid fields with the RecID of the list value. Service requests through POST /api/rest/ServiceRequest/new with subscriptionId, strUserId, strCustomerLocation, parameters par-{RecID} and localOffset. REST API key (rest_api_key=…) on behalf of a dedicated user and role.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BambooHR | Field in Ivanti | Notes |
|---|---|---|
employeeNumber | Personeelsnummer op de employee | |
firstName en lastName | Voornaam en achternaam | |
workEmail | PrimaryEmail en loginnaam | |
jobTitle | Functietitel | |
department | Afdeling met het bijbehorende _Valid-veld | |
location | Locatie met het bijbehorende _Valid-veld | |
supervisorEmail | Manager, opgezocht met $filter | |
terminationDate | Parameter einddatum van het offboardingverzoek |
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