Recruitment to HR
Workable to Remote integration: a hire outside the own entity as an employment with Remote
With an integration between Workable and Remote, a candidate in the Workable Hired stage for a country where Remote is the employer becomes an employment with Remote, with name, email, job title and provisional start date. Workable lists a Remote integration through Zapier, but the Remote app in Zapier cannot create an employment; KoppelHet creates the employment through the Remote API and leaves the invitation to HR.
What the integration does
Organisations that recruit in Workable and hire people through Remote in countries without an own office enter every foreign hire in Remote by hand. HR has to find out per country which data Remote asks for, and hires for the own entity must not go there at all.
- The recruiter moves the candidate to the Hired stage in Workable.
- KoppelHet looks at the job's legal entity; only hires without an own entity go to Remote.
- KoppelHet retrieves Remote's form for the country and fills it with data from Workable.
- The employment is created at Remote; HR completes it and sends the invitation.
- If the candidate withdraws before the contract is signed, KoppelHet cancels the onboarding.
What to watch for with Workable and Remote
- Workable lists Remote as a third-party integration, built by Remote and powered by Zapier, that moves hired candidates to Remote. The Remote app on Zapier has no action that creates an employment, only Invite Employment for an employment that already exists. KoppelHet therefore creates the employment with the Remote API.
- Through the API Remote only creates employments of type employee or contractor. Own employees and global payroll employees can only be retrieved there. A Workable job at an own entity therefore does not go to Remote but to the own HR system.
- Remote asks for a separate form per country, with besides name, email, job title and provisional start date also whether someone worked for the company before. KoppelHet fills the latter with no, unless the candidate is marked as a former employee in Workable; then HR decides.
- The first working day is a variable in the offer document in Workable, not a fixed field. KoppelHet takes that variable as the provisional start date at Remote, so the day someone moved to Hired does not accidentally become the start date.
- Remote recommends a unique external ID but does not enforce it. KoppelHet puts the Workable candidate number in that field and first checks itself whether an employment already belongs to it, so a second notice from Workable does not create a duplicate hire at Remote.
- If a candidate is disqualified in Workable after Hired, Remote can only cancel the onboarding as long as the employee has not signed yet. KoppelHet cancels in that case; after a signature it is a termination, and KoppelHet leaves that to HR.
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
Does KoppelHet send the invitation to the new employee?
No. HR first checks the employment in Remote and then sends the invitation.
Do contractors go to Remote too?
Not in the first version. That can be added later as an extension; the API does support the contractor type.
What happens to hires in the Netherlands?
They belong to your own entity and do not go to Remote. They need an integration with the own HR system.
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 and GET /candidates/:id, /jobs/:shortcode and /candidates/:id/offer (state; document_variables with start_date). Token with r_candidates and r_jobs.
- Remote with a company-scoped token (renewed through the refresh token flow). First the country's JSON schema, then create employment with employment.basic_information (email, name, job_title, provisional_start_date, has_seniority_date), company_id, country_code, external_id and type employee. Cancel with POST /v1/cancel-onboarding/{employment_id} at status created, created_awaiting_reserve, created_reserve_paid or pre_hire.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Remote | Notes |
|---|---|---|
firstname en lastname | basic_information.name | |
email | basic_information.email | An address that receives mail; Remote sends the invitation there later |
title (vacature) | basic_information.job_title | |
document_variables start_date (aanbod) | basic_information.provisional_start_date | |
location.country_code (vacature) | country_code | Converted to the three-letter code |
Workable-kandidaat-ID | external_id |
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