Skip to content

HiBob

The HiBob integration connects mTime with HiBob (Bob), your HR system. It imports employees, employments, departments and approved time off from HiBob, so HR data is kept in one place: HiBob. The integration only reads from HiBob — it never changes anything there.

What it syncs

The integration imports the following from HiBob into mTime:

  • Employees — Name, email, birthdate and payroll number
  • Employments — Manager, start and end dates, working pattern and employment type
  • Org units — Departments become org units, headed by the manager most of the department’s members report to. Departments nobody active belongs to are left out.
  • Time off — Approved time off requests, including sickness registered after the fact, and their cancellations and changes

Time off imported from HiBob is managed by HiBob: it can’t be changed or cancelled in mTime. See Time off from HiBob.

Before you start: a service user in HiBob

mTime reads from HiBob as a service user. In Bob, go to Settings > Integrations > Service users, create one for mTime and note its ID and token.

Then give the service user a permission group. mTime asks only for what it reads, and only reads: it never changes anything in HiBob, so the service user needs View only — never Edit, and never View history. Where Bob lets you grant a single field rather than a whole category, grant just the fields below. HiBob does not report a missing permission — it simply leaves the data out — so mTime syncs what it can see and lists the rest under Not synced in the last run on the integration page.

PermissionWhat mTime readsWhat it is used forWithout it
Access data for — all employees, including terminated onesWhich employees there areEvery employee synced; terminated ones so their employment gets its end dateEmployees outside it aren’t synced. The default covers employed people only, so leavers keep an open employment in mTime.
People’s data → Basic info — ViewEmail, first name, surnameMatching employees to mTime and naming themNo email: saving is refused, as no employee can be matched. No name: synced empty.
People’s data → Personal → Date of birth — View. Optional.BirthdateBirthdays in mTimeSynced empty. Bob shows the full date, with the year, only to a user that may also edit it, so with View alone the birthdate usually stays empty. mTime doesn’t need it to sync.
People’s data → Work — View on start date, department, reports to and the payroll number fieldStart date, department, manager (reports to) and, by default, the payroll numberThe employment’s start, org unit and manager, and the employee’s payroll numberNo start date: the employment isn’t synced. No department or manager: kept as they are in mTime. No payroll number: synced empty.
People’s data → Lifecycle → Termination date — View on this one field only (internal.terminationDate)Termination dateThe employment’s end dateLeavers keep an open employment in mTime.
People’s data → Employment — View on the working pattern, weekly hours, FTE and employment typeWorking pattern, weekly hours, FTE, employment typeThe employment’s work time norm, and its employment terms through Employment Terms by TypeThe work time norm and the employment terms are kept as they are in mTime.
Time off → See who’s out, plus See who’s out because of a private policyApproved time off and its changesImporting time offNo time off is imported; mTime reports that it found none for the past year. Without private policies, sick leave is left out.

mTime does not need, and you shouldn’t grant:

  • Lifecycle, beyond the termination date: not the lifecycle table, nor the status or lifecycle status fields. HiBob hands out the whole lifecycle table — leave statuses and reasons included — and mTime gets the dates it needs from the start date and the termination date. After a rehire, HiBob moves the start date to the new start.
  • View history on any table. mTime reads only the current entry.
  • Time off requests (create, edit and cancel), balances or time off settings. mTime reads approved time off through See who’s out. For the policy types to enter under Time-Off Activities by Policy Type , look in Bob’s time off settings yourself.

Setting it up in mTime

  1. Go to Integrations and select HiBob
  2. Enter the Service User ID and the Service User Token
  3. Check the settings below — at least Time-Off Activities by Policy Type
  4. Turn the integration on and save
  5. Click Sync Now to run the first sync

When you save, mTime reads a few employees from HiBob to check that the service user can see them and their email addresses. Without those, no employee can be synced, so saving fails.

Anything else the service user may not see — names, birthdates, payroll numbers, start dates, time off — doesn’t stop the sync: mTime syncs what it can and lists what it couldn’t under Not synced in the last run on the integration page. Grant View on the named fields in the service user’s permission group and the next sync fills them in.

SettingDescription
Payroll ID FieldThe HiBob field that holds the employee’s payroll (EE) number. It is synced to the Payroll Number attribute. Default: work.employeeIdInCompany. If your payroll number is in a custom field, enter that field’s id instead.
Employment Type FieldThe HiBob field that holds the employment type, synced to the employment’s HiBob Employment Type attribute. Default: payroll.employment.type.
Employment Terms by TypeWhich employment terms employments of each HiBob employment type get — for example Permanent → your standard terms. Enter the type as HiBob shows it. Types not listed keep the terms they have in mTime.
Time-Off Activities by Policy TypeWhich mTime time off activity each HiBob policy type is registered on — for example Holiday → Vacation and Sick → Sick leave. Enter the policy type as HiBob shows it. Time off on a policy type that isn’t listed is not imported, and is reported after each sync.
Import Absences FromHow far back the first sync imports time off. Leave it empty to start on 1 January of the current year.
API Base URLThe HiBob address. Leave the default, unless you connect to a HiBob sandbox (https://api.sandbox.hibob.com/v1).
Live UpdatesApplies changes in HiBob as they happen, through a webhook in Bob. Off by default. See Live updates.
Webhook Signing SecretThe signing secret Bob shows for the webhook. Only needed for live updates.

How employees are matched

Each HiBob employee is matched to an mTime employee by the HiBob Employee ID once a previous sync has linked the two, and otherwise by email address. If no match is found, a new employee is created in mTime.

Make sure employees have the same email address in both systems before the first sync — that is what prevents duplicates.

Time off from HiBob

Only approved time off is imported. Every kind of HiBob request comes across: full days, half days (morning or afternoon), hours on a day — a 6-hour request becomes 6 hours of time off on that day — clock times, percentages and open-ended leave.

  • The first sync imports all approved time off from the Import Absences From date until a year ahead.
  • Every following sync imports what changed in HiBob since the previous one: new requests, sickness registered after the fact, and changed or cancelled requests — a request cancelled in HiBob is removed from mTime, too.
  • Balances stay in HiBob. Imported time off doesn’t draw on any time off account in mTime.

Managed by HiBob

Time off that comes from HiBob is shown with the label Managed by HiBob, and it can only be changed in HiBob. In mTime, nobody — employee, manager or administrator — can change, cancel, interrupt or approve it, change its hours on the timesheet, book other time off over it, or overwrite it with an Excel import. Make the change in HiBob instead; the next sync brings it to mTime.

Time off registered directly in mTime is not affected — it can be changed as usual.

Attributes added by HiBob

When the integration is active, it adds read-only attributes to synced records. These attributes are managed by HiBob and cannot be edited in mTime.

AttributeDescription
HiBob Employee IDThe employee’s unique identifier in HiBob
Payroll NumberThe employee’s payroll number, read from the Payroll ID Field
HiBob Employment TypeThe employment type, read from the Employment Type Field
HiBob Unit IDThe department the org unit comes from

These appear in their own section on each record, named after the integration. See Custom attributes for more about how integration attributes work.

What to expect after each sync

The integration syncs once per night, or immediately with Sync Now . After each sync:

  • Employees from HiBob are linked to their mTime records, and any that were missing are created — see Employees
  • Each employee’s employment gets its manager, dates, working pattern and employment type from HiBob, and the employment terms you mapped to that type
  • Departments are created or updated in Settings › Org Units. A department archived in HiBob, or one nobody active belongs to any more, is removed from mTime.
  • Approved time off is imported, and time off cancelled in HiBob is removed
  • Anything the sync couldn’t import — a field the service user can’t see, time off on a policy type that isn’t mapped — is reported in the sync run’s result, under Admin › Job Runs

The working pattern is taken from the employee’s weekly, fortnightly or flexible pattern in HiBob. Without one, mTime uses the weekly hours, or the site’s working pattern scaled by the employee’s FTE.

What isn’t synced

  • Only the current employment is synced — not earlier employment periods, nor the history of department and manager changes.
  • Teams aren’t synced — only departments. Teams are a custom field in HiBob, set up differently in every company.
  • HiBob has no hierarchy of departments, so all departments sit side by side in mTime.
  • HiBob has no heads of unit, so mTime picks the manager more than half of a department’s active members report to, directly or further up the line. A department without such a manager keeps the head it has in mTime.
  • A department deleted outright in HiBob (rather than archived) stays in mTime.

Live updates

With Live Updates turned on, HiBob tells mTime about each change as it is made, and mTime applies it shortly after — a new hire or an approved vacation doesn’t have to wait for the night. The daily sync keeps running: it catches up on anything a live update missed, for example while mTime couldn’t be reached.

Live updates bring across:

  • Employees — a new, changed or leaving employee, with their current employment, read the same way the daily sync reads them. A new employee is created in mTime straight away.
  • Time off — time off approved, changed or given an end date in HiBob, and time off declined, cancelled or deleted there.

These still wait for the next daily sync, or for Sync Now :

  • Departments. New, renamed or archived departments, and changed heads, reach mTime with the next sync. An employee moved to a department that isn’t in mTime yet keeps their previous one until then.
  • Changes made while live updates were off, or before the webhook was added in Bob.

Every update HiBob sends about an employee is listed in Admin › Integration Log with the direction Inbound, showing whether it was applied, and if not, why.

Setting up live updates

This takes a HiBob administrator who may add webhooks in Bob. The service user doesn’t change.

  1. In mTime, open HiBob under Integrations, turn on Live Updates and save. The page then shows the webhook URL for your workspace — it ends in /api/webhooks/hibob/ followed by the workspace’s id. You don’t have to enter the service user again to save.
  2. In Bob, go to Settings > Integrations > Webhooks and add a webhook:
    • Version: 2
    • URL: the URL mTime shows
    • Events: the employee events, the table entry events and the time off request events
  3. Bob shows a signing secret for the webhook. Enter it in Webhook Signing Secret in mTime and save.

mTime checks every update against the signing secret and refuses one that isn’t signed with it. Until the secret is saved in mTime, updates from HiBob are ignored. Bob’s test of the webhook still succeeds, so you can add the webhook before you enter the secret.

Troubleshooting

ProblemSolution
Saving fails with “the HiBob service user may not see these fields: root.email”Grant View on the employees’ email in the service user’s permission group in HiBob. Then save again.
The integration page lists fields under Not synced in the last runGrant View on the named fields, and their categories, in the service user’s permission group in HiBob. The next sync fills them in.
Saving fails with “the HiBob service user can see no employees”Add the employees to Access data for in the service user’s permission group.
Employees or end dates are missingAccess data for must include terminated employees, and the service user needs View on the termination date.
Sick leave is not importedThe service user needs the time off permission for private policies, and the sick policy type must be listed under Time-Off Activities by Policy Type .
Some time off is not importedCheck the sync run’s result under Admin › Job Runs — time off on a policy type that isn’t mapped is listed there. Add the policy type to Time-Off Activities by Policy Type .
“Managed by HiBob” when changing time offThe time off comes from HiBob. Change or cancel it in HiBob; the next sync updates mTime.
Payroll numbers are emptyCheck that Payroll ID Field is the field your payroll number is kept in, and that the service user may see it.
Changes in HiBob only reach mTime overnightCheck that Live Updates is on, that the webhook in Bob is version 2 with the URL mTime shows, and that Webhook Signing Secret holds the secret Bob shows. Admin › Integration Log lists each update mTime received. New departments always wait for the next sync.

Next steps

Once the integration is running, see Integrations for how to check sync status, trigger manual syncs, adjust settings, and troubleshoot issues.