Accounts in applications
BambooHR to Simplicate integration: Dutch colleagues with timetable and manager in Simplicate
With an integration between BambooHR and Simplicate, every new colleague at a Dutch location in BambooHR automatically becomes an employee in Simplicate, with manager, team and a timetable based on weekly hours. When someone leaves, KoppelHet closes the timetable on the last working day and the Simplicate administrator gets a prompt to block the user.
What the integration does
Organisations that use BambooHR for every country and track projects and hours in Simplicate in the Netherlands prepare new colleagues there by hand. Anyone moving to fewer hours often keeps the old timetable in Simplicate, so capacity figures are wrong.
- HR creates a new colleague in BambooHR at a Dutch location.
- BambooHR sends a notification; KoppelHet fetches the data.
- KoppelHet first creates the person and then the employee in Simplicate, with manager and team.
- The weekly hours become a timetable from the start date.
- The administrator invites the colleague as a user in Simplicate.
- On different hours or departure KoppelHet closes the timetable; on departure the administrator gets a task to block the user.
What to watch for with BambooHR and Simplicate
- BambooHR keeps working time as one number, the standard hours per week. A Simplicate timetable wants hours per day. KoppelHet spreads the weekly hours over the working days by a fixed rule you choose, and HR adjusts deviating days in Simplicate afterwards.
- A global webhook in BambooHR monitors a fixed list of fields. KoppelHet creates its own webhook through the API that also monitors weekly hours and location, so a change in hours produces a new timetable in Simplicate straight away.
- In BambooHR supervisorId points to the manager's employee number and supervisorEId to the internal ID. KoppelHet uses the internal ID to find the manager in Simplicate. If that manager works outside the Netherlands and is not in Simplicate, the field stays empty and the administrator sees it on a list.
- The employment status in BambooHR has values such as Contractor, Full-Time and Part-Time. Every Simplicate user costs a licence. Per status we agree who goes into Simplicate, so a freelancer who books no hours does not end up there.
- Simplicate has no users endpoint in its public API. KoppelHet prepares person, employee and timetable; the administrator invites and blocks. If someone leaves in BambooHR, the administrator gets a task on the last working day to block the user.
- A new colleague takes at least three calls in Simplicate, for person, employee and timetable. Simplicate promises at least sixty calls per minute. If BambooHR bundles many employees in one notification, KoppelHet spreads the work over time, so Simplicate refuses no calls.
- A Dutch surname such as van Dijk is often stored in one BambooHR field. The Simplicate person has a separate field for the name prefix. KoppelHet puts the prefix there, so the colleague is sorted under Dijk in Simplicate.
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
Does the new colleague also become a Simplicate user?
The integration prepares everything, but the administrator sends the invitation. Simplicate's public API cannot create or block users.
Does salary come along for the cost rate?
No. The integration's BambooHR user sees no compensation, and rates cannot be written through the Simplicate API. The controller sets them.
Can time off from BambooHR go to Simplicate too?
That can be added later as an extension. We start with employees and timetables.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- BambooHR through a permissioned webhook (HTTPS only; payload with employees, changedFields and fields; HMAC-SHA256 with X-BambooHR-Timestamp and X-BambooHR-Signature; up to five retries over a little over an hour; no custom table fields) and the Employees API for id, firstName, preferredName, lastName, workEmail, location, department, supervisorEId, employmentStatus, standardHoursPerWeek, hireDate and terminationDate. API key of a user with only these fields, without compensation.
- Simplicate REST API v2 (Authentication-Key and Authentication-Secret; at least 60 requests per minute, 429 above that): POST /crm/person (first_name, family_name_prefix, family_name, email, teams), POST and PUT /hrm/employee (only person_id, supervisor, status and custom_fields), POST and PUT /hrm/timetable (employee_id, even_week, odd_week, has_odd_weeks, start_date, end_date). Teams read-only; no users endpoint.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BambooHR | Field in Simplicate | Notes |
|---|---|---|
id | Eigen veld bij de medewerker (custom_fields) | Fixed key |
preferredName of firstName | first_name (persoon) | |
lastName | family_name_prefix en family_name (persoon) | Prefix separately |
workEmail | email (persoon) | |
supervisorEId | supervisor (medewerker) | Only if the manager is in Simplicate |
department | teams (persoon) | Lookup to existing teams |
standardHoursPerWeek | even_week (rooster) | |
hireDate | start_date (rooster) | |
terminationDate | end_date (rooster) en status | |
location | Wel of niet naar Simplicate | Dutch locations only |
Related
Ashby → BambooHR
Ashby to BambooHR integration: hire, changed start date and employment status in BambooHR
BambooHR → 4PS Construct
BambooHR to 4PS Construct integration: employees from BambooHR in the 4PS company of their location
BambooHR → Active Directory
BambooHR to Active Directory integration: accounts in your own domain from HR
BambooHR → ADP iHCM
BambooHR to ADP iHCM integration: salary, bonuses and commissions to Dutch payroll