Recruitment to HR
Workable to Deel integration: from the Hired stage to a draft contract in Deel
With an integration between Workable and Deel, a candidate in the Workable Hired stage is ready in Deel for a contract as an EOR employee, contractor or global payroll employee. Deel offers this integration itself and for most organisations it is enough; KoppelHet adds to it when hires for the own entity must not reach Deel or when salary details from the offer must come along.
What the integration does
Organisations that recruit in Workable and hire people in other countries through Deel often enter hires in Deel by hand. With the Deel integration that largely happens automatically, but every candidate in Hired then reaches Deel, even when someone starts at the own Dutch entity.
- The recruiter moves the candidate to the Hired stage in Workable.
- The candidate appears in Deel among the new hires from Workable.
- HR chooses the working relationship in Deel and adds what is missing.
- Deel creates the contract, which the candidate then signs.
- With custom work from KoppelHet, hires for the own entity go to the own HR system instead of Deel.
What to watch for with Workable and Deel
- Deel has its own Workable integration, which you connect in Deel under Apps with the Workable subdomain. That needs a Super Admin in Workable and an administrator in Deel, and it is available on all Workable plans.
- The integration does not create a final contract. A candidate in Hired appears in Deel among the new hires from Workable, and HR chooses the working relationship per person there and adds the details before the contract is ready.
- In the Deel integration you set per group and seniority what a new hire gets, and exclusion rules keep candidates out of Deel. If an organisation also recruits for its own entity, those rules are the first place to handle that, before custom work is needed.
- Only name, email, phone, job title, department, country and compensation with currency come from Workable. The salary interval and the start date from the offer document are not in that list; HR adds them in Deel.
- An EOR contract in Deel needs nationality, seniority and a team, which Workable does not have. With custom work KoppelHet looks up team and seniority in Deel; Deel asks the candidate for nationality.
- Anyone who deletes the Deel integration instead of disabling it loses all settings and field mappings. When moving to custom work we therefore disable the integration first and record its settings.
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 only the Deel integration?
We actually recommend that if all hires run through Deel. Custom work is only needed when part of the hires must go elsewhere.
Who signs the contract?
That stays in Deel. HR checks the contract and the candidate signs there.
Do we get a notice when it goes wrong?
In the Deel integration you set recipients for emails about errors. With custom work notices arrive in the KoppelHet platform.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Standard integration - in Deel under More, Apps, Workable with the Workable subdomain and Allow Access; contract after the Hired stage; settings for group, seniority, custom fields, exclusion rules and email notifications. Contract types Global payroll, Independent contractor and EOR.
- Custom work reads Workable through a subscription on candidate_moved with stage_slug hired and GET /candidates/:id/offer (document_variables with start_date; salary with amount, frequency and currency_iso). To Deel through POST /eor (seniority from GET /lookups/seniorities, team from GET /teams), POST /contracts or POST /contracts/gp.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Deel | Notes |
|---|---|---|
firstname, lastname en preferred name | Voornaam, achternaam en roepnaam in Deel | |
email (privé en werk) | Personal email en email | |
phone | Phone | |
title en department (vacature) | Job title en department | |
location.country (vacature) | Country | |
salary (amount, currency_iso) | Compensation rate en currency |
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