Recruitment to HR
Jobvite to HiBob integration: hired candidates as new employees in Bob
With an integration between Jobvite and HiBob, a candidate hired in Jobvite becomes a new employee in Bob, with name, email, start date, site, department and job title. KoppelHet then checks that all fields in Bob were filled and notifies HR when something is missing.
What the integration does
Organisations that recruit in Jobvite and use Bob from HiBob as their HR system often retype hires. Where it gets stuck is that site, department and job title in Bob only accept existing list values, while recruiters in Jobvite use other names.
- We put the sites and departments from Bob into Jobvite as locations and departments.
- The recruiter hires the candidate in Jobvite on a requisition with those values.
- KoppelHet creates the new employee in Bob.
- KoppelHet reads the employee back and checks whether all fields were filled.
- If something is missing, HR gets a notice with the Jobvite line attached.
What to watch for with Jobvite and HiBob
- Bob rejects a new employee without site and start date, and site, department and job title must be existing list values. Jobvite can import locations and departments through a CSV import with code and name. If we load Bob's lists there, the values line up.
- According to HiBob's API documentation, Bob gives no warning if an integration's user only has rights for part of the fields. A hire can therefore succeed while the job title stays empty. KoppelHet reads every new employee back and compares the fields with the Jobvite line.
- Besides new hires, Jobvite's new hire file also contains rehires and internal transfers. In Bob an internal transfer is a new work entry for an existing employee, not a new person. KoppelHet only creates an employee for new hires.
- With a start date in the future, tenure fields in Bob stay at zero until that date. Bob reports on tenure therefore only count a hire from the first working day, even if Jobvite passed it on weeks earlier.
- The Jobvite file contains US fields such as race and veteran status. These do not go to Bob; KoppelHet drops them on reading, so they never end up in Dutch HR records.
- A search in Bob leaves out former employees by default, and filtering is only possible on ID or email. For a rehire from Jobvite KoppelHet therefore searches by email address with inactive employees included. That way the integration recognises a former colleague and does not create a second person.
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?
No. HR sends it once the work email exists.
Does the BSN come from Jobvite?
No. 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.
- KoppelHet reads the Jobvite New Hire Export file (CSV through SFTP at Jobvite, optionally PGP; New Hire, Rehire and Internal Transfer). To Bob through POST /v1/people with email, firstName, surname, work.site and work.startDate (required) plus work.title and work.department as existing list values. Jobvite issues API key and secret through Jobvite support. Service user with Add new people to the company and edit rights per category.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Jobvite | Field in HiBob | Notes |
|---|---|---|
Sollicitatie-ID uit Jobvite | Eigen veld in Bob | To process a hire only once |
Voornaam en achternaam | firstName en surname | |
E-mail van de kandidaat | email | Required in Bob |
Startdatum | work.startDate | |
Locatie van de requisition | work.site | Required; existing sites only |
Afdeling van de requisition | work.department | |
Functietitel van de requisition | work.title | Existing list values only |
Related
Jobvite → Personio
Jobvite to Personio integration: hires from the Jobvite file as employees in onboarding
Jobvite → SAP SuccessFactors
Jobvite to SAP SuccessFactors integration: hires from the Jobvite file as employees in Employee Central
Jobvite → Workday
Jobvite to Workday integration: Jobvite's new hire file as pre-hires in Workday
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob