HR to ITSM
Nmbrs to Zendesk integration: employees per company in the internal service desk, with a task on hire and termination
With an integration between Nmbrs and Zendesk, every employee from Nmbrs appears as an end user in your internal Zendesk, in the organisation of their Nmbrs company, and IT gets a task with a due date as soon as an employment starts or ends. Job and department follow Nmbrs per payroll period, and a leaver is suspended instead of deleted.
What the integration does
Organisations with several entities in one Nmbrs environment that use Zendesk as internal service desk for IT and HR questions often hear about new colleagues through a separate message from the manager. Zendesk does not show which entity someone belongs to, while that is needed when laptop costs are charged per entity.
- Payroll creates an employee with an employment in the right company in Nmbrs.
- Nmbrs reports the change; KoppelHet fetches employee, employment, job and department.
- In Zendesk the employee is added as an end user in the organisation of their company.
- Before the start date IT gets an onboarding task; an end date is followed by an offboarding task.
- After the last working day KoppelHet suspends the user.
What to watch for with Nmbrs and Zendesk
- Employee numbers in Nmbrs are only unique within a company, while the external key in Zendesk applies to the whole account. KoppelHet puts the company number in front of the employee number, so number 12 of one BV never overwrites the user of the other BV.
- Each company in the Nmbrs environment becomes an organisation in Zendesk. The service desk can then report per BV and charge laptops to the right BV.
- Job and department apply per payroll period in Nmbrs. If a change is entered for next month, KoppelHet only updates the user in Zendesk when that period starts.
- At the start of a year or after a reorganisation, Nmbrs sometimes changes the department for hundreds of employees at once. Zendesk only allows a few changes per minute per user, so KoppelHet bundles such a wave in blocks of a hundred as a background job.
- Not every Nmbrs customer keeps the business email in Nmbrs. Without an address, Zendesk cannot recognise the colleague when they email; KoppelHet then takes the address from Entra ID or Google Workspace, or waits with the user until the address exists.
- The end date in Nmbrs is often only fixed just before the final payroll run. The offboarding task gets that date as due date and arrives immediately if the remaining time is already shorter than agreed.
- If payroll runs through a payroll bureau, the bureau gives the integration access to only your companies in Nmbrs. The bureau does not need to send anything to the service desk.
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 this work if our payroll bureau manages Nmbrs?
Yes. The bureau gives the integration read access to your companies. Nothing else changes for the bureau.
Is payroll data sent to Zendesk?
No. Only name, work email, company, job and department. Pay, BSN and payslips stay in Nmbrs.
What if someone moves from one BV to another?
Then one employment ends in Nmbrs and the other starts. KoppelHet recognises that as a transfer: the user moves to the other organisation and no offboarding task is created.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and read-only scopes for employees, employments and companies, with webhooks on changes and a daily comparison. The SOAP API stops in 2027.
- Zendesk is written through the Users API (create_or_update with skip_verify_email; create_or_update_many with at most 100 users per call as a background job, at most 30 at a time). Update User and Create Or Update User are limited to 5 requests per minute per user. Organisations through create_or_update on external_id, tasks through the Tickets API with type task and due_at.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Zendesk | Notes |
|---|---|---|
Bedrijfsnummer + personeelsnummer | external_id | Unique per Zendesk account, even with equal numbers in two BVs |
Voornaam, tussenvoegsel en achternaam | name | |
Zakelijk e-mailadres | email | |
Bedrijf | organization (external_id = bedrijfs-id) | |
Functie (per periode) | user_fields: functie | |
Afdeling (per periode) | user_fields: afdeling (dropdown) | |
Startdatum dienstverband | Ticket type task met due_at | |
Einddatum dienstverband | Offboardingtaak en daarna suspended = true |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll