HRIS

HiBob

Use the HiBob integration to sync employee data into Ploy so you can drive onboarding, role changes and offboarding from your HRIS. Ploy can also make changes in HiBob for you: add employees, update their names, revoke or restore their access to HiBob, and terminate them.

The HiBob actions are in beta. They were built from HiBob's API documentation and have not yet been run against a real HiBob company, so check the result in HiBob the first few times you use each one. Reading employees into Ploy is unchanged.

How to integrate with HiBob

  1. In Ploy, go to Integrations.

  2. Click Configure under HiBob, then follow the setup instructions. Use the HiBob documentation linked at the top of the setup flow if you need help creating API credentials. Use the HiBob service user ID as the username in Ploy, and create the service user from an admin account with the required permissions.

  3. In HiBob, grant Ploy the required permissions.

  1. In HiBob, make sure the service user has access to Everyone.

  1. Optional: if you want Ploy to restore people's access to HiBob and your company has more than one welcome flow, enter the ID of the welcome flow Ploy should send in Welcome flow for re-invitations. With a single welcome flow you can leave it blank.

Integration Overview

Ploy connects to HiBob through a service user account with API credentials: a service user ID and token. An admin must create the service user and give it access to the full employee directory by granting access to Everyone.

Permissions requested

To read employees, the service user needs read access to the People module in HiBob, plus field-level permissions so Ploy can read employee profile data, organisational structure and employment status.

Only grant the permissions below for the actions you plan to use:

  • Add employees: the "Add new people to the company" permission, and Edit on the fields Ploy sends (name, email, site, start date, department and job title).

  • Update names: Edit on the employee's first and last name.

  • Terminate employees: Edit on the Lifecycle table.

  • Revoke and restore HiBob access: permission to manage employee access and invitations, and to view welcome flows.

What each action does in HiBob

  • Create user adds an employee record with a site and start date. Enter the site name exactly as it appears in HiBob. The start date defaults to today. This does not invite them to sign in to HiBob.

  • Update user changes an employee's first and last name.

  • Suspend revokes the employee's access to HiBob. Their employment is not changed.

  • Restore invites the employee back into HiBob through your welcome flow.

  • Remove user terminates the employee as of today. HiBob has no way to delete employees, so the record stays in HiBob. If HR has already set a leaving date, Ploy keeps it: a date that has passed counts as done, and a future date is left for HR to change.

Data accessed

Ploy can read employee records from the HiBob search API, including:

  • Employee ID

  • Work email

  • First name

  • Surname

  • Department

  • Manager email or ID

  • Start date

  • Site or location

  • Job title

  • Lifecycle status

  • Termination date

  • Active status

  • Payroll employment type

  • Personal email, when configured

  • Any mapped custom columns across work, home, root, financial, and about categories

Ploy also reads company named lists to resolve values such as departments and job titles, and company people field definitions to support custom field mapping during setup. Employees removed from HiBob lose their access in Ploy on the next scan.

Ploy uses HiBob as a source of truth for identity lifecycle events such as onboarding, role changes and offboarding. A related workflow is Employee Field Changed.

Was this helpful?
Was this helpful?