HR to ITSM
Nmbrs to ServiceDesk Plus integration: employees per company as users in ManageEngine ServiceDesk Plus, with requests for joiners and leavers
With an integration between Nmbrs and ManageEngine ServiceDesk Plus, every employee from your Nmbrs companies is a user in ServiceDesk Plus, with company as site, department, job and manager, and KoppelHet creates a request from your template on a new employment, a job change or a departure. The company code precedes the employee number, so employees of different entities never merge.
What the integration does
Organisations with several entities in Nmbrs and a service desk in ManageEngine ServiceDesk Plus often hear about joiners and leavers through payroll or an accounting firm, by email and sometimes only after the first payroll run. ServiceDesk Plus then does not show which entity a requester belongs to.
- Payroll enters the new employee at the right company in Nmbrs.
- Nmbrs reports the change; KoppelHet creates the user in ServiceDesk Plus in the company's site and the right department.
- Within the agreed lead time before the start date the onboarding request follows, with that company's group.
- A change of job or department per the next period gives a change request on the first day of that period.
- On an end date the offboarding request follows, with closing off the user as a task.
What to watch for with Nmbrs and ManageEngine ServiceDesk Plus
- In ServiceDesk Plus a department sits under a site, and in Nmbrs departments sit under a company. The structures match one to one. KoppelHet makes each Nmbrs company a site, so two entities each keep their own Planning department without names clashing.
- Nmbrs numbers employees per company. Because employee_id in ServiceDesk Plus is meant as a unique key, KoppelHet puts the company code in front; a move to another entity thus becomes a change of the same user instead of a new one.
- Per entity a different team may prepare the laptop. KoppelHet fills the request's group based on the Nmbrs company, so the onboarding lands with the right team straight away.
- Job and department apply per payroll period in Nmbrs. A change per next month therefore reaches ServiceDesk Plus on the first day of that month, with that day as due date of the change request.
- Nmbrs gives the manager's email address. KoppelHet uses it to look up the user in ServiceDesk Plus and fills reporting to; if that user does not exist yet, they are created first, even when they work at another entity.
- The ServiceDesk Plus API does not allow changing a user's status. When someone leaves, KoppelHet creates the offboarding request with a task to close off the user. If they later return under the same Nmbrs number, KoppelHet finds the same user again.
- Nmbrs stops the old SOAP route on 1 March 2027. This integration uses the REST API with an employer-level login; an accounting firm thereby only grants access to this organisation's companies.
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
Our accounting firm manages Nmbrs. Do they need to do anything?
Only create an employer-level login once and grant consent for your companies.
Do pay or BSN go to ServiceDesk Plus?
No. The integration only reads personal, employment and organisation data.
Does this also work with ServiceDesk Plus on premises?
Yes, from build 11000. Older builds have a different requester API that stops working after the upgrade.
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 only read scopes for employee and employment data and the company structure, per company; webhooks on changes and a daily comparison.
- ServiceDesk Plus Cloud through Zoho OAuth 2.0 (EU: sdpondemand.manageengine.eu) and /api/v3/requesters; on premises from build 11000 through /api/v3/users with the authtoken header. User fields employee_id, name (mandatory), email_id, login_name, jobtitle, department (with site), reporting_to; status read-only, deletion with DELETE.
- Requests through POST /api/v3/requests with input_data (JSON); subject mandatory, plus requester (email_id), template, group, site, due_by_time in milliseconds and udf_fields.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in ManageEngine ServiceDesk Plus | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | employee_id | Numbers in Nmbrs are only unique per company |
Voornaam, tussenvoegsel en achternaam | first_name, middle_name, last_name en name | |
Zakelijk e-mailadres | email_id en login_name | |
Functie (huidige periode) | jobtitle | |
Bedrijf | site | |
Afdeling (huidige periode) | department binnen de site | |
Leidinggevende (e-mailadres) | reporting_to | |
Datum in of uit dienst | due_by_time van de aanvraag | |
Bedrijf van de medewerker | group van de aanvraag |
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