Recruitment to HR
Recruitee to Sympa integration: hired candidates as a data card in Sympa
With an integration between Recruitee and Sympa, a candidate hired in Recruitee automatically appears as an employee in Sympa, with name, email, start date, organisation, job title and manager. Nobody has to pass on a hire by hand any more, and terms from the offer are included too.
What the integration does
Organisations with Sympa as HR system and Recruitee for recruiting now often pass on hired candidates by hand, one candidate at a time. If that does not happen or happens late, the new colleague is missing in Sympa and in every system that runs on Sympa.
- The Sympa administrator opens an API interface with only the fields the integration may write.
- The recruiter marks the candidate as hired in Recruitee.
- KoppelHet checks whether the person already exists in Sympa and otherwise creates a new employee.
- The contract from the offer is added as a row on the employee, optionally with the signed agreement as attachment.
- If Sympa cannot place a value, the reason shows in the KoppelHet platform and HR gets an alert.
What to watch for with Recruitee and Sympa
- KoppelHet sends a hired candidate to Sympa automatically and also includes contract data.
- A Sympa interface has no fixed fields. The administrator chooses which fields the integration may write, and a field not on the interface makes the hire fail rather than being ignored.
- Option lists such as organisation or contract type must match the interface's mapping table exactly. KoppelHet therefore first translates the values from Recruitee to that table.
- Sympa links the manager through a unique field, such as employee number or email. A name from Recruitee is not unique enough, so the recruiter picks the manager by email address.
- After a new employee is created, it can take up to half an hour before Sympa returns them on a query. KoppelHet therefore remembers which candidates have already been sent, so a second notice does not create a duplicate employee.
- Rows added to a table through the integration are approved in Sympa straight away. If HR wants to review a contract row first, we leave the contract out and HR enters it.
- Sympa cannot delete anything through the integration. A hire that is reversed in Recruitee therefore goes to HR as a task.
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
Which fields does the Sympa administrator need to open?
Only the fields we agree on together, usually name, email, organisation, job title, manager and the contract table. Everything else stays closed.
What happens with the BSN?
It is not sent from Recruitee. HR or the employee enters it in Sympa.
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 signed candidate_moved webhook to a stage with the hire category (X-Recruitee-Signature header) and the ATS API for candidate, offer and profile fields.
- To Sympa through the Integration API (OData 4.0) on an interface with POST and PATCH. A data card with POST api/{interface} (204 response with Location header), a contract row with POST api/{interface}({id})/{table}, attachments as multipart/form-data. Dates yyyy-MM-dd, numbers with a period, DELETE is not supported.
- Authentication with an API key in the X-ApiKey header or with basic authentication (key and secret), fixed per key.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Sympa | Notes |
|---|---|---|
name | Voornaam en achternaam | We split the single Recruitee name field |
emails[0] | E-mailadres | |
phones[0] | Telefoon | |
Startdatum (profielveld) | Startdatum contractregel | Format yyyy-mm-dd |
offer.department | Organisatie-eenheid | Must match the interface's mapping table |
Functie (profielveld) | Functie | |
Leidinggevende (profielveld) | Leidinggevende via personeelsnummer of e-mail | |
Uren per week (profielveld) | Uren op de contractregel | Period as decimal separator |
Getekend contract (bijlage) | Bijlage bij de contractregel |
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