Accounts in applications
Nmbrs to Slack integration: Slack account with company, department and start date from Nmbrs
With an integration between Nmbrs and Slack, a new employee from Nmbrs gets a Slack account on their start date with function, department, company and start date, and joins their department's user group. A move to another company only updates profile and groups, and after the end date the integration deactivates the account.
What the integration does
Organisations that run payroll for their companies in Nmbrs and work internally in Slack often create Slack accounts after a message from the manager. The profile does not show which company someone works for, user groups do not follow the departments, and leavers stay active until someone notices.
- Together we decide which companies and departments get a user group and which fields go into the Slack profile.
- Someone with access to the employers in Nmbrs gives the integration consent once, for reading only.
- On the start date KoppelHet creates the Slack account with function, department, company and start date, in the department's user group.
- Another function, department or company updates profile and user group on the effective date.
- After the end date KoppelHet deactivates the account.
What to watch for with Nmbrs and Slack
- One Nmbrs environment often holds several companies. Slack has a profile field for the organisation; KoppelHet puts the company from Nmbrs there, so colleagues in Slack see which company someone works for, and creates user groups per company and department instead of one group per department name.
- A move to another company is a leave and a hire in Nmbrs. Slack refuses a new account on an email address that already exists, even for a deactivated user. KoppelHet recognises the same person and only updates company, department and user group on the existing account.
- Employee numbers in Nmbrs are only unique per company, while the employee number in Slack is a single field. KoppelHet puts the company code in front of the number, so a lookup in Slack never ends up at the wrong employee.
- Slack has a profile field for the start date. KoppelHet fills it with the start date from Nmbrs and only creates the account on that day, even if payroll entered the employee weeks earlier.
- A function applies per payroll period in Nmbrs. KoppelHet updates the job title in Slack on the first day of that period, so the profile does not change on the day payroll enters the change.
- A Slack username may have at most 21 characters. Nmbrs stores the name prefix separately from the surname; KoppelHet builds the name without spaces and shortens long names by a fixed rule, so a Van der Heijden does not end up with a converted, unreadable name.
- When a former employee returns under the same employee number, KoppelHet finds the deactivated Slack account by that number and makes it active again, so old messages and channels stay with the same person.
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
Doesn't Slack go through Entra ID or Google for us?
Then that stays the source for Slack, and Nmbrs supplies the right data there. Directly from Nmbrs fits when company, start date and departments per company must be right in Slack and the identity provider does not pass them on.
Does the manager also go into Slack?
Not in the first version. Slack can store a manager; we first check whether it is recorded per employee in your Nmbrs. It can follow later as an extension.
What happens to a leaver's messages?
Slack deactivates users instead of deleting them. Messages and files stay according to the retention policy of your Slack environment.
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 (identityservice.nmbrs.com, authorisation code flow with consent from an Nmbrs user and refresh token) with read-only scopes: employee.info.read, employee.employment.read, employee.orgstructure.read and company.info.read; read per company. No scopes for pay or bank accounts.
- Slack is written through the Slack SCIM API v2 (api.slack.com/scim/v2) with an OAuth token with the admin scope from an Owner or Admin. Users with POST, PATCH and DELETE (deactivate), reactivation with active = true; enterprise extension with employeeNumber, organization and department; startDate through urn:ietf:params:scim:schemas:extension:slack:profile:2.0:User. User groups through /Groups. Only on Business+ and Enterprise; 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 Slack | Notes |
|---|---|---|
Bedrijfscode en personeelsnummer | enterprise.employeeNumber | Number is only unique per company |
Roepnaam, tussenvoegsel en achternaam | name.givenName, name.familyName en displayName | |
Naamgevingsregel | userName | At most 21 characters |
Werk-e-mailadres | emails | |
Functie | title | |
Afdeling | enterprise.department en user group | |
Bedrijf (bv) | enterprise.organization | |
Datum in dienst | startDate (Slack-profielextensie) | |
Datum uit dienst | Deactiveren (DELETE /Users) |
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