HR to ITSM
Deel to Ivanti Neurons for ITSM integration: employees for own staff, EOR and contractors, with service requests
With an integration between Deel and Ivanti Neurons for ITSM, everyone who works for the organisation in Deel is an employee in Ivanti, whether own employee, EOR worker or contractor, and KoppelHet submits a service request from the template that suits that kind of worker at every start or end. The time zone from Deel goes into the request, so dates do not shift for colleagues in other countries.
What the integration does
Organisations that use Deel for own employees, employer of record and contractors, and Ivanti Neurons for ITSM for IT, usually only see in Ivanti who already has an account in the directory. Contractors and EOR workers in countries without an own office often fall outside it, while they also need a laptop and access.
- Deel sends a signed webhook; KoppelHet acknowledges it immediately and fetches the worker through the People API.
- KoppelHet creates or updates the employee in Ivanti, with the manager looked up by work email.
- At the onboarding status in Deel a service request follows from the template for own employees, EOR or contractors.
- A last working day produces an offboarding request, with the worker's time zone.
- After the last working day KoppelHet sets the employee in Ivanti to inactive.
What to watch for with Deel and Ivanti
- Deel returns a hiring type per worker. Own employees under the organisation's own legal entity are called direct employees in the current Deel guide; they get the full onboarding template in Ivanti, while EOR workers and contractors get their own template that IT puts together.
- Ivanti asks for the offset from UTC in minutes on every service request. Deel returns a time zone per worker; KoppelHet converts it to minutes on the date of the request, including daylight saving time, so the start date for a contractor on another continent does not shift by a day.
- Deel names the direct manager with their work email. KoppelHet uses that address to look up the employee in Ivanti and sets them as manager, so approvals in the service request reach the manager from Deel, even if they work in another country themselves.
- Deel expects an acknowledgement of a webhook within thirty seconds and disables the webhook after ten failed attempts. KoppelHet therefore acknowledges first and only then talks to Ivanti, and monitors whether the webhook in Deel is still enabled.
- Departments in Deel have a parent department, and department is a validated field with a fixed list in Ivanti. KoppelHet translates the Deel department to an existing list value and reports a new Deel department to IT instead of saving free text.
- Deel can deliver the same webhook twice. KoppelHet recognises a repeat by the event ID, so Ivanti never gets two onboarding requests for one start.
- The work email in Deel sits on the employment, not on the person. A contractor without a work email from the organisation only gets an Ivanti employee with their own address once IT confirms it in the onboarding request.
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 Deel have an Ivanti app?
We found none in the Deel App Store and no Deel connector at Ivanti either. KoppelHet uses the APIs of both sides.
Can we keep contractors out of Ivanti?
Yes. The integration filters on hiring type; which kinds of workers are included is set at the start.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through GET /people with fields (worker_id, preferred_first_name, last_name, employments with work_email and termination_last_day, department with parent, direct_manager with work_email, hiring_type, hiring_status, timezone) and filters hiring_types (including direct_employee, eor, contractor) and hiring_statuses (including onboarding, active, offboarding). Webhooks with x-deel-signature (HMAC-SHA256) and x-deel-hmac-label, 200 within 30 seconds, ten attempts up to sixteen hours and then disabled; recognise repeats by event_id. Token with read access only.
- Ivanti through the OData REST API on /api/odata/businessobject/employees (POST, PATCH on the RecID, $filter on email address, _Valid fields) and POST /api/rest/ServiceRequest/new with subscriptionId, strUserId (RecID), strCustomerLocation, parameters par-{RecID} and localOffset in minutes. 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 Deel | Field in Ivanti | Notes |
|---|---|---|
worker_id | Personeelsnummer op de employee | |
preferred_first_name en last_name | Voornaam en achternaam | |
employments[].work_email | PrimaryEmail en loginnaam | |
department.name | Afdeling met het bijbehorende _Valid-veld | |
direct_manager.work_email | Manager, opgezocht met $filter | |
hiring_type | Keuze van het sjabloon en een veld voor soort werker | |
timezone | localOffset van het serviceverzoek | |
termination_last_day | Parameter laatste werkdag van het offboardingverzoek |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions