Recruitment to HR
Carerix to HiBob integration: successful match becomes a new employee in Bob
With an integration between Carerix and HiBob, a candidate with a successful match in Carerix becomes a new employee in Bob, with start date, site, job title and department. KoppelHet checks every quarter of an hour which matches in Carerix changed status, because Carerix sends no notification itself.
What the integration does
Organisations that recruit in Carerix for their own organisation and use HiBob as their HR system enter new colleagues in Bob by hand. Bob asks for a site and start date that sit in different places in Carerix, and a department with a slightly different name makes creation fail.
- The recruiter sets the match in Carerix to a status for a successful placement.
- Every quarter of an hour KoppelHet retrieves the changed matches and takes only the successful ones.
- Work location, function and department are translated to the lists in Bob.
- KoppelHet creates the employee in Bob with site and start date.
- HR gets a task with the agreed salary and a notice when Bob rejects a value.
What to watch for with Carerix and HiBob
- Carerix marks per status whether it is a successful placement. Only matches that reach such a status become an employee in Bob. A proposal to the hiring manager or a rejection stays in Carerix.
- Bob does not create an employee without a site and start date. In Carerix the start date sits on the match and the work location on the vacancy. KoppelHet retrieves both and converts the city through a table to a site in Bob.
- Function and work unit are pick lists in Carerix and fixed lists in Bob that must match exactly. KoppelHet translates per value and reports a new Carerix function that does not yet exist in Bob, instead of letting the hire fail.
- Carerix only stores the candidate's private email address, while Bob uses the email address for login and invitations. We agree beforehand whether Bob gets the private address first or IT has already created the work address.
- The salary is free text on the match in Carerix. A salary entry in Bob needs an amount. KoppelHet therefore puts the text in a task for HR instead of guessing a salary entry.
- Carerix does not report status changes, but does record per match when the status changed. KoppelHet requests only those matches every quarter of an hour, so the integration does not put a heavy load on Carerix.
- Bob does not warn when the integration user has too few rights; fields then stay empty. After setup we check per field whether Bob really filled it.
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 new employee get an invitation to Bob right away?
Only if you want it. HR often only sends the invitation once the work email address exists.
What happens to the BSN?
It is not taken from Carerix. The employee or HR enters it in Bob, or only in payroll.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Carerix through the GraphQL API (https://api.carerix.io/graphql/v1/graphql), confidential client with client credentials and scope urn:cx/cx5Wrapper:data/crmatch:read. crMatchPage with a qualifier on statusInfoModificationDate; statusInfo.isSuccessfullyFilled; CRMatch jobStartDate and agreedSalary (String); CREmployee firstName, lastNamePrefix, lastName, emailAddress and mobileNumber; CRVacancy workCity, toFunctionLevel1 and toWorkUnitNode.
- HiBob through the People API (create employee with required email, firstName, surname, work.startDate and work.site; list fields such as work.title and work.department must have existing values). Service user with Add new people and edit rights per category.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Carerix | Field in HiBob | Notes |
|---|---|---|
CREmployee firstName | firstName | |
CREmployee lastNamePrefix en lastName | surname | Name prefix at the front of the surname |
CREmployee emailAddress | email | Private address, until the work address is known |
CREmployee mobileNumber | Persoonlijk mobiel nummer | |
CRMatch jobStartDate | work.startDate | |
CRVacancy workCity | work.site | Through a lookup table |
CRVacancy toFunctionLevel1 | work.title | |
CRVacancy toWorkUnitNode | work.department |
Related
Carerix → ADP Workforce Now
Carerix to ADP Workforce Now integration: placement in North America as an in-progress hire
Carerix → AFAS Profit
Carerix to AFAS integration: a placed candidate starts onboarding in AFAS Profit
Carerix → BambooHR
Carerix to BambooHR integration: successful placement as an employee with employment status in BambooHR
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce