Recruitment to HR
Recruitee to Talentech integration: hired candidates with a contract on a position in Talentech
With an integration between Recruitee and Talentech, a candidate hired in Recruitee automatically arrives as an employee in Talentech's HR module, with a contract on the right position, including start date, contract type, hours, probation and salary. The Recruitee id is stored as an external identifier on the employee, so a second notice does not create a duplicate employee.
What the integration does
Organisations that use Talentech for HR but recruit in Recruitee set up positions in Talentech and link new employees to them by hand. If a hire lands on the wrong position, entity, department and manager are wrong.
- KoppelHet fetches the positions from Talentech daily, with legal entity, department, location and superior position.
- At the hire the recruiter picks the position in Recruitee and fills in start date, hours and salary.
- KoppelHet creates the employee profile in Talentech, with the Recruitee id as external identifier.
- Then the contract between the new employee and the chosen position follows.
- HR completes in Talentech what Recruitee does not know, such as the national ID.
What to watch for with Recruitee and Talentech
- Talentech works with positions. An employee is only properly placed once a contract exists between employee and position, and that position determines entity, department, location and manager.
- Recruitee has no positions. HR records per job which Talentech position belongs to it, and the recruiter can set a different position in a profile field at the hire.
- The contract in Talentech holds weekly hours, probation and salary with currency. The terms from the offer are thus in the right place straight away, instead of as a loose note.
- Talentech can store identifiers from other systems on employee and contract. KoppelHet puts the Recruitee id there and searches on it first, so a repeated notice creates nothing twice.
- The employee's login address is called the Talentech ID email in Talentech and is separate from the business email. KoppelHet fills it with the work address from Recruitee, never with the candidate's private address.
- Every write action in Talentech needs its own scope, such as for employees and for contracts. The integration only gets those two write rights and read access to positions.
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
Talentech has its own recruiting systems. Why Recruitee?
That is the organisation's choice. This integration is for those who recruit in Recruitee and run HR in Talentech.
What if the position does not exist yet?
Then HR creates it in Talentech first. KoppelHet does not create positions, because that touches the organisation structure.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee is read through the candidate_moved webhook to a hire stage (signature in X-Recruitee-Signature) and the ATS API for offer and profile fields.
- To Talentech through the PeopleCore API (api.talentech.io/peoplecore) with a JWT from auth.talentech.io (client credentials). POST /v1/Employees (scope peoplecore-employees:write; talentechIdEmail, personalDetails, privateContactInformation, businessContactInformation, nationalIds, externalSystemIdentifiers), POST /v1/Contracts (scope peoplecore-contracts:write; positionId, employeeId, contractType, startDate, endDate, probationEndDate, weeklyHours, salary with amount and currency). Positions through GET /v1/Positions (peoplecore-positions:read).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Talentech | Notes |
|---|---|---|
name | personalDetails.firstName en lastName | Recruitee name split |
emails[0] | privateContactInformation.privateEmail | |
Zakelijk e-mailadres (profielveld) | businessContactInformation.businessEmail en talentechIdEmail | talentechIdEmail is the login address |
phones[0] | privateContactInformation.privatePhoneNumber | |
id van de kandidaat | externalSystemIdentifiers | |
Positie (profielveld) | Contract positionId | |
Startdatum (profielveld) | Contract startDate | |
Contractsoort en einddatum (profielvelden) | Contract contractType en endDate | |
Uren per week (profielveld) | Contract weeklyHours | |
Einde proeftijd (profielveld) | Contract probationEndDate | |
Profielveld salary (amount, currency) | Contract salary |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AFAS Profit
Recruitee to AFAS integration: from hired candidate to new employee
Recruitee → AlexisHR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
Recruitee → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping