Recruitment to HR
Workable to HiBob integration: hired candidate complete in Bob, with start date and salary
With an integration between Workable and HiBob, a candidate in Workable's Hired stage becomes a new employee in Bob, with site, start date, department, job title and salary from the offer. The existing Workable integration in Bob sends name, email, job title, department, phone, CV and offer letter and has HR complete the new hire in a wizard afterwards; KoppelHet comes in when that last step must be automatic.
What the integration does
Organisations that recruit in Workable and use HiBob get a notification per hired candidate through the Workable integration in Bob. HR then opens the wizard and fills in site, start date and salary from the offer; with many hires at once, notifications pile up.
- The recruiter moves the candidate to the Hired stage in Workable.
- KoppelHet retrieves candidate, job and offer and checks that the offer was accepted.
- Site, department and job title are translated to the lists in Bob.
- KoppelHet creates the employee in Bob with start date and site, and adds the salary as an entry from the start date.
- A value that Bob rejects is shown with the candidate in the KoppelHet platform.
What to watch for with Workable and HiBob
- The Workable integration in Bob only works if the stage in Workable is called exactly Hired. KoppelHet looks at the stage's fixed code instead of its name, so a renamed or translated stage does not stop the integration.
- With the Workable integration, job title and department in Workable must have exactly the same names as in Bob, otherwise the export fails. KoppelHet translates through a table, so recruiters can write job titles for candidates without Bob throwing an error.
- After a hire through the Workable integration, Bob does not yet create an employee. Bob sends a notification, and HR completes the new hire in a wizard. KoppelHet creates the employee directly, with site and start date, which Bob requires.
- In Workable the start date is a variable in the offer document, not a fixed field. KoppelHet reads that variable from the accepted offer; if it is not in the template, we add it before the integration goes live.
- The salary in a Workable offer has an amount, an interval and a currency. KoppelHet puts it into Bob as a salary entry with the start date as effective date, with the same interval, so an hourly wage does not end up in Bob as a monthly amount.
- Workable sends the candidate in a notification as it is at the moment of sending. KoppelHet therefore fetches the offer separately and only creates an employee in Bob once that offer has been accepted.
- For the Workable integration a Super Admin in Workable has to grant access. KoppelHet uses its own key with read rights on candidates and jobs only, and writes nothing back to Workable.
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 not just the Workable integration in Bob?
It is included in every Workable plan and is often enough when HR reviews every new hire anyway. Custom work pays off when there are many hires or job titles cannot be kept identical.
Does the new employee get an invitation to Bob right away?
Only if you want it. HR can also send the invitation themselves after a check.
Does the CV come along too?
It can, but the first version only carries the employee data. Documents can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Workable through a subscription on candidate_moved with stage_slug hired, signed with X-Workable-Signature (HMAC-SHA256). Then GET /candidates/:id, /jobs/:shortcode (title, department, location) and /candidates/:id/offer (state accepted; document_variables with start_date; salary with amount, frequency and currency_iso). Token with the r_candidates and r_jobs scopes.
- HiBob through the People API (create employee with required email, firstName, surname, work.startDate and work.site; work.department and work.title must be existing list values), then an entry in the salary table. Service user with Add new people 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 Workable | Field in HiBob | Notes |
|---|---|---|
firstname en lastname | firstName en surname | |
email | email | |
phone | Persoonlijk telefoonnummer | |
Locatie van de vacature | work.site | Required in Bob; through a lookup table |
department van de vacature | work.department | |
title van de vacature | work.title | |
Document variable start_date uit het aanbod | work.startDate | |
salary (amount, frequency, currency_iso) | Salarisregel met ingangsdatum |
Related
Workable → ADP Workforce Now
Workable to ADP Workforce Now integration: from the Hired stage to an in-progress hire per ADP company
Workable → AFAS Profit
Workable to AFAS integration: a candidate in the hired stage starts onboarding in AFAS
Workable → BambooHR
Workable to BambooHR integration: hire with salary interval and later changes
Workable → Dayforce
Workable to Dayforce integration: hire from the Hired stage, validated first