Identity and access management
Hailey HR to Google Workspace integration: accounts, units and groups from Hailey
With an integration between Hailey HR and Google Workspace, every new employee from Hailey gets a Google account in the organisational unit of their entity or office, with job title and manager, and teams from Hailey become groups in Google. KoppelHet creates the work email according to your naming rule, writes it back to Hailey and suspends the account on the last working day.
What the integration does
Organisations that use Hailey HR and Google Workspace often still create Google accounts by hand. A new colleague only gets an account once HR enters a work email on the right domain, and a leaver stays active until someone suspends them.
- HR records a new employee in Hailey without a work email.
- KoppelHet determines the address following the naming rule and puts it in Hailey.
- KoppelHet creates the Google account and puts it in the unit of the entity or office.
- Teams from Hailey become groups in Google, so shared drives and calendars follow.
- On the last working day KoppelHet suspends the account, if you want that.
What to watch for with Hailey HR and Google Workspace
- A Google account needs a primaryEmail, but a new employee is recorded in Hailey without a work email. KoppelHet creates that address following your naming rule and writes it back to Hailey as companyEmail.
- KoppelHet places accounts in the unit of their entity or office, so policies for apps and devices can differ per location.
- Besides the last day of employment Hailey has a last working day. KoppelHet suspends on the date you choose, for example the last working day when holiday is taken at the end.
- An employee can be in several teams and have several job titles in Hailey. Google has one title per account. KoppelHet chooses the leading title and turns each team into a Google group.
- A Hailey webhook only contains the employee's ID. KoppelHet fetches the full employee after each notification with a token of a user who may only see the fields for the account, so the Google integration never sees salary or absence.
- Hailey's API token expires after a year and can be extended without changing. KoppelHet extends it in time, so writing back Google addresses and suspending do not stop after a year.
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
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Hailey HR API (v1) with a personal access token (valid for a year, extend through POST /PersonalAccessToken/Extend). GET /Employees (companyEmail, titleIds, teamIds, managerEmployeeId, lastWorkingDay, lastDayOfEmployment), PUT /Employee/{employeeId}/CompanyEmail; webhooks with IDs only. To Google through the Admin SDK Directory API (users with orgUnitPath and suspended; groups and members) with a service account with domain-wide delegation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Hailey HR | Field in Google Workspace | Notes |
|---|---|---|
employeeId | externalIds (type organization) | |
Naamgevingsregel | primaryEmail en companyEmail in Hailey | |
Gekozen functietitel (titleIds) | organizations.title | |
Teams (teamIds) | groepen | |
Juridische entiteit of kantoor | orgUnitPath | |
managerEmployeeId | relations (type manager) | |
lastWorkingDay of lastDayOfEmployment | suspended = true |
Related
Hailey HR → Active Directory
Hailey HR to Active Directory integration: domain accounts from Hailey, expiring on the last working day
Hailey HR → ADP iHCM
Hailey HR to ADP iHCM integration: approved salaries and end of employment to Dutch ADP payroll
Hailey HR → AFAS Profit
Hailey HR to AFAS integration: employment, scope and salary to Dutch payroll
Hailey HR → Arbodienst (SIVI)
Hailey HR to the occupational health service via SIVI: sick days from the Hailey calendar as absence reports