Recruitment to HR
Teamtailor to Rippling integration: from a hire to a hire in Rippling
With an integration between Teamtailor and Rippling, a candidate who moves to the chosen stage in Teamtailor goes to Rippling, where an admin completes the hire and Rippling starts onboarding, devices and accounts. Besides name, email, job title and department, KoppelHet also takes start date, entity, country and salary from the offer.
What the integration does
Organisations that recruit in Teamtailor and use Rippling for HR, laptops and accounts enter every hire into Rippling by hand. The admin copies start date, entity and salary from the offer letter.
- The recruiter moves the candidate in Teamtailor to the chosen stage.
- KoppelHet first fetches the country requirements for the hire from Rippling.
- Start date, entity and salary come from the offer and custom fields in Teamtailor.
- The hire is ready for review in Rippling, or incomplete with the missing fields.
- An admin completes the hire; Rippling then handles onboarding and accounts.
What to watch for with Teamtailor and Rippling
- Rippling requires different mandatory fields per country for a hire, and the Netherlands is one of the supported countries. KoppelHet fetches those requirements for the country of the Teamtailor job before the hire is created.
- A job for a country where the organisation has no entity of its own becomes an employer-of-record hire in Rippling. KoppelHet derives that from the job's location, so the recruiter does not have to choose anything extra.
- Rippling recognises a repeated or duplicate hire and then returns the existing role. If a candidate accidentally moves to the stage twice in Teamtailor, no second hire is created.
- Teamtailor does not retry a failed delivery: every response outside 2xx counts as a failed delivery. KoppelHet checks the signature in TT-Signature and acknowledges the notification straight away, and only then calls Rippling, so a slow call does not drop a hire.
- Rippling asks for an Idempotency-Key on every call, and the same key on a retry. KoppelHet builds that key from the application in Teamtailor, so a retry after an outage hits the same hire.
- Rippling sends the invitation to an email address or to a mobile number with country code, such as +31. A phone number in Teamtailor is free text, so KoppelHet uses the candidate's email address as the invitation address.
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 Rippling's recruiting module?
That is an option. If you keep recruiting in Teamtailor, the career site and pipelines stay there; the integration starts at the hire.
Does the integration also arrange the laptop and accounts?
No, Rippling does that itself once the hire is completed. The integration ends at the hire.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Teamtailor through the company webhook job_application.update (stage_id change, HMAC SHA-256 in TT-Signature, without retry on a failed delivery) and the Teamtailor API.
- To Rippling through REST API v2 - GET hire-requirements with country_code and hire_type (direct_hire or eor), then POST /hires/ with one to five hires and an Idempotency-Key. Status ready_for_review, incomplete with missing_required_fields or failed; existing_role_id 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 Teamtailor | Field in Rippling | Notes |
|---|---|---|
first-name en last-name | Voornaam en achternaam | |
email | Uitnodigingsadres | |
phone | Telefoon | |
title van de vacature | Functie | |
department van de vacature | Afdeling | |
start-date (onboarding) of eigen veld | Startdatum | |
Locatie van de vacature | Werkland en werklocatie | |
Salaris en valuta uit het aanbod | Basissalaris met periode | Period agreed per job |
Related
Teamtailor → ADP Workforce Now
Teamtailor to ADP Workforce Now integration: hired candidates as in-progress hires
Teamtailor → AFAS Profit
Teamtailor to AFAS integration: hired candidates straight in as new employees
Teamtailor → BambooHR
Teamtailor to BambooHR integration: hired candidates as employees in BambooHR
Teamtailor → BuddeeHR
Teamtailor to BuddeeHR integration: hired candidate as a new employee in BuddeeHR