X4HR to ITSM
Deel to Xurrent integration: people per country and requests at the start and end of every contract
With an integration between Deel and Xurrent, everyone working through Deel becomes a person in Xurrent, with site, time zone and manager, and KoppelHet creates an onboarding request with the start date as desired completion as soon as someone enters onboarding in Deel. When the last contract gets a last working day, an offboarding request follows for the team of that country.
What the integration does
Organisations that hire people in different countries through Deel and use Xurrent as their service desk often receive a signed contract months before the start. The IT team in that country then needs to know when the workplace must be ready, without contract details being visible to everyone in the request.
- Deel reports a new or changed person; KoppelHet checks the signature and reads the person with a field list.
- KoppelHet creates or updates the person in Xurrent, with the site of their country and the manager.
- At the onboarding status KoppelHet creates the request for the team of that site, with the start date as desired completion.
- When the last running contract gets a last working day, the offboarding request follows.
- Once the offboarding request is completed, KoppelHet disables the person.
What to watch for with Deel and Xurrent (4me)
- In Xurrent a desired completion date that lies later than the SLA resolution target replaces that target. KoppelHet sets the start date from Deel as the desired completion, so a contract signed three months before the start does not push the onboarding request outside the SLA straight away.
- Xurrent notifies the requester when the desired completion is set or changed. When the start date in Deel moves, KoppelHet adjusts the date on the open request, so the manager also sees the new date.
- An internal note in Xurrent is only visible to the Auditor, Specialist and Account Administrator roles. KoppelHet puts the type of working relationship and the legal entity from Deel there, so the IT team sees whether it is EOR, PEO or a contractor, while the new colleague does not read that in their request.
- Xurrent has an employeeID of up to 128 characters per person. KoppelHet puts the Deel worker_id there, which stays the same per person across all their contracts, so a switch from contractor to own employee keeps the same person with the same requests.
- A request in Xurrent always needs a team. KoppelHet chooses the team from the site of the country in Deel, so an EOR employee in a country without an own office reaches the team that handles hardware shipping to that country.
- Deel disables a webhook subscription after the tenth failed attempt, about sixteen hours after the first. KoppelHet therefore compares every person with a running contract in Deel with Xurrent each day and creates the requests that were left behind by a dropped subscription.
- Deel gives a termination its own status, which can also become cancelled. When the termination in Deel is cancelled, KoppelHet sets the open offboarding request in Xurrent to declined with a note, and the person remains active.
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 Deel integration?
We found none, and the Deel App Store has no Xurrent app. KoppelHet builds on the APIs of both sides.
Does the new colleague see their contract details in the request?
No. Type of working relationship and entity are in the internal note, which only specialists, auditors and administrators see. Salary does not enter Xurrent at all.
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, work_email, job_title, country, timezone, client_legal_entity, direct_manager, hiring_type, hiring_status, start_date, active_worker_termination_status, employments with termination_last_day). Webhooks with x-deel-signature (HMAC-SHA256) and x-deel-hmac-label; for own employees Employee Created Direct and Employee Updated Direct. Ten attempts up to sixteen hours, then disabled.
- Xurrent through the REST API: /people (name and primary_email required, employeeID up to 128 characters, job_title up to 80, site, manager, time_zone, locale, disabled) and POST /requests with category, subject, requested_by, requested_for, team, template, desired_completion_at and internal_note; status declined for a withdrawn departure.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Xurrent (4me) | Notes |
|---|---|---|
worker_id | employeeID | Fixed key, up to 128 characters |
preferred_first_name en last_name | name | |
work_email | primary_email | |
job_title | job_title | Up to 80 characters |
country en timezone | site en time_zone | |
direct_manager.work_email | manager en requested_by | |
hiring_type en client_legal_entity | internal_note van het request | |
start_date | desired_completion_at van het onboardingrequest | |
employments[].termination_last_day | Offboardingrequest, daarna disabled |
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