Identity and access management
BuddeeHR to SailPoint integration: Buddee as authoritative source in SailPoint
With an integration between BuddeeHR and SailPoint, every employee from Buddee becomes an identity in SailPoint, with company, department, location, job title, employment type and manager. KoppelHet delivers Buddee as a file to a Delimited File source, with the position that applies on that day and the dates from which SailPoint calculates the lifecycle state.
What the integration does
Organisations that keep HR in BuddeeHR and govern access with SailPoint now load employees into SailPoint with an export. Future colleagues are missing from it, a move as of the first of the month arrives too early, and freelancers and volunteers get the same roles as employees.
- Buddee gets a separate account for the integration; SailPoint a Delimited File source with an identity profile.
- KoppelHet reads employees with their active or future employment, contracts and positions.
- KoppelHet writes one row per employee with today's position and the dates in a fixed format, without IBAN or BSN.
- SailPoint aggregates the file, links the manager through manager correlation and calculates the lifecycle state.
- Roles in SailPoint follow department, location and employment type.
What to watch for with BuddeeHR and SailPoint
- SailPoint has no source for Buddee, and Buddee only lists sign-in with Microsoft and Google as an authentication integration. KoppelHet therefore delivers the employees as a file to a Delimited File source, which SailPoint uses as an authoritative source.
- Over time an employee has several positions in Buddee, each with a start and end date. A SailPoint transform only uses the first value of a multi-value attribute. KoppelHet therefore only puts today's position in the file, so SailPoint only switches roles on the day of the move.
- Buddee can include employees with a future employment. KoppelHet includes them with their start date, so the transform in SailPoint can give a preparatory lifecycle state and accounts are ready before the first working day.
- Contracts in Buddee form a series, with a flag for the last contract. KoppelHet delivers the end date of the last contract in the series, so the lifecycle state does not jump to inactive between two temporary contracts.
- Buddee has six employment types, including intern, agency worker, freelancer and volunteer. KoppelHet puts the type in its own column, so roles and certifications in SailPoint can differ for a freelancer or volunteer from those for an employee.
- SailPoint links a manager through manager correlation on an account in the same source. In Buddee a position points to the manager's internal ID. KoppelHet replaces it with that manager's User Name, and delivers the indirect manager in a separate column for two-step approvals.
- The employee record in Buddee also contains IBAN, BSN and private contact details. The integration account signs in with email and password and sees those fields. KoppelHet drops them immediately, so the file for SailPoint only contains identity data.
This integration is also part of joiner, mover, leaver.
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 Buddee have a SailPoint integration?
Not according to Buddee's integrations page. KoppelHet delivers the data as a file for a Delimited File source.
Does the buddy also go to SailPoint?
Not by default; only the direct and indirect manager. An extra column can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Buddee through the REST API on api.buddee.nl: /employees with include=active_or_future_employment (company_id, number, first_name, composed_last_name, work_email, manager_id, indirect_manager_id), /employments (type, start_date, end_date), /contracts (sequence_number, is_last_in_sequence, end_date) and /positions (job_id, department_id, location_id, manager_id with start_date and end_date); per_page 200. Basic Auth on /auth/token, then JWT as Bearer.
- SailPoint Identity Security Cloud with a Delimited File source as authoritative source. Required identity attributes uid (unique across all profiles), email (not validated) and lastname; Manager Name with manager correlation; Lifecycle State through a transform on the dates; a transform only takes the first value of a multi-value attribute.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BuddeeHR | Field in SailPoint | Notes |
|---|---|---|
company_id + number | uid (User Name) | |
work_email of naamgevingsregel | email (Work Email) | Never personal_email |
composed_last_name_prefix + composed_last_name | lastname | |
first_name | firstname | |
Afdeling, locatie en functie (positie van vandaag) | Identity attributes | |
manager_id | Manager Name (uid van de leidinggevende) | |
indirect_manager_id | Identity attribute indirect leidinggevende | |
employment.type | Identity attribute soort dienstverband | |
employment.start_date en einddatum laatste contract | Lifecycle State (via transform) |
Related
BuddeeHR → Active Directory
BuddeeHR to Active Directory integration: domain account from employment and position in Buddee
BuddeeHR → AllSolutions
Buddee to AllSolutions integration: employees, positions and schedules from BuddeeHR in AllSolutions
ASBuddeeHR → Arbodienst (SIVI)
BuddeeHR to occupational health service via SIVI: verified sickness registrations from Buddee to the health service
BuddeeHR → Microsoft Entra ID
BuddeeHR to Entra ID integration: Microsoft 365 account from the employment in Buddee