Recruitment to HR
SmartRecruiters to Rippling integration: ready to onboard becomes a hire for review in Rippling
With an integration between SmartRecruiters and Rippling, a candidate who is ready to onboard in SmartRecruiters becomes a hire for review in Rippling, with job title, start date, work country, department and pay with period. As soon as Rippling has the hire, the recruiter sees it in the onboarding status in SmartRecruiters, or which field is still missing.
What the integration does
Organisations that recruit in SmartRecruiters and use Rippling for HR, devices and apps enter every hire by hand into Rippling's hire flow, and the recruiter does not know when the hire is done.
- At the start we record which offer properties contain start date, salary and employment type.
- The recruiter sets the onboarding status of the hired candidate to ready to onboard.
- KoppelHet requests the mandatory fields for the job's country and creates the hire in Rippling.
- KoppelHet sets the onboarding status in SmartRecruiters to successful, or to failed with the missing field.
- An admin or manager completes the hire in Rippling.
What to watch for with SmartRecruiters and Rippling
- After a hire Rippling returns whether it is ready for review or incomplete, with the missing fields. KoppelHet translates that into SmartRecruiters' onboarding status - successful when ready for review, failed with the field names when incomplete.
- A SmartRecruiters notification only contains an ID and must be acknowledged within five seconds. KoppelHet acknowledges straight away and then fetches candidate, job and offer, because Rippling's mandatory fields for the country must first be requested.
- Start date, salary and employment type are in offer properties in SmartRecruiters that each organisation names itself. Rippling asks for pay as amount, currency and period. During setup we link each property to one Rippling field, and a missing period sets the status to failed.
- A candidate can have a status on several jobs in SmartRecruiters. KoppelHet sends candidate and job ID together as ATS reference to Rippling, so only the job someone was hired for produces a hire and a repeated notification does not produce a second.
- Rippling accepts up to five hires per call, but only for the same country and type of worker. If a recruiter sets many candidates to ready to onboard at once in SmartRecruiters, KoppelHet groups them per country, so no call fails on a mixed group.
- If a former employee returns through SmartRecruiters, Rippling recognises the existing role and returns it with a next action, instead of creating a new hire. KoppelHet then sets the onboarding status in SmartRecruiters to failed with that message, so HR handles the return in Rippling.
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 the new colleague become an employee in Rippling straight away?
No, it becomes a hire that an admin or manager completes in Rippling. Then Rippling arranges devices and apps.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SmartRecruiters through a webhook subscription (ID only; HMAC-SHA256 in smartrecruiters-signature; 202 within 5 seconds; up to ten retries; callbacks log for 30 days) and the Customer API with OAuth 2.0 client credentials, including the Offer API. Status back through PUT /candidates/{id}/jobs/{jobId}/onboardingStatus.
- To Rippling through REST API v2 - GET /hire-requirements/ with country_code and hire_type, then POST /hires/ (one to five per call, one country and worker type) with an Idempotency-Key. Status ready_for_review, incomplete with missing_required_fields or failed. Scopes hires.read-write and hire-requirements.read; Rippling's API SKU is required.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SmartRecruiters | Field in Rippling | Notes |
|---|---|---|
firstName en lastName | personal.first_name en last_name | |
email | personal.invite_email | |
location.country (vacature) | work_location.country_code | |
location (vacature) | work_location.location_id | Through a table per address |
department (vacature) | employment.department_id | |
Functie van de vacature | employment.title | |
Startdatum (offer property) | employment.start_date | |
Contractsoort (offer property) | employment.employment_type_id | |
Salaris, valuta en periode (offer properties) | compensation.base_pay_amount en base_pay_period | |
Kandidaat-ID en job-ID | related_records.ats_applicant_id |
Related
SmartRecruiters → ADP Workforce Now
SmartRecruiters to ADP Workforce Now integration: ready to onboard becomes a hire in ADP
SmartRecruiters → AFAS Profit
SmartRecruiters to AFAS integration: hired candidate starts onboarding, status back to SmartRecruiters
SmartRecruiters → BambooHR
SmartRecruiters to BambooHR integration: hire with Dutch fields and feedback
SmartRecruiters → Dayforce
SmartRecruiters to Dayforce integration: validate first, then create the employee