Recruitment to HR
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
With an integration between Bullhorn and HiBob, an approved placement of a candidate who joins your payroll becomes a new employee in Bob, with start date, your own site, department and job title. Contractors and placements through an umbrella company stay out of Bob, and a second placement of the same person does not become a second employee.
What the integration does
Organisations that place consultants or seconded staff through Bullhorn and manage their own workforce in Bob from HiBob enter every new colleague in Bob by hand. The placement names the client where someone works, while Bob wants your own site, and contractors do not belong in Bob as employees.
- The recruiter sets the Placement in Bullhorn to approved.
- KoppelHet reads the placement from the event queue and keeps only your own employees.
- If the candidate is not yet in Bob, KoppelHet creates the employee with your own site.
- KoppelHet reads the employee back and checks whether all fields were filled.
- On a second placement or a termination, HR gets a notice.
What to watch for with Bullhorn and HiBob
- Bob wants a site from its own list for a new employee. A placement in Bullhorn belongs to an assignment at a client, so the work address is the client's. KoppelHet therefore sets the site of your own office in Bob, determined with a table, and never the client's address.
- A Placement in Bullhorn gets the status Placed by default, and can then become Approved, Completed or Terminated among others. KoppelHet only creates an employee in Bob at the approved status, so a placement that is still reversed does not produce an employee.
- When a placement is set to terminated, Bullhorn fills in the reason in a separate field. KoppelHet terminates nothing in Bob, but sends HR a notice with that reason, because the end of an assignment need not be the end of employment.
- According to HiBob's API documentation, Bob does not report it if the integration's user only has write rights for part of the fields. KoppelHet therefore reads every new employee back and compares job title, department and start date with the placement.
- A placement through an umbrella company can be recognised in Bullhorn by a linked company. Such a person is on that company's payroll and not on yours, so KoppelHet creates no employee for them in Bob.
- Bullhorn fills the hourly pay rate and the salary in separate fields, with a unit per year or per hour for the salary. Bob has its own salary table for that; in the first version the amount goes to HR as a task, and filling it automatically can be added later.
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
What happens with a second assignment for the same consultant?
No second employee is created in Bob. HR gets a notice and adjusts the work entry if needed.
Does the BSN come from Bullhorn?
No. Bullhorn's SSN field is for the US number. The employee or HR enters the BSN in Bob or payroll.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Bullhorn through the REST API after OAuth 2.0 and a REST login with BhRestToken. Event subscription on Placement (INSERTED and UPDATED), read with GET event/subscription. Placement fields status, terminationReason, employeeType, employmentStartDate, dateBegin, positionCode, payRate, salary, salaryUnit and vendorClientCorporation; Candidate firstName, lastName and email.
- HiBob through POST /v1/people with email, firstName, surname, work.startDate and work.site (required) plus work.title and work.department as existing list values; reading back through People Search. Service user with Add new people to the company, edit rights per category and access to the new employee.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Bullhorn | Field in HiBob | Notes |
|---|---|---|
Candidate.id | Eigen veld in Bob | Recognises a later placement of the same person |
Candidate.firstName en lastName | firstName en surname | |
Candidate.email | email | Required in Bob |
Placement.employmentStartDate (anders dateBegin) | work.startDate | |
Vestiging per Bullhorn-kantoor (tabel) | work.site | Not the client's address |
Placement.positionCode | work.title en work.department | Through a table to existing list values |
Placement.employeeType | Wel of geen medewerker in Bob | Through a table per type |
Related
Bullhorn → AFAS Profit
Bullhorn to AFAS integration: a consultant's first placement starts onboarding
Bullhorn → BambooHR
Bullhorn to BambooHR integration: first placement as an employee with a status row in BambooHR
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel