Recruitment to HR
Workable to Rippling integration: only hired candidates, with the offer, as a hire in Rippling
With an integration between Workable and Rippling, only a candidate in the Workable Hired stage appears as a hire for review in Rippling, with start date, job title, legal entity and salary from the offer. Applicants stay out of Rippling, and HR does not have to retype the offer.
What the integration does
Organisations that recruit in Workable and use Rippling for HR, payroll and IT retype start date, job title and salary from the offer in Workable for every hire.
- The recruiter moves the candidate with an accepted offer to the Hired stage.
- KoppelHet fetches candidate, offer and job from Workable.
- KoppelHet asks Rippling for the mandatory fields for the job's country.
- The hire arrives in Rippling ready for review, or as incomplete with the missing fields.
- An admin in Rippling completes the hire; Rippling then handles apps and equipment.
What to watch for with Workable and Rippling
- KoppelHet only reacts to the Hired stage with an accepted offer, so Rippling contains no applicants.
- The salary in a Workable offer has an amount, a period and an ISO currency. Rippling asks for exactly those three, with a period of year, month, week, day or hour. KoppelHet converts the period and stops with an alert if Workable gives a period Rippling does not know.
- Rippling requires a legal entity for a direct hire; for a hire through employer of record it is omitted. Workable records legal entities per job. KoppelHet translates them to the entity in Rippling, and a job in a country without an own entity becomes an EOR hire.
- Rippling has a field for the applicant ID from the ATS and accepts an Idempotency-Key. KoppelHet fills both with the Workable candidate number, so a repeated notice continues the same hire instead of creating a second one.
- Rippling answers per hire with ready for review, incomplete with the missing field paths, or failed. KoppelHet reports an incomplete or failed hire to HR with the fields still missing from the Workable offer or job.
- In Workable KoppelHet only needs a token with the read scopes r_candidates and r_jobs. On the Rippling side the API SKU and the scopes hires.read-write and hire-requirements.read are needed, and nothing more.
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
Is the new colleague an employee in Rippling right after the integration?
No. Rippling turns it into a hire that an admin reviews and completes.
Can the offer document come along?
Not in the first version. Rippling accepts files through a separate upload; that 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.
- KoppelHet reads 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; salary with amount, frequency and currency_iso). Token with r_candidates and r_jobs.
- To Rippling through GET /hire-requirements/ (country_code, hire_type direct_hire or eor) and POST /hires/ with one to five hires; compensation.base_pay_period YEAR, MONTH, WEEK, DAY or HOUR; related_records.ats_applicant_id; status ready_for_review, incomplete or failed. Scopes hires.read-write and hire-requirements.read; the Rippling API SKU is required.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Rippling | Notes |
|---|---|---|
firstname en lastname | personal.first_name en personal.last_name | |
email | personal.invite_email | |
document_variables start_date (aanbod) | employment.start_date | Format YYYY-MM-DD |
title (vacature) | employment.title | |
Juridische entiteit (vacature) | employment.legal_entity_id | Lookup table; empty for employer of record |
location.country_code (vacature) | work_location.country_code | |
salary amount, frequency en currency_iso | compensation.base_pay_amount en base_pay_period | |
Workable-kandidaat-ID | related_records.ats_applicant_id en Idempotency-Key |
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