Recruitment to HR
Recruitee to Yoobi integration: new colleagues ready for planning in Yoobi
With an integration between Recruitee and Yoobi, a candidate hired in Recruitee automatically appears as an employee in Yoobi, with employee number, start date, department, job title and login email. Project leads can schedule the new colleague before the first working day, without waiting for someone to add them to Yoobi.
What the integration does
Organisations that keep hours, projects and planning in Yoobi and recruit in Recruitee create every new colleague in Yoobi by hand. Until that happens, nobody can assign the new colleague to a project, and they log no hours in the first week.
- The recruiter marks the candidate as hired in Recruitee.
- KoppelHet determines the employee number, as agreed with HR or payroll.
- The new colleague appears in Yoobi with department, job title, start date and login email.
- The Yoobi administrator sets the contract hours; after that the colleague can be scheduled.
What to watch for with Recruitee and Yoobi
- Yoobi asks for an employee number for a new employee, and Recruitee has none. We agree whether HR puts the number in Recruitee or KoppelHet picks the next free number, so it matches payroll later.
- Through the API Yoobi can only return contracts, not create them. The contract hours planning needs are therefore set by the Yoobi administrator; KoppelHet turns that into a task.
- There is a Zapier template that creates hired Recruitee candidates as Yoobi employees. It works per company account and without checks for duplicate employees or a fixed employee number.
- Yoobi's API works directly on production data and has no separate test environment. We therefore test with one test candidate and an API user that may only create and read employees.
- Yoobi splits a name into first name, prefix and surname, Recruitee has one name field. KoppelHet extracts Dutch prefixes such as van or de, so the colleague sorts correctly in Yoobi.
- The email address in Yoobi is what the colleague logs in with and uses to log hours. It has to be the work address, so HR sets it in advance as a profile field in Recruitee.
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
Why not use the Zapier template?
That works for a few hires a year. If you want a fixed employee number and a check for duplicate employees, you need more.
Are contract hours included?
No, Yoobi's API cannot create contracts. The administrator sets them, and KoppelHet creates a task for it.
Can Yoobi then feed payroll?
Yes, as a separate integration: hours from Yoobi to for example Nmbrs or AFAS. That can follow later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee is read through the signed candidate_moved webhook to a stage with the hire category (X-Recruitee-Signature header) and the ATS API for candidate, offer and profile fields.
- To Yoobi through the Yoobi REST API (RAML and JSON), which is switched on per organisation. Separate API user with per-method rights, only creating and retrieving employees; contracts can only be retrieved through the API.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Yoobi | Notes |
|---|---|---|
name | Voornaam, tussenvoegsel en achternaam | We split the single Recruitee name field, with the surname prefix separately |
Personeelsnummer (uit HR of door KoppelHet uitgegeven) | Personeelsnummer | Mandatory in Yoobi |
Startdatum (profielveld) | Startdatum | |
offer.department | Afdeling | Through the departments that exist in Yoobi |
Functie (profielveld) | Functie | |
Zakelijk e-mailadres (profielveld) | Gebruikers-e-mail | |
Profielveld gender | Geslacht |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AFAS Profit
Recruitee to AFAS integration: from hired candidate to new employee
Recruitee → AlexisHR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
Recruitee → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping