Integrations
Integrations that help prevent duplicate work
Absentra is researching which HR, payroll, identity and calendar integrations deliver the most value for its first customers.
What the statuses mean
We show the status of every integration transparently. At this moment all listed integrations are being researched; none is available yet.
The integration is available and supported in the current product phase.
The integration works for a limited number of pilot organizations, where it is being validated.
A product decision has been made; the integration is on the roadmap, without a fixed release date.
We are researching the need, the data flow and the privacy impact. No integration is available yet.
HR and payroll
Nmbrs
Being researchedResearching how to reuse employee and department data to avoid duplicate entry.
Loket.nl
Being researchedResearching synchronization of basic employee and team data.
AFAS
Being researchedResearching alignment with existing HR processes and master data.
Exact
Being researchedResearching reuse of organization and employee data.
Identity and access
Microsoft Entra ID
Being researchedResearching secure single sign-on (SSO) and central management of user access.
Google Workspace
Being researchedResearching single sign-on and user management for organizations working with Google.
Collaboration and calendar
Microsoft 365
Being researchedResearching alignment with the existing Microsoft work environment.
Microsoft Teams
Being researchedResearching notifications about outstanding administrative actions.
Notifications would never contain medical information; only administrative task information.
Outlook-agenda
Being researchedResearching calendar items for administrative contact moments.
Calendar items would never contain medical information; only process appointments.
Google Calendar
Being researchedResearching calendar items for administrative contact moments.
Calendar items would never contain medical information; only process appointments.
How we develop an integration
From need to production, with privacy as a fixed checkpoint.
- 1
Collect needs
Through integration requests and pilot conversations we determine which integrations deliver the most value.
- 2
Define the data flow
We establish exactly which administrative data an integration needs — and which it does not.
- 3
Assess privacy and security impact
Every integration is tested against data minimization and the non-medical scope of Absentra.
- 4
Technical pilot
An integration first runs with a limited number of organizations in a guided pilot.
- 5
Production support after validation
Only when an integration has been validated in practice is it presented as available.
Frequently asked questions about integrations
None yet. All integrations on the integrations page — such as HR and payroll packages, single sign-on and calendars — have the status 'Being researched'. We show the status per integration transparently and present nothing as available before it has been validated.
Choose 'Integration request' in the contact form and mention the product name of the system you would like to connect in the 'Current system' field. Do not share exports, screenshots or employee data.
Not yet. We are researching single sign-on via Microsoft Entra ID and Google Workspace as part of the 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?
Report your integration need through the contact form. Mention only the product name of your system; do not share exports or employee data.