Recruitment to HR
Carerix to Rippling integration: successful match as a hire for review in Rippling
With an integration between Carerix and Rippling, a successful match in Carerix becomes a hire in Rippling that an admin reviews, with legal entity, employment type, start date and salary with period. KoppelHet checks changed matches every quarter of an hour and sends each match with a fixed key, so a repeated run does not create a second hire.
What the integration does
Organisations that recruit in Carerix and use Rippling for HR, payroll and equipment start a hire in Rippling by hand after every successful match. Salary, contract type and entity are already in Carerix, but HR retypes them and converts an hourly or monthly wage itself.
- The recruiter sets the match in Carerix to a status for a successful placement.
- Every quarter of an hour KoppelHet retrieves the changed matches, with candidate and vacancy.
- KoppelHet asks Rippling for the country's mandatory fields and translates entity and contract type.
- The hires go to Rippling in groups of at most five, each with the match key.
- An admin in Rippling reviews and completes the hire; an incomplete hire reaches HR as an alert.
What to watch for with Carerix and Rippling
- We did not find a Carerix integration from Rippling or a Rippling integration from Carerix. Rippling does let admins choose draft hires from an external system when hiring; KoppelHet supplies those hires from Carerix through the API.
- Carerix does not report a new placement by itself, so KoppelHet checks every quarter of an hour. The same match may come up more than once. KoppelHet gives every hire the Carerix match number as key, and Rippling continues the existing hire when a key is repeated.
- A Carerix match has a salary with a unit, such as per hour or per month. Rippling asks for amount, currency and a period of year, month, week, day or hour. KoppelHet translates the unit; a unit without a translation holds the hire back with an alert.
- For a direct hire Rippling asks for a legal entity and an employment type from its own list. The Carerix vacancy has a legal entity and a contract type as data nodes; per value we record the Rippling ID.
- Rippling accepts one to five hires per call. If KoppelHet finds more successful matches in a quarter of an hour, they go in groups of five. When completing in Rippling, full-time employees can only be grouped with full-time employees from the same country, and contractors only with contractors.
- Carerix stores the name prefix apart from the last name, Rippling only knows first and last name. KoppelHet puts the prefix before the last name, so a colleague such as de Vries is spelled correctly in Rippling and in the apps Rippling rolls out.
- If Rippling recognises the person as a former employee or a duplicate hire, it returns the existing role with suggested next steps. KoppelHet then creates nothing new, but puts the match with that role to HR, so a returning worker from Carerix is handled properly.
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 candidate an employee in Rippling right after the integration?
No. Rippling turns it into a hire that an admin reviews and completes.
Does this work for placements in the Netherlands?
Yes, the Netherlands is on Rippling's list of countries for direct hires. KoppelHet retrieves per hire which extra fields Rippling asks for the Netherlands.
Do resume and contract from Carerix come along?
Not in the first version. Files through Rippling's upload 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.
- Carerix through the GraphQL API (https://api.carerix.io/graphql/v1/graphql), confidential client with client credentials. crMatchPage with a qualifier on statusInfoModificationDate and statusInfo.isSuccessfullyFilled; CRMatch _id, jobStartDate, salary and salaryUnitTag; CREmployee firstName, lastNamePrefix, lastName and emailAddress; CRVacancy toLegalEntity, toContractTypeNode and toFunctionLevel1.
- Rippling through GET /hire-requirements/ (country_code, hire_type direct_hire) and POST /hires/ with one to five hires and an Idempotency-Key; fields personal, work_location, employment (title, start_date, employment_type_id, legal_entity_id), compensation (base_pay_amount with currency_type and value, base_pay_period) and related_records.ats_applicant_id. Status ready_for_review, incomplete or failed; existing_role_id and next_actions for a duplicate hire. Scopes hires.read-write and hire-requirements.read.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Carerix | Field in Rippling | Notes |
|---|---|---|
CREmployee firstName | personal.first_name | |
CREmployee lastNamePrefix en lastName | personal.last_name | Name prefix in front |
CREmployee emailAddress | personal.invite_email | |
CRMatch jobStartDate | employment.start_date | |
CRVacancy toFunctionLevel1 | employment.title | |
CRVacancy toLegalEntity | employment.legal_entity_id en work_location.country_code | Lookup table |
CRVacancy toContractTypeNode | employment.employment_type_id | Lookup table to the list in Rippling |
CRMatch salary en salaryUnitTag | compensation.base_pay_amount en base_pay_period | |
CRMatch _id | related_records.ats_applicant_id en Idempotency-Key |
Related
Carerix → ADP Workforce Now
Carerix to ADP Workforce Now integration: placement in North America as an in-progress hire
Carerix → AFAS Profit
Carerix to AFAS integration: a placed candidate starts onboarding in AFAS Profit
Carerix → BambooHR
Carerix to BambooHR integration: successful placement as an employee with employment status in BambooHR
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce