Accounts in applications
Nmbrs to Zoom integration: Zoom users with licence, department and manager from Nmbrs
With an integration between Nmbrs and Zoom Workplace, a new employee from Nmbrs automatically gets a Zoom user, with a Basic or Licensed account depending on their function, and with department, cost centre and manager in the profile. After the end date in Nmbrs the Zoom user is deactivated and their recordings and meetings go to their manager.
What the integration does
Organisations that use Nmbrs as their personnel system and meet or call with Zoom often hand out paid Zoom licences on request. Licences stay with leavers, new colleagues wait for an account, and after a marriage or divorce Zoom still shows the old surname.
- You record which functions in Nmbrs get a paid Zoom licence; the rest get a Basic account.
- KoppelHet reads the employees of the designated companies in Nmbrs every day, without BSN and without wage data.
- A new employee becomes a Zoom user with the account type for their function, and with department, cost centre and manager.
- On a change of name, function or department KoppelHet updates the profile and, if needed, the account type.
- After the end date KoppelHet deactivates the user, with the manager as recipient of their data.
What to watch for with Nmbrs and Zoom Workplace
- In Zoom the account type determines whether someone has a paid licence. KoppelHet derives it from the function in Nmbrs, so a team leader does get a Licensed account and a warehouse worker does not. If licences have run out, Zoom refuses a paid user; KoppelHet then creates a Basic account and reports the shortage.
- Zoom does not update the display name when only the first or last name changes. Nmbrs uses its name format setting to decide whether someone is addressed by their own name, their partner's or a combination. KoppelHet builds the name according to that setting and sends the display name again on every change.
- Zoom expects the manager as an email address. In Nmbrs the manager is a separate manager record with its own email address. KoppelHet takes that address over directly, without first looking the manager up as an employee.
- Zoom has a recipient who receives a user's recordings and meetings when that user is deactivated or deleted. KoppelHet fills that recipient with the manager from Nmbrs, so a leaver's recurring meetings do not disappear.
- The cost centre from Nmbrs goes to Zoom's cost centre field. That lets finance recharge Zoom licences per cost centre with the same structure as the wage costs.
- Zoom does not let administrators be deactivated or have their email changed through provisioning. If someone with an admin role leaves, KoppelHet reports this to IT instead of failing silently, so the role goes to someone else first.
- Zoom's SCIM integration only works on a Business or Education account with an approved vanity URL and single sign-on. Without those three KoppelHet cannot manage users from Nmbrs; we check that before the start.
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
We have no single sign-on for Zoom. Is it still possible?
Not through SCIM, because Zoom requires single sign-on for it. It is often simpler to set up SSO through Entra ID or Google first; we discuss that in the first conversation.
Are Zoom Phone numbers included too?
Not in the first version. Assigning a phone number per function can be added later as an extension.
What happens to a leaver's recordings?
They go to the manager from Nmbrs, who is set as recipient. If no manager is known, IT gets a notice before the user is deactivated.
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 access only. In the SOAP EmployeeService (ending 1 March 2027) the sources are called PersonalInfoWithoutBSN (with Naamstelling), Function_GetCurrent, Department_GetCurrent, CostCenter_GetCurrent and Manager_GetCurrent.
- Zoom through the SCIM2 API at https://api.zoom.us/scim2 with a server-to-server OAuth app with scope scim2:admin, content type application/scim+json. POST /Users, PUT /Users/{userId} with userType, title and the enterprise extension (department, costCenter, employeeNumber, manager, organization), transferee in the Zoom extension, and PATCH with active = false to deactivate. Zoom returns HTTP 429 on too many calls.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Zoom Workplace | Notes |
|---|---|---|
EmailWork | userName en emails (work) | |
Nickname of FirstName | name.givenName | |
Prefix en LastName, volgens Naamstelling | name.familyName en displayName | |
Function | title en userType | Licensed or Basic through a table per function |
Department | enterprise.department | |
CostCenter | enterprise.costCenter | |
Bedrijfsnaam | enterprise.organization | |
EmployeeNumber | enterprise.employeeNumber | |
Manager (e-mail) | enterprise.manager en transferee | |
Datum uit dienst | active = false |
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