Recruitment to HR
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
With an integration between Ashby and HiBob, a candidate who accepted an offer and was hired in Ashby becomes an employee in Bob, with name, start date, job title, department, salary and manager from candidate, offer and job. KoppelHet creates the employee directly, without HR having to complete them in Bob.
What the integration does
Organisations that recruit in Ashby and use HiBob as their HR system want a hire to be in Bob without retyping, with the right manager and without an extra completion step for HR.
- The candidate accepts the offer and is marked as hired in Ashby.
- KoppelHet receives the hire from Ashby, with the offer and the job.
- KoppelHet creates the employee directly in Bob, with the manager by their legal name.
What to watch for with Ashby and HiBob
- A hire that arrives through Bob's Hire API is first a notification HR must complete in Bob with a template. KoppelHet creates the employee directly through Bob's people API, so that completion step disappears.
- Bob only shows an employee's legal name. A hiring manager who uses a preferred name in Ashby is therefore not found; the name in Ashby must match the one in Bob exactly.
- If a candidate already exists in Bob, as with an internal move, HR handles it in Bob itself; KoppelHet builds no route for it.
- Bob requires five fields for a new employee, including the site from the Work table. Ashby only supplies a locationId with the hire. KoppelHet translates that location to an existing site in Bob; without a site Bob does not create the employee.
- Department and job title are list values in Bob that must exist exactly, or Bob rejects the request. KoppelHet first sends a new title or department from Ashby to HR as an alert, so the list in Bob is extended before the hire goes through.
- A salary entry in Bob requires a payPeriod next to the amount, such as Annual or Monthly. The salary in an Ashby offer is an amount with a currency code, without a period. KoppelHet records during setup which period belongs to your offers.
- Ashby gives the offer's start date as a timestamp, Bob wants work.startDate as YYYY-MM-DD. KoppelHet uses only the calendar day, so the first working day in Bob does not move because of a time zone.
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
Why does the manager not come along?
Usually because the name in Ashby differs from the legal name in Bob. Make them the same in Ashby.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- The Hire API receives a POST on https://app.hibob.com/api/integrations/ats/hire (service user or token with X-Bob-HireAPI-Signature, HMAC-SHA256 over timestamp and body, at most 5 minutes old). No required fields; Bob stores the payload and creates a notification. KoppelHet reads Ashby through the candidateHire webhook (Ashby-Signature) and writes to POST /v1/people.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Ashby | Field in HiBob | Notes |
|---|---|---|
candidate.name | firstName en lastName | |
candidate.primaryEmailAddress | email | |
candidate.primaryPhoneNumber | about (telefoon) | |
offer.latestVersion.startDate | work.startDate | |
job.title en departmentId | work.title en work.department | |
offer.latestVersion.salary (value, currencyCode) | financial (salary, currency) | |
Hiring manager | work.reportsTo | Name must match the legal name in Bob |
Related
Ashby → BambooHR
Ashby to BambooHR integration: hire, changed start date and employment status in BambooHR
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker