Recruitment to HR
Lever to HiBob integration: hired candidate with offer as an employee in Bob
With an integration between Lever and HiBob, a candidate hired in Lever becomes an employee in Bob, with site, start date, job title and salary from the signed offer. The recruiter then sees in Lever that the employee exists in Bob.
What the integration does
Organisations that recruit in Lever and use HiBob as their HR system often enter a hired candidate in Bob by hand or complete a half-filled new hire there. Start date and salary sit in the Lever offer and are copied by hand, and Lever does not show whether that has happened yet.
- The recruiter marks the opportunity as hired in Lever.
- Lever only sends the opportunity and contact numbers; KoppelHet fetches opportunity, offer and posting itself.
- KoppelHet checks whether candidate and company have both signed the offer.
- Location, department and job title are translated to the lists in Bob, and the employee is created with a salary entry.
- KoppelHet adds a note to the opportunity in Lever with the outcome.
What to watch for with Lever and HiBob
- On a hire Lever only sends the number of the opportunity and of the contact. KoppelHet fetches the rest with its own key, so Bob only receives data that Lever really holds at that moment.
- A Lever offer already shows a signed document as soon as one party has signed. Bob only receives the employee once the company signature is there too; KoppelHet checks each signer in the offer for that.
- Bob does not create an employee without a site, and the location of a Lever posting is a free tag. KoppelHet records the Bob site per tag and reports a new tag to HR, instead of sending Bob a value that is not in the list.
- The salary in a Lever offer has an amount, a currency and an interval. KoppelHet puts it into Bob as a salary entry on the start date, with the same interval, so an hourly wage or annual salary does not reach Bob as a monthly amount.
- Lever has no status for reporting back from an HR system. KoppelHet therefore adds a note to the opportunity through the API, so the recruiter sees in Lever that the employee exists in Bob or why it failed.
- Lever retries a failed webhook five times and then stops. Because a missed hire in Bob only shows on the first working day, KoppelHet compares the hired opportunities in Lever with the employees in Bob every day.
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 if the candidate is confidential in Lever?
Confidential opportunities belong to confidential postings. KoppelHet's key needs access to them; we arrange that during setup.
Does the new employee get an invitation to Bob right away?
No, unless you want it. HR usually sends the invitation itself, shortly before the start date.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Lever through the candidateHired webhook (data.opportunityId and data.contactId; HMAC-SHA256 over token and triggeredAt with the signing token; HTTPS only; five retries) and the Lever API with an API key through basic authentication. GET /opportunities/:opportunity, GET /opportunities/:opportunity/offers (fields with identifier anticipated_start_date, job_title, salary_amount, compensation_currency, salary_interval; signatures per signer), GET /postings/:posting (categories.team, department, location). Reporting back through POST /opportunities/:opportunity/notes. Limit 10 requests per second, bursts up to 20.
- HiBob through POST /v1/people (required email, firstName, surname, work.startDate and work.site; list values must exist), then an entry in the salary table. Service user with Add new people to the company and edit rights per category; Bob does not report partial rights.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Lever | Field in HiBob | Notes |
|---|---|---|
name (één veld) | firstName en surname | Split, with the name prefix kept with the surname |
emails[0] | email | Required in Bob; usually the private address |
phones[0] | Persoonlijk mobiel nummer | |
categories.location (posting) | work.site | Required in Bob, through a lookup table |
categories.department en team (posting) | work.department | |
Offer field job_title | work.title | |
Offer field anticipated_start_date | work.startDate | |
Offer fields salary_amount, compensation_currency, salary_interval | Salarisregel met ingangsdatum |
Related
Lever → BambooHR
Lever to BambooHR integration: hired candidate as a new employee profile in BambooHR
Lever → Dayforce
Lever to Dayforce integration: signed offer as a validated new employee in Dayforce
Lever → Deel
Lever to Deel integration: hired candidate as own employee or EOR contract in Deel
Lever → Oracle HCM Cloud
Lever to Oracle HCM integration: hired opportunity as a pending worker in Oracle