Recruitment to HR
Recruitee to HoorayHR integration: hired candidates as employees in HoorayHR
With an integration between Recruitee and HoorayHR, a candidate hired in Recruitee becomes a new employee in HoorayHR, with name, email and start date, so HR can finish contract and employment terms there. With several entities KoppelHet picks the right entity and translates the job's department to a team.
What the integration does
Organisations that recruit in Recruitee and use HoorayHR for personnel files, leave and sickness absence often transfer hires by hand. If the organisation works with several entities, HR also has to pick the right entity and team.
- KoppelHet gets an API key from an administrator in HoorayHR, and Recruitee gets a webhook to KoppelHet.
- The recruiter moves the candidate to a stage with the hire category.
- The employee arrives in HoorayHR with status not invited.
- HR adds contract and employment terms in HoorayHR.
- An administrator sends the invitation from HoorayHR.
What to watch for with Recruitee and HoorayHR
- The HoorayHR API key belongs to an administrator and has an expiry date. KoppelHet therefore uses a fixed integration account, so the integration does not stop when a colleague leaves.
- An employee added to HoorayHR through the API always has the status not invited. Only when an administrator sends the invitation in HoorayHR can the new colleague log in; HR decides when.
- Contracts and employment terms, such as salary and working hours, can only be read in HoorayHR's public API. An integration therefore cannot fill them; that remains HR's work in HoorayHR.
- Employees can be created in the HoorayHR API but not changed. If the start date moves after the hire, HR adjusts it in HoorayHR; the integration cannot do that automatically.
- HoorayHR has entities and teams, but no fixed field for department. KoppelHet picks the entity based on the placement location in Recruitee and translates the job's department to a team.
- HoorayHR stores a name in parts: first name, name particle in insertion and last name, and builds the display name from those itself. Recruitee has one name field. KoppelHet puts the name particle separately in insertion, so someone named Van Dijk is listed correctly in HoorayHR.
- In HoorayHR the teams field is a text with a list of team IDs, such as "[1, 2, 3]", not a team name. For the department from Recruitee KoppelHet looks up the team ID through /teams-information and sends it in that form.
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
Does the salary from Recruitee reach HoorayHR?
No. Employment terms cannot be written through the HoorayHR API, so HR fills them in HoorayHR.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Recruitee through the candidate_moved webhook to a stage with the hire category (HMAC SHA-256 in X-Recruitee-Signature, up to nine retries) and writes to HoorayHR with POST /users (email required; firstName, lastName, entityId, teams as a list of team IDs, companyStartDate). API key of an administrator with an expiry date.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in HoorayHR | Notes |
|---|---|---|
name | firstName, insertion en lastName | Name particle separately in insertion |
Zakelijk e-mailadres (profielveld) | email | Required in HoorayHR |
Startdatum (profielveld) | companyStartDate | |
Plaatsingslocatie of vacature | entityId | With several entities |
Afdeling van de vacature | teams | List of team IDs |
Kandidaat-ID | Logging in het KoppelHet platform |
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