Recruitment to HR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
With an integration between Recruitee and AlexisHR, now called Simployer One, a candidate hired in Recruitee becomes a new employee in AlexisHR, with work and personal email, job title, department, manager and start date. KoppelHet builds that step through the public HRM One API.
What the integration does
Organisations with Scandinavian entities in AlexisHR that recruit in Recruitee re-enter every hire in AlexisHR.
- KoppelHet fetches departments and employees with work address from AlexisHR daily.
- The recruiter moves the candidate in Recruitee to a stage with the hire category.
- KoppelHet looks up department and manager and creates the employee.
- Then the employment and the compensation follow.
- AlexisHR confirms with the employee.created webhook; if it is missing, HR gets an alert.
What to watch for with Recruitee and AlexisHR
- AlexisHR has been called Simployer One since the acquisition by Simployer, but the API still runs on api.alexishr.com. Existing integrations and documentation use both names.
- AlexisHR keeps the work address and the personal address apart. Recruitee only knows the application address, so it becomes the personal address and we put the work address in a profile field beforehand.
- AlexisHR records a manager as a reference to an existing employee, not as a name. KoppelHet looks up the manager by their work address in AlexisHR and sets the reference; if unknown, the field stays empty and HR gets an alert.
- The employment is a separate record in AlexisHR with start date and employment type, apart from the employee. KoppelHet creates it after the employee, with the start date from Recruitee.
- Pay in AlexisHR has a payout period from hourly to annual. The salary field in Recruitee lacks that period; we add a choice field to the offer form, so a Swedish monthly salary arrives as a monthly amount.
- AlexisHR stores the personal identity number together with the issuing country. That number does not belong in a recruitment system, so the integration does not send it; HR or the employee completes it in AlexisHR.
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
Is AlexisHR the same as Simployer One?
Yes. The name changed; the API and the integration stay the same.
Why not Simployer's recruitment module?
That is an option. If you keep recruiting in Recruitee, jobs and pipelines stay there; the integration starts at the hire.
Do Dutch hires go to AlexisHR too?
Only if you manage Dutch employees in AlexisHR. KoppelHet decides per job whether the hire goes to AlexisHR.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee through the candidate_moved webhook with event_subtype stage_changed to a stage with the hire category (HMAC SHA-256 in X-Recruitee-Signature, up to nine retries) and the ATS API for profile fields.
- AlexisHR through the HRM One API (api.alexishr.com/v1, bearer token) - POST /employee (createEmployee, with firstName, lastName, workEmail, privateEmail, birthDate, title, departmentId and managerEmployeeId), then employment and compensation. Confirmation through the employee.created webhook signed in X-Simployer-Signature.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in AlexisHR | Notes |
|---|---|---|
name | firstName en lastName | |
Zakelijk e-mailadres (profielveld) | workEmail | |
emails[0] | privateEmail | |
Geboortedatum (profielveld) | birthDate | |
Functietitel (profielveld) | title | |
Afdeling van de vacature | departmentId | |
E-mail van de leidinggevende (profielveld) | managerEmployeeId | Looked up through workEmail in AlexisHR |
Startdatum (profielveld) | Employment startDate | |
Salaris en periode (profielveld) | Compensation met payoutPeriod |
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 → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping
Recruitee → BuddeeHR
Recruitee to BuddeeHR integration: hired candidates as employees in BuddeeHR