Recruitment to HR
Teamtailor to Remote integration: hires abroad as employments at Remote
With an integration between Teamtailor and Remote, a candidate hired in Teamtailor for a country without an own entity becomes a new employment at Remote, with name, email, job title, start date and the fields Remote requires for that country. HR checks the employment in Remote and sends the invitation there, after which Remote takes up onboarding as employer of record.
What the integration does
Organisations that recruit in Teamtailor and employ people through Remote in countries without an own entity enter every hire abroad into Remote by hand. HR has to work out each time which fields Remote wants per country.
- The recruiter moves the candidate to the hire stage in Teamtailor.
- KoppelHet checks from the job's location whether the hire runs through Remote.
- Remote's current form for that country is fetched and filled.
- The employment is ready at Remote; HR checks it and sends the invitation.
- Every day KoppelHet compares the hires in Teamtailor with the employments at Remote.
What to watch for with Teamtailor and Remote
- We found no Remote integration in Teamtailor's partner list, nor a ready-made Teamtailor integration at Remote itself. Hires therefore go through custom work or by hand.
- Remote asks for its own set of data per country and supplies a form schema for it. A Teamtailor job can be in any country, so KoppelHet fetches the schema of the job's country for every hire.
- Remote requires a provisional start date and an answer to whether the employee was employed before. Teamtailor has no fixed field for that question; we add it as a custom field and use no when it is empty.
- Through the API Remote only creates employments of the employee type, so employer of record. Employees through the own entity or global payroll cannot be created by the integration, and Dutch hires therefore go to the own HR system.
- The Teamtailor application ID goes to Remote as external reference. Remote does not enforce uniqueness, so KoppelHet checks itself whether a candidate already has an employment before a new one is created.
- Teamtailor does not retry a failed webhook. If Remote is briefly down at the moment of the hire, KoppelHet's daily comparison still finds the missed candidate.
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 integration send the invitation to the new colleague?
No. HR checks the employment first and sends the invitation in Remote. Automatic invitations can follow later as an extension.
Does this work for contractors?
No. The Remote API cannot create contractors; HR arranges them in Remote.
Who decides which jobs run through Remote?
You do, per country. KoppelHet records the list and only sends hires from those countries.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Teamtailor through the company webhook job_application.update (on a stage_id change; HMAC SHA-256 in TT-Signature; webhooks must be enabled for the company by Teamtailor) and the Teamtailor API for candidate, job with location and custom fields.
- To Remote through the Remote API with a company-scoped token and refresh flow. First the JSON schema for the country, then create employment with company_id, country_code (three letters), type employee, external_id and basic_information (email, name, job_title, provisional_start_date, has_seniority_date). Response with status created.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Teamtailor | Field in Remote | Notes |
|---|---|---|
first-name en last-name | basic_information.name | |
email | basic_information.email | |
title van de vacature | basic_information.job_title | |
start-date (onboarding) of eigen veld | basic_information.provisional_start_date | |
Vraag eerdere dienst (eigen veld) | basic_information.has_seniority_date | No by default |
Land van de vacaturelocatie | country_code | Three-letter code |
Job application ID | external_id |
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