Recruitment to HR
Recruitee to HiBob integration: from offer to employee with a welcome wizard
With an integration between Recruitee and HiBob, a candidate hired in Recruitee automatically appears as a new employee in Bob, with site, start date, department, job title and salary. People Ops no longer retypes anything, and the new colleague can get the right welcome wizard in Bob straight away.
What the integration does
Organisations with HiBob for HR and Recruitee for recruiting retype every hired candidate into Bob, choosing site and department from the list, before onboarding starts. In a busy hiring period that falls behind and the welcome email only arrives just before the first day.
- KoppelHet keeps the lists of sites, departments and job titles from Bob up to date, so everything from Recruitee maps to an existing value.
- The recruiter marks the candidate as hired in Recruitee.
- The new employee then appears in Bob, with site, start date, department and job title.
- The salary from the offer is in Bob, with the start date as the effective date.
- If you want, the new colleague immediately gets the welcome wizard that belongs to the site or department.
What to watch for with Recruitee and HiBob
- Bob does not accept a new employee without email, first name, surname, site and start date. Site and start date are not standard in Recruitee; we add them to the offer form or derive the site from the placement location.
- Site, department and title are fixed lists in Bob. A department named slightly differently in Recruitee makes the creation fail. KoppelHet therefore always translates through the current lists from Bob.
- Recruitee only knows the candidate's private email address, while Bob uses the email address for login and invitations. We agree whether the work address is set in advance or whether Bob gets the private address first.
- The salary in Recruitee is an amount with currency. In Bob it becomes a salary entry with the start date as the effective date and the pay period you use in Bob.
- Bob gives no warning if the integration has rights to only some of the fields. After setup we therefore test whether every field is actually filled, otherwise the salary, for example, is missing without an error.
- HiBob has its own hiring module. If you keep recruiting in Recruitee, vacancies and pipelines stay there; the integration only starts at the hire.
- Each site or department in Bob can have a different welcome wizard. KoppelHet picks it based on the data from 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 HiBob's own hiring module?
That is an option. If you already use Recruitee and are happy with it, you do not have to switch; the integration makes Bob complete from day one.
Does the new hire get an invitation automatically?
Only if you want it. Some customers let People Ops check first and send the invitation themselves.
Does this work for offices outside the Netherlands?
Yes. The placement location in Recruitee determines the site in Bob, so each office gets its own site.
What happens with the BSN?
It is not sent from Recruitee. The employee or People Ops enters it in Bob, or only in the Dutch payroll.
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 candidate_moved webhook and the ATS API (name, emails, phones, placement_locations, offer.department and profile fields for start date, title, salary and address).
- HiBob is written through the People API (create employee with firstName, surname, email and the Work table work.site, work.startDate, work.department, work.title), then an entry in the salary table and optionally an invitation with a welcome wizard.
- The Bob service user has permissions per field; Bob omits fields without permission without an error.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in HiBob | Notes |
|---|---|---|
name | firstName, surname | We split the single Recruitee name field into first name and surname |
emails[0] | email | Bob requires an email address on creation; usually the work address, otherwise the private one for now |
phones[0] | home.mobilePhone | |
placement_locations[0] | work.site | Recruitee placement location to an existing site in Bob |
Startdatum (profielveld) | work.startDate | |
offer.department | work.department | Must match a value in the Bob list exactly |
Functie (profielveld) | work.title | |
Profielveld salary (amount, currency) | Salaristabel: bedrag en valuta | |
Profielveld address | Privéadres in Bob | One text line from Recruitee, split into the address fields in Bob |
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