Service · Software development

Build a Recruitee integration.

Recruitee is a strong ATS for the Dutch market, but it sits apart from your HR, payroll and CRM systems. We build the integrations that let candidates flow automatically into AFAS, Personio, Nmbrs, HubSpot and the rest of your stack — with clear field mapping, an audit trail and GDPR checks.

Recruitee APIAFAS integrationWebhooksBi-directional sync

An ATS is only valuable when it keeps pace with the rest.

Recruitee (part of Tellent) is the standard for recruitment at hundreds of Dutch organisations. It's pleasant for recruiters to use, offers a clean API and, in our experience, is one of the easiest ATSs to integrate with. But once a candidate is hired, the real work begins: creating the employee in AFAS or Personio, informing payroll via Nmbrs or Loket, getting the contract signed via DocuSign, and scheduling calendars in Microsoft 365 or Google Workspace.

Without an integration, someone does all of that by hand — with double entry, error-prone field mapping and delays in onboarding. In growing organisations, that quickly becomes an invisible burden on the recruiter and on HR. We build the Recruitee integrations that complete your flow, with attention to what you should and shouldn't sync under the GDPR. For clients who need their own custom recruitment layer alongside Recruitee, we combine both tracks in a single architecture.

The Recruitee REST API and webhook events form the foundation. Around them, we build a thin integration layer that handles the transformations (field mapping, normalisation of address and name data), takes care of retries for systems that occasionally falter, and keeps an audit trail that both your IT team and your data protection officer can use. Not a middleware platform with a separate licence, but your own integration in your stack, with no vendor lock-in.

Three types of Recruitee integration.

Most of the questions we receive fall into one of these three types. Which one fits depends on where your candidate data needs to go and how much room there is for error.

Hire flow · fixed sprint budget

Connecting Recruitee to AFAS, Personio or Nmbrs

The classic: a candidate is set to "Hired" in Recruitee and must then land as an employee in your HR or payroll system. We build the field mapping, trigger it via webhook or polling, and add re-checks so you don't end up with duplicates or half-created records.

Recruitee → AFASRecruitee → PersonioRecruitee → NmbrsRecruitee → LoketRecruitee → Visma
Operational flow · fixed sprint budget

Connecting Recruitee to your CRM, calendar and communication tools

Everything that needs to keep pace during the recruitment process: new applications as notifications in Slack or Teams, interview invitations automatically in Microsoft 365 or Google Workspace, and lead tracking via HubSpot or Salesforce for recruitment agencies that treat candidates as a sales process.

Slack notificationsTeams alertsOutlook calendarHubSpot syncSalesforce leads
Enterprise / multi-tenant · fixed sprint budget

Recruitee within a larger HR or staffing stack

For organisations with BambooHR, Workday or their own secondment platform: Recruitee as one source in a larger stack, with bi-directional sync, document flow via DocuSign or AdobeSign, and multi-tenant support for recruitment agencies that manage multiple clients within a single Recruitee environment.

BambooHRWorkdayDocuSignAdobeSignMulti-tenant

What you get at the end.

A working integration between Recruitee and your systems, plus everything around it so you can manage it yourself when a field is added or a new employee is hired.

  • The integration itselfA production and staging environment, running on your cloud (GCP, AWS, Azure) or with us. Stateless where possible, with a retry queue for anything that has to wait on a slow-responding system.
  • Field mapping documentA readable overview of which Recruitee field maps to which target field, including conversions, defaults and the choices made around personal and BSN data. Written for both your HR team and your data protection officer.
  • Audit trail and monitoringEvery sync is logged: which record, which field, which target system, and what the response was. Your IT team gets a dashboard with error rates, and your recruiter gets a simple status per candidate.
  • Error handling and retry flowWhat does the integration do when AFAS is briefly unavailable? What if a required field in Personio turns out to be empty? We document every failure path and build in recovery actions, not just a log line.
  • Codebase + documentationFull source code in your own repository, with build and deploy instructions and an architecture overview. No vendor lock-in: another party can pick it up from here.
  • Maintenance contract (optional)Monitoring, retries, version updates for the Recruitee and target system APIs, and further development when a new integration is added. Fixed monthly price, agreed with you.

When a Recruitee integration is the right choice.

Four patterns we help clients with. If you recognise one, we'd be glad to talk it through.

Onboarding speed

Double entry on every hire

