Identity and access management
Buddee to Google Workspace integration: Google account from the employment, sign-in to Buddee with Google
With an integration between BuddeeHR and Google Workspace, a new employee from Buddee gets a Google account before the start date of their employment, with job, department, location and manager, and the Google address goes back to Buddee as the work email. The employee then signs in to Buddee with that Google account, and after the end date KoppelHet suspends the account.
What the integration does
Organisations that do HR in Buddee and use Google Workspace as their workplace often already use sign-in with Google for Buddee. IT still creates the Google account itself by hand, and until it exists the new colleague cannot get into Buddee either, while their onboarding is waiting there.
- A separate Buddee account is created for the integration, and in Google a service account gets rights on users.
- KoppelHet reads employments that are about to start, with the position that applies on the start date.
- Before the start date KoppelHet creates the Google account and writes the address back to Buddee as the work email.
- KoppelHet then sends the Buddee invitation to that business address, so the employee signs in with Google.
- After the end date of the employment KoppelHet suspends the Google account.
What to watch for with BuddeeHR and Google Workspace
- Buddee offers sign-in with Google, Google Calendar and Google Authenticator, but no integration that creates Google accounts. KoppelHet creates the account from Buddee, so sign-in with Google to Buddee works from day one.
- Buddee can send an invitation to an employee's business address. KoppelHet first sets the new Google address as the work email in Buddee and only then requests that invitation, so the new colleague gets the email in their own Gmail and not in a private mailbox.
- Buddee has six employment types, including intern, self-employed, agency worker and volunteer. KoppelHet gives each type its own organisational unit in Google, so a volunteer for example has no Drive sharing outside the domain.
- A position in Buddee has an indirect manager next to the manager. Google has the dotted_line_manager relation for that second line. KoppelHet fills both, and leaves the buddy from Buddee out of the org chart.
- Job, department and location are stored in Buddee as positions with a start and end date. KoppelHet applies a new position in Google on its start date; with the location the building changes too, and with it the rooms Google Calendar suggests.
- Buddee builds the surname according to the name composition the employee chooses. KoppelHet bases the Google address on the employee's own name, because a Google address remains as an alias after a change and cannot be reused.
- The Buddee API works with an ordinary user's login. If that user later signs in with Google, the integration stops when the account is suspended. KoppelHet therefore uses a separate Buddee account with a password, which stays outside the integration to Google.
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
We already sign in to Buddee with Google. Is this still needed?
That sign-in uses a Google account that already exists. The integration makes sure the account is there in time and closes on departure.
Does the integration see salaries in Buddee?
The integration account only gets rights on employees, employments and positions. We agree at the start which roles Buddee offers for that.
Does this work with several companies in Buddee?
Yes. The company is part of the key, so identical employee numbers are not a problem.
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 with Basic Auth on /auth/token and then a JWT as Bearer: employees (number, last_name_composition, work_email), employments (type, start_date, end_date; filters active_or_future and future) and positions (job_id, department_id, location_id, manager_id, indirect_manager_id with start_date and end_date). Work email back through PUT /employees/{id}; invitation through POST /employees/{id}/invite?type=business.
- Google through the Admin SDK Directory API (users with primaryEmail, name, externalIds, orgUnitPath, organizations with title and department, locations with buildingId, relations type manager and dotted_line_manager, suspended), with a service account with domain-wide delegation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BuddeeHR | Field in Google Workspace | Notes |
|---|---|---|
Bedrijf + number | externalIds (type organization) | Number is unique per company |
first_name en achternaam volgens last_name_composition | name.givenName en name.familyName | |
Naamgevingsregel op eigen naam | primaryEmail | Back as work_email |
employment type | orgUnitPath | |
positions.job_id | organizations.title | |
positions.department_id | organizations.department | |
positions.location_id | locations.buildingId | |
positions.manager_id | relations (type manager) | |
positions.indirect_manager_id | relations (type dotted_line_manager) | |
employments.end_date | suspended = true |
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