Recruitment to HR
Recruitee to BuddeeHR integration: hired candidates as employees in BuddeeHR
With an integration between Recruitee and BuddeeHR, a candidate hired in Recruitee becomes a new employee in Buddee, with name, employment date and first day at work, and also position, manager, buddy, contract and salary. If several employers work in Buddee, KoppelHet puts the new colleague in the right company straight away.
What the integration does
Organisations that recruit in Recruitee and use BuddeeHR for personnel files, leave and payroll preparation enter position, manager and contract for every hire by hand in Buddee. With several employers HR also has to move each new colleague to the right company.
- HR creates the custom fields start_date and first_day_at_work_date in Recruitee.
- The recruiter fills those fields and marks the candidate as hired.
- KoppelHet creates the employee in the right company in Buddee.
- Employment, position, contract and salary follow.
- HR sends the invitation from Buddee.
What to watch for with Recruitee and BuddeeHR
- A new employee in Buddee requires an employment date and a first day at work, and they can differ, for example when someone joins on a Sunday. KoppelHet reads both from a custom field in Recruitee.
- Buddee always creates an employee within a company. If the organisation works with several employers in Buddee, KoppelHet picks the company based on the placement location or job in Recruitee.
- Buddee stores the name particle separately from the last name, while Recruitee has one name field. KoppelHet splits the name, so someone named De Vries sorts correctly in Buddee and later in payroll.
- Buddee has a manager, an HR manager and a buddy per employee who guides the new colleague in the first weeks. KoppelHet fills the manager from a profile field in Recruitee; HR picks the buddy, or it also comes from a profile field.
- Access to the Buddee API runs through a normal user account with email and password. We create a separate integration account, so the integration does not stop when an HR employee leaves.
- Buddee only sends an invitation if the employee has a work or personal email address, and for each invitation you choose which of the two: business or personal. Both addresses come along from Recruitee, so HR can invite the new colleague on the work address straight after the hire.
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 two dates in Recruitee?
Buddee asks for both the employment date and the first day at work. Without those fields the candidate does not reach Buddee.
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) and writes to Buddee through the REST API (employee with company_id, first_name, last_name, employment_date and first_day_at_work_date required; further last_name_prefix, work_email, personal_email, manager_id, hr_manager_id and buddy_id). Sign-in with basic auth on /auth/token and then a JWT as bearer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in BuddeeHR | Notes |
|---|---|---|
name | first_name, last_name_prefix en last_name | Name particle separately |
emails[0] | personal_email | |
Zakelijk e-mailadres (profielveld) | work_email | |
Custom field start_date | employment_date | |
Custom field first_day_at_work_date | first_day_at_work_date | |
Plaatsingslocatie of vacature | company_id | With several employers |
Leidinggevende (profielveld) | manager_id |
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