Identity and access management
AFAS to JumpCloud integration: employees from AFAS Profit as users in JumpCloud
With an integration between AFAS Profit and JumpCloud, JumpCloud's Custom API import fetches every employee from AFAS as a user, with job title, department, employer and a status that follows from the start and end dates. KoppelHet delivers AFAS in the form JumpCloud can read, so a new colleague is ready and a leaver is suspended on time.
What the integration does
Organisations that have AFAS Profit as their HR system and use JumpCloud for accounts, SSO and devices often add new employees to JumpCloud by hand or with a CSV file, and only suspends leavers when the manager remembers.
- The AFAS administrator creates a dedicated app connector for KoppelHet, with one GetConnector holding only the fields for JumpCloud.
- KoppelHet reads AFAS for changes and prepares one record per employee on its own secured address.
- In JumpCloud we set up the Custom API import on that address, with the mapping and a status rule on the dates.
- We check with Preview Mappings, switch on a scheduled import and link the users to groups with their applications.
- After the end date JumpCloud suspends the user; KoppelHet monitors whether every import succeeds.
What to watch for with AFAS Profit and JumpCloud
- Without skip and take, an AFAS GetConnector only returns the first hundred rows, and AFAS advises against fetching everything at once. JumpCloud's Custom API import supports limit, pageSize, count and size for the page size, but not take. KoppelHet therefore offers its own address with paging JumpCloud understands.
- JumpCloud can read an API with a fixed header itself, and AFAS works with an AfasToken in the Authorization header. Still, we do not give JumpCloud an AFAS token. That token could reach the whole GetConnector; JumpCloud only gets its own key for KoppelHet's address.
- Work email and username are required in the JumpCloud import. For a new employee the work email in AFAS is often still empty. KoppelHet then fills in the address according to your naming rule, so the user is still created.
- A new employee is often in AFAS weeks before the first working day. KoppelHet passes the start date along, and the status rule in JumpCloud keeps the user staged until that day. According to JumpCloud, a staged user has no access to assigned applications yet.
- A user who has once been active cannot go back to staged in JumpCloud. If HR withdraws a hire in AFAS after the start date, the rule sets the user to suspended; KoppelHet reports it to IT.
- In AFAS the employer sits on the contract. With several administrations, KoppelHet supplies the employer of the current contract as company, so a move to another company keeps the same JumpCloud user and only changes the group membership.
- AFAS keeps the name prefix and surname separate. KoppelHet joins them into the surname in JumpCloud, so apps behind JumpCloud show "Jan van Dijk" and not "Jan Dijk".
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
Is a leaver deleted from JumpCloud?
No, suspended. According to JumpCloud, suspension immediately revokes access to everything provided through JumpCloud; deleting remains a step for IT.
How often does JumpCloud fetch the data?
A scheduled import is off by default. We switch it on at go-live, usually hourly.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS is read with a dedicated GetConnector under its own app connector (header Authorization: AfasToken with the token in Base64), with skip, take and a fixed sort order, filtered on modification date. Response as JSON with skip, take and rows.
- JumpCloud: Custom API import (HR Directories) with Bearer Token or API Key on the KoppelHet address, method GET, Resource Location pointing at the list of users, offset paging with limit and offset; required mapping Company email and Username; State through EXPR with manageUserState (STAGED, ACTIVATED, SUSPENDED) and date functions such as today() and dateAfter(); scheduled import hourly, daily or custom.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in JumpCloud | Notes |
|---|---|---|
Medewerker (EmId) | employeeIdentifier | Key between both systems |
E-mail werk | Company email en Username | Required in JumpCloud |
Roepnaam en voorvoegsel + achternaam | firstname en lastname | |
Functie (omschrijving) | jobTitle | |
Organisatorische eenheid | department | |
Werkgever | company | |
Kostenplaats | costCenter | |
Datum in dienst en datum uit dienst | State via manageUserState | Staged, active or suspended |
Related
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit
AFAS Profit → AG5
AFAS to AG5 integration: employees, employments and absence from AFAS Profit in the skills matrix