Recruitment to HR
Teamtailor to Lucca integration: hired candidates with employment and job position in Lucca
With an integration between Teamtailor and Lucca, a candidate who reaches Hired in Teamtailor becomes an employee in Lucca, with the first employment, contract template, legal entity, job position and probation complete straight away. KoppelHet determines establishment and department per application, and a returning employee with an existing email address does not block the hire.
What the integration does
Organisations that recruit in Teamtailor and use Lucca as their HR core, often with establishments in France, Belgium and the Netherlands, enter new colleagues in Lucca by hand. A job recruiting for two establishments easily puts an employee in the wrong place there.
- The recruiter moves the candidate to Hired; onboarding in Teamtailor holds start date and work email.
- KoppelHet reads candidate, offer and job and determines establishment, department, legal entity and contract template from a lookup table.
- KoppelHet checks whether the login already exists in Lucca.
- Lucca receives the employee with first employment and first job position in one call.
- If the offer mentions a probationary period, KoppelHet creates it separately.
What to watch for with Teamtailor and Lucca
- One job in Teamtailor can recruit for several establishments. KoppelHet determines establishment and department per application from the location the candidate was hired for, so one job for several establishments still lands in the right place in Lucca.
- Lucca cannot have two employees with the same email address. KoppelHet checks beforehand whether the login exists and puts a returning employee as a task with HR, instead of letting the hire fail.
- Lucca rejects a new employee without a first employment with contract template and legal entity. KoppelHet sends them in the same call, so there is never an employee without a contract in Lucca.
- KoppelHet uses the Lucca API with OAuth and only the rights on employees, employments and job positions.
- Lucca's endpoint for creating employees is in beta and can change without notice. KoppelHet tests every change in Lucca's test environment first and reports a rejected hire to HR immediately.
- Lucca records the probationary period as a separate part of the employment, with an original end date. KoppelHet calculates it from the duration in the Teamtailor offer.
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
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 of type hired (signature in TT-Signature) and the Teamtailor API (job-applications with locations, candidates, jobs with department, job-offers and onboarding with start-date and work-email), 50 requests per 10 seconds.
- Lucca through the Lucca API (header Api-Version 2024-11-01, OAuth 2.0 with employees.readwrite, employments.readwrite and job-positions.readwrite) - POST /lucca-api/employees with givenName, familyName, remoteId and firstEmployment (start, legalEntity, template, firstJobPosition with businessEstablishment and department); POST /lucca-api/probationary-periods with initialEndsOn.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Teamtailor | Field in Lucca | Notes |
|---|---|---|
first-name en last-name | givenName en familyName | |
Werkmail uit de onboarding | remoteId (login) | Must be unique |
Startdatum uit aanbod of onboarding | firstEmployment.start | |
Vacature en locatie | legalEntity en contractsjabloon | Lookup table |
Locatie van de sollicitatie | firstJobPosition.businessEstablishment | |
Department of division | firstJobPosition.department | |
Hiring manager | Leidinggevende | |
Proeftijd uit het aanbod | probationary-period (initialEndsOn) |
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