Teamtailor logoTalentech logo

Recruitment to HR

Teamtailor to Talentech integration: hired candidates with a contract on a vacant position in Talentech

With an integration between Teamtailor and Talentech, a hired candidate from Teamtailor arrives as an employee in Talentech's HR module, with a contract on a vacant position, start date, hours, probation and salary. The Teamtailor ID is stored on the employee as an external identifier, so the same hire never reaches Talentech twice.

What the integration does

Organisations that use Talentech for HR but recruit in Teamtailor miss the link Talentech has with its own recruitment systems. HR creates every starter by hand and picks the position, so a hire sometimes ends up on a position that is already filled.

  1. KoppelHet fetches the positions from Talentech daily and keeps track of which are vacant.
  2. The recruiter moves the candidate to the hired stage in Teamtailor.
  3. KoppelHet picks the vacant position that belongs to the job and creates the employee profile, with the Teamtailor ID as external identifier.
  4. Then the contract follows with start date, hours, probation and salary.
  5. If there is no vacant position, HR gets an alert instead of a contract on a filled position.
Teamtailor → KoppelHet → TalentechSOURCETeamtailorTARGETTalentechKoppelHetmapping · logging · monitoringTeamtailor → KoppelHet → TalentechSOURCETeamtailorTARGETTalentechKoppelHetmapping · logging · monitoring
Out: Employee profile with Talentech ID email · Contract on a vacant position · Start date, weekly hours and probation end · Salary with currency · External identifier with the Teamtailor ID

What to watch for with Teamtailor and Talentech

  • Talentech provides its own recruitment systems, such as Webcruiter and ReachMee, and keeps data from those systems separately on the employee. Teamtailor is not one of them. KoppelHet therefore sets the Teamtailor ID as an external identifier on employee and contract, so the origin of the hire stays visible in Talentech.
  • An employee is only properly placed in Talentech with a contract on a position, and a position shows whether it is vacant. Teamtailor has no positions. KoppelHet links the Talentech positions per job and at the hire only picks a position that is still vacant.
  • A position in Talentech has its own weekly hours and possibly a collective agreement. A Teamtailor job has no hours, only an employment type. If there is no deviating hours field on the hire in Teamtailor, KoppelHet copies the position's hours into the contract.
  • The contract in Talentech wants salary as an amount with currency, while a Teamtailor offer stores the salary as free text. KoppelHet takes the amount from the offer and the currency from the job, and leaves the salary empty with a task for HR when the text gives no unambiguous amount.
  • The login address is called the Talentech ID email in Talentech and is separate from the private address. Teamtailor knows the application address and, with the onboarding, also a work address. KoppelHet only fills the login address with that work address.
  • Every action in Talentech requires its own scope. The integration only gets write access to employees and contracts and read access to positions, and in Teamtailor a key that only reads, unless something must go back to the 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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Talentech has its own recruitment systems. Why Teamtailor?

That is the organisation's choice. This integration is for those who recruit in Teamtailor and run HR in Talentech.

Does KoppelHet create positions in Talentech?

No. Positions touch the organisation structure, so HR creates them. KoppelHet only uses existing vacant positions.

What about audit logging, GDPR and our integration platform?

You are the controller and KoppelHet is the processor, under a data processing agreement. Only hired candidates go to Talentech, and every action is in the audit logging. An existing integration platform is left alone.

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 (TT-Signature) and the Teamtailor API (job-applications, candidates, jobs with currency and employment-type, job-offers with status accepted, details.salary and details.start-date, onboardings with work-email). API key with Admin read.
  • To Talentech through the PeopleCore API (api.talentech.io/peoplecore) with a JWT from auth.talentech.io (client credentials). GET /v1/Positions (peoplecore-positions:read; isVacant, jobInformation.weeklyHours, collectiveAgreement), POST /v1/Employees (peoplecore-employees:write; talentechIdEmail, personalDetails, privateContactInformation, businessContactInformation, externalSystemIdentifiers), POST /v1/Contracts (peoplecore-contracts:write; positionId, employeeId, contractType, startDate, weeklyHours, probationEndDate, salary). External identifiers according to GET /v1/Settings/ExternalIdentifiersSettings.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in TeamtailorField in TalentechNotes
first-name en last-namepersonalDetails.firstName en lastName
email van de kandidaatprivateContactInformation.privateEmail
work-email (onboarding)talentechIdEmail en businessEmail
id van de kandidaatexternalSystemIdentifiers
Vacature (vertaaltabel)Contract positionIdOnly a vacant position
start-date uit het aanbodContract startDate
Uren (eigen veld) of uren van de positieContract weeklyHours
Einde proeftijd (eigen veld)Contract probationEndDate
Salaris uit het aanbod en currency van de vacatureContract salary (amount, currency)

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.