A recruiter sets the status to "Hired", and the same person is then created by hand in AFAS or Personio. With more than a handful of hires a month, that wastes time and becomes a source of errors in address details, contract type or start date.

Payroll flow

Nmbrs or Loket lags behind

Payroll only sees new employees once HR fills in the payslip template. One forgotten candidate means a correction batch in the next period. A direct sync from Recruitee prevents that pattern.

Recruitment as sales

Candidates are leads too

For temp, secondment and recruitment agencies, every candidate is also a potential deal record. HubSpot or Salesforce needs to know who has which status, and you want reports per account manager. A one-way or bi-directional integration with Recruitee makes that possible.

Compliance

The GDPR question gets sharper

Which personal data flows to which system, at what moment, and on what legal basis? A well-thought-out Recruitee integration makes that explicit, and offers controls to limit or anonymise data where appropriate.

How a Recruitee integration project runs.

1

Introduction and scope

A conversation in which we look at which systems Recruitee needs to serve, which triggers are required (application received, status change, hire event) and what requirements your HR and compliance teams bring. We also discuss what stays in scope and what we explicitly leave out, so the first delivery doesn't balloon. At the end: a set-up with clear choices and a proposal.

2

Field mapping and data audit

A short workshop with your recruiter and your HR or payroll employee to map Recruitee fields to AFAS, Personio or Nmbrs fields. This is where we catch the small differences: how "tussenvoegsel" (name prefix) is stored, what we do with BSN (citizen service numbers), and how we handle part-time percentages and agency contracts. The outcome is a readable mapping document that your data protection officer can also review.

3

Building in sprints

Every two weeks you get a working build you can test, with the first integration often already running in a verifiable environment after a few sprints. We work iteratively: one target system done properly first, then the next. No big bang. Each sprint we show what has been built in a short demo, and you can follow along with the test data yourself.

4

Pilot phase with real hires

Before we switch the integration on for all vacancies, it first runs on a limited set: one department, one contract type or one region. This brings edge cases to light (volunteers, interns, external consultants, payroll staff) without them immediately affecting production. Whatever we discover during the pilot, we resolve before the wider rollout.

5

Rollout and maintenance

Full rollout, training for your recruiters and HR team on what is visible in the audit trail, and a runbook for your IT department with escalation paths. Optionally a maintenance agreement for the years afterwards, because Recruitee, AFAS, Personio and Nmbrs all roll out updates that we need to keep monitoring. We pick up updates without you having to keep an eye on them yourself.

Tools and techniques we work with.

A Recruitee integration is not a black box. Below is what we use under the hood, so your IT team knows what they will be managing.

Recruitee side

API and webhooks

The Recruitee REST API for reading and updating candidates, vacancies and custom fields. Webhook events for near-real-time triggers on status changes, which are faster and more reliable than polling. OAuth tokens with scoped permissions rather than a main account.

Target systems

HR, payroll and CRM APIs

AFAS GetConnector and UpdateConnector, Personio API, Nmbrs SOAP, Loket REST, Visma, HubSpot, Salesforce, BambooHR and Workday. For each target we know the quirks: rate limits, mandatory fields, how they handle dates, and which error codes signal what.

Document flow

DocuSign, AdobeSign, Microsoft 365

For clients who want to send the employment contract straight after hiring: a DocuSign or AdobeSign integration that generates contracts from the Recruitee candidate data, with job title, salary and start date pre-filled. Notifications via Microsoft 365, Teams, Slack or Google Workspace.

Architecture

Stateless or queue-based

Simple integrations run stateless: webhook in, transformation, target API out. For heavier or bursty flows we use a queue (RabbitMQ, Cloud Tasks, SQS) so we can retry after a failure. Monitoring runs via your existing stack or a lightweight dashboard that we build. Also read about our broader approach to smart API integrations.

GDPR, security and which data to sync or not.

Candidate data is highly sensitive. A Recruitee integration needs to handle it deliberately, not push everything through automatically "because it can".

  • Legal basis per fieldFor every Recruitee field we sync, we record the legal basis (employment contract, legal obligation, legitimate interest). That way your data protection officer knows exactly which processing takes place on which basis.
  • Selective syncingBy default we only sync what the target system needs. Open answers from an application form, photos and interviewer feedback stay in Recruitee. What goes to HR is a deliberate choice.
  • Rejected candidatesFor candidates who are not hired, the hire sync does not run. Their data stays within Recruitee under your organisation's regular retention policy. No creeping processing into systems where it doesn't belong.
  • Encryption and access controlConnections run over TLS, secrets are stored in a secrets manager (Vault, AWS Secrets Manager, GCP Secret Manager), and only the integration process itself has access to the API tokens. No tokens in code or in log lines.
  • Access and rectification requestsIf a (former) candidate makes a GDPR request, you can see in a single overview which systems their data has gone to. The audit trail makes it possible to erase or correct data in a targeted way.

