Integrations
Integrations that help prevent duplicate work
We are working out which links to HR, payroll and calendar software would save our first customers the most work. None of them is ready yet.
What the statuses mean
Each integration shows how far we have got. Right now, everything is still at research.
The integration works and is supported in this product phase.
The integration runs at a handful of organisations. That is how we find out whether it holds up in practice.
We have decided to build this integration. There is no release date yet.
We are working out where the need lies, which data would move back and forth and what that means for privacy. Nothing has been built yet.
HR and payroll
Nmbrs
Being researchedWe are looking at whether employees and departments could carry over from Nmbrs, so you do not have to enter them twice.
Loket.nl
Being researchedWe are looking into whether basic employee and team data from Loket.nl could stay up to date on its own.
AFAS
Being researchedHR processes and master data are often already held in AFAS. We are looking into whether Absentra could connect to that.
Exact
Being researchedWe are looking at whether you could reuse organisation and employee data from Exact.
Sign-in and access
Microsoft Entra ID
Being researchedSigning in with the work account people already have (SSO) and managing access from one place: we are working out whether that is possible.
Google Workspace
Being researchedWorking with Google? We are looking at sign-in and user management through Workspace.
Collaboration and calendar
Microsoft 365
Being researchedWe are looking into whether Absentra could connect to the Microsoft environment you already work in.
Microsoft Teams
Being researchedWe are looking at whether Absentra could flag an outstanding administrative action in Teams.
Such a message would never contain medical information, only the fact that a task is waiting.
Outlook-agenda
Being researchedWe are looking into whether administrative appointments could go straight into the Outlook calendar.
Such a calendar item would hold no medical information, only the appointment itself.
Google Calendar
Being researchedFor Google Calendar we are looking at the same thing: appointments that turn up in the calendar on their own.
Such a calendar item would hold no medical information, only the appointment itself.
How we build an integration
From question to production. At every step we look at privacy again.
- 1
Hear what is needed
Integration requests and pilot conversations tell us which link gets asked for most.
- 2
Draw the data boundaries
We set out which administrative data an integration needs. And, above all, which it does not.
- 3
Check privacy and security
We hold every integration to two rules: as little data as possible, and nothing medical.
- 4
Technical pilot
An integration first runs at a handful of organisations, in a guided pilot.
- 5
Available only when it works
Does the integration hold up in practice? Then we set the status to available, and not before.
Frequently asked questions about integrations
None yet. Everything on the integrations page is marked “Being researched”, from HR and payroll packages to single sign-on and calendars. We show the status per integration and call nothing available until it has been validated.
Choose “Integration request” in the contact form and put the product name of the system you want to connect in the “Current system” field. Do not share exports, screenshots or employee data.
Not yet. Signing in through Microsoft Entra ID and Google Workspace is part of our integration research.
We deliberately do not name release dates. An integration first goes through needs research, a privacy and security assessment and a technical pilot. The current status is always shown on the integrations page.
More questions? See all frequently asked questions.
Which integration would help your team?
Let us know through the contact form. Give us the name of your system, and please do not send exports or employee data.