Recruitment to HR
Workable to Loket integration: hired candidate with offer as a concept employee at the right employer
With an integration between Workable and Loket, a candidate who moves to the hired stage in Workable and has an accepted offer automatically becomes a concept employee in Loket. The legal entity from Workable determines the employer, and start date and salary from the offer are already on the concept.
What the integration does
Organisations that recruit in Workable and run payroll in Loket forward the signed offer to payroll after every hire. Payroll copies name, start date and salary into Loket and asks which entity the new colleague belongs to.
- The recruiter moves the candidate in Workable to hired.
- KoppelHet fetches candidate and offer and checks that the offer is accepted.
- In Loket a concept appears at the employer of the legal entity, with the new hire checklist started.
- Payroll adds citizen service number, payroll tax and collective agreement details.
- After review the concept becomes an employee.
What to watch for with Workable and Loket
- Workable sends a notification on every stage change, also when a candidate lands on hired by mistake. KoppelHet first requests the offer and only creates a concept in Loket when that offer has the accepted status.
- In Workable's offer, start date and salary are document variables with a fixed slug. The salary has an amount, a frequency and a currency. A monthly amount in euros becomes a monthly wage in Loket, an hourly amount an hourly wage; an annual amount or foreign currency becomes an alert.
- Workable has legal entities, Loket employers each with one or more payroll administrations. Per entity we record the Loket employer and payroll administration, because the fields of a new concept in Loket depend on that payroll administration.
- A Workable key only gets the rights chosen when it is created. For this integration read rights on candidates, jobs and the account are enough; the integration writes nothing back into Workable.
- Loket only admits an external application to production after Loket's approval, and tests first on an acceptance environment with test data. We test the first hires from Workable there, with a translation table per entity, before the integration runs on the real employers.
- Workable signs its notifications with an HMAC in its own header. KoppelHet checks that signature before anything happens in Loket, so a forged notification cannot put a concept into payroll.
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 offer has no start date?
Then KoppelHet creates no concept and the recruiter gets an alert. After completing it in Workable the hire goes through.
Does this work with several entities?
Yes, as long as each legal entity in Workable belongs to one employer in Loket.
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 (HMAC-SHA256 in X-Workable-Signature) and the API (GET /spi/v3/candidates/{id}, GET /spi/v3/candidates/{id}/offer with state and document_variables, salary in value.data with amount, frequency and currency_iso, start_date in value.body; /legal_entities). Token with scopes r_candidates, r_jobs and r_account.
- Loket through the REST API with OAuth 2.0 (authorization code). Concept metadata per employer (jobapplicant/metadata) and per payroll administration; create the concept and start the new hire checklist. Acceptance on api.loket-acc.nl, production only for approved applications.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Loket | Notes |
|---|---|---|
Candidate id | Vrij veld op het concept | Recognises a second notification |
firstname en lastname | Voornaam, voorvoegsel en achternaam | |
Legal entity | Werkgever in Loket | Through a translation table |
document_variables start_date | Datum in dienst | |
salary (amount, frequency, currency_iso) | Loon per verloningsperiode | Only euro per month or per hour |
email en phone | Privé-e-mail en telefoon |
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