Multi-tenant scenarios for agencies.

A specific case we see regularly: recruitment, secondment or staffing agencies that recruit for multiple clients within a single Recruitee environment. Different rules apply there.

Client separation

A separate sync route per client

One client uses AFAS, the next Personio, a third its own HR system. We build a routing layer that uses vacancy or label metadata to determine which integration should run for which candidate. One Recruitee, multiple target systems, no cross-contamination.

Separate mapping per client

Not all clients are the same

Client A wants start date and cost centre, client B only the job title. We make the mapping configurable per client instead of hard-coded, so onboarding a new client doesn't have to mean a new development project.

Reporting and invoicing

Connecting to your own administration

Many agencies want hires to land automatically in their own CRM or invoicing tool for placement fees. We link Recruitee status changes to your own workflow, optionally combined with your own secondment platform.

Client visibility

Optional client portal

Some agencies want to give clients insight into which candidates are at which stage. This is possible with a protected portal that reads from Recruitee — a pattern that is often added on top of the basic integration.

Frequently asked questions.

What clients usually want to know before we start on a Recruitee integration.

Can you integrate Recruitee with AFAS?
Yes. AFAS is one of the most requested target systems for Recruitee integrations in the Netherlands. We work with the AFAS GetConnector and UpdateConnector APIs and map candidate fields from Recruitee (name, address, contract type, start date) to the right AFAS employee fields. Common pitfalls — name prefixes, BSN (Dutch citizen service number), contract types, cost centres — are covered in the field mapping session.
What about integrating Recruitee with Personio or Nmbrs?
Both have an open REST API and are standard integrations for us. Personio is stronger for internationally operating companies; Nmbrs is common in the Netherlands for payroll administration. For both, we use the hire trigger from Recruitee as the starting point, and we build the retry logic so that a temporary outage on the other side doesn't lose a candidate.
Can you also integrate ATSes other than Recruitee?
Yes. The same approach works for BulletJobs, OTYS, Carerix, BambooHR, Workday and other systems. The Recruitee page exists because it is the most requested route among Dutch SMEs and mid-market organisations, but we are not tied to a single vendor. For custom recruitment software, you can also take a look at our page on custom recruitment software.
What do you do with custom fields in Recruitee?
Recruitee lets you define your own fields on candidates and vacancies. We include these in the mapping. During the workshop we look at which custom fields you use, which of them are worth passing on to the target system, and what we do if a field is empty or filled in inconsistently.
How do you handle GDPR compliance when syncing candidate data?
Three principles: only the fields needed for the target system, an explicit legal basis for every sync (usually employment contract or legitimate interest), and an audit trail that shows when which data was passed on. For larger projects we contribute a short DPIA (data protection impact assessment) to your data protection officer. Rejected candidates stay in Recruitee — we don't sync that data by default.
What determines the cost and lead time?
Mainly: the number of target systems, the complexity of the field mapping (especially custom fields and contract types), whether you need bi-directional sync, and whether a document flow (DocuSign, AdobeSign) is involved. A straightforward Recruitee-to-AFAS integration takes a few sprints; a multi-tenant integration with several target systems and bi-directional sync takes considerably more work. After the scoping session, we'll give you a well-founded estimate.
Do we have to handle maintenance ourselves, or do you do that?
Either works. You always get the full codebase in your own repository, plus documentation. Many clients opt for a light maintenance agreement, because both Recruitee and the target system (AFAS, Personio, Nmbrs) roll out API updates regularly and someone needs to keep an eye on them. It's a fixed monthly arrangement, not tied to hours.

Talk to us about your Recruitee integration.

A no-obligation introductory call of half an hour. Tell us which systems Recruitee needs to serve and which flow is currently stuck, and we'll come back with an initial direction. We build Recruitee integrations as standalone projects and as part of broader enterprise software implementations or an Exact Online integration.

Edit content