Recruitment to HR
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob
With an integration between Greenhouse and HiBob, a candidate marked as hired in Greenhouse becomes a new employee in Bob, with start date, site, department, job title and contract type from the offer. KoppelHet fetches the offer and creates the employee straight away, with the salary entry and the text fields from the offer.
What the integration does
Organisations that recruit in Greenhouse and manage their staff in HiBob often still retype a hire in Bob. HR then adds salary from the offer and free text fields by hand.
- The recruiter marks the candidate as hired in Greenhouse.
- Greenhouse sends the candidate has been hired webhook to KoppelHet.
- KoppelHet fetches the offer and creates the employee with a salary entry.
- KoppelHet checks whether start date, site and salary really are in Bob.
What to watch for with Greenhouse and HiBob
- If hours or a note sit on the Greenhouse offer as a text field, KoppelHet fills them in Bob separately.
- Greenhouse removed Harvest API v1 and v2 on 31 August 2026. KoppelHet fetches the offer with Harvest v3 with its own client ID and secret; the offer is only readable for a user allowed to see salary data.
- Bob gives no error when the service user may not write a field; the field simply stays empty. After each hire KoppelHet checks whether start date, site and salary really are in Bob.
- Bob requires exactly one site, but a job in Greenhouse can have several offices. Every office in Greenhouse has an external_id field; you put the site name from Bob in it. If a job has more than one office, KoppelHet puts the choice to HR.
- Greenhouse can mark a currency field as a compensation field; it then also gets a frequency, such as annually. A salary entry in Bob requires a payPeriod. KoppelHet translates that frequency to the period in Bob, such as Annual or Monthly.
- The key of a custom field in Greenhouse is its name at creation and does not change when someone renames the field later. KoppelHet maps on that key, so a renamed salary field does not break the handover to Bob.
- If the ping fails when a webhook is saved in Greenhouse, the webhook is disabled and someone has to switch it back on by hand. KoppelHet checks during setup that the hire webhook is active.
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
Is the BSN sent from Greenhouse?
No. The employee or HR fills it in Bob or 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.
- KoppelHet reads Greenhouse through the hire_candidate webhook (HMAC SHA-256 in the Signature header, up to seven attempts in about fifteen hours) and Harvest v3 (OAuth 2.0 client credentials at auth.greenhouse.io/token, GET /v3/offers with starts_on, opening_id and custom_fields).
- To Bob through POST /v1/people with email, firstName, surname, work.site and work.startDate (required) plus work.title and work.department, then an entry in the salary table. The service user needs the Add new people to the company permission.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Greenhouse | Field in HiBob | Notes |
|---|---|---|
Primary email | email | |
First name en Last name | firstName en surname | |
Job name | work.title | |
Offer start date (starts_on) | work.startDate | |
Job office | work.site | Value must exist exactly in Bob's list |
Primary job department | work.department | |
Offer employment type | Contract | |
Salaris als custom field op het aanbod | Salarisregel met ingangsdatum |
Related
Greenhouse → ADP Workforce Now
Greenhouse to ADP Workforce Now integration: accepted offer as an in-progress hire in ADP
Greenhouse → AFAS Profit
Greenhouse to AFAS integration: an accepted offer starts onboarding in AFAS Profit
Greenhouse → BambooHR
Greenhouse to BambooHR integration: hired candidates in BambooHR automatically and completely
Greenhouse → Dayforce
Greenhouse to Dayforce integration: accepted offer as a validated new employee in Dayforce