Skip to content
All connectors
HiBob logo

HiBob

HR, recruitment & payroll

Bring new starters, changes and leavers from HiBob into every system that needs them, with HR approving each change.

26 ways to read, 5 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
HiBob with Nexra

Connected, approved, proven.

The things teams do most with HiBob, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Add custom table entryApproval by rule
  • Create employeeApproval by rule
  • Get time off balanceRead

Example flow

  1. HiBob · Get time off balanceDone
  2. HiBob · Add custom table entryNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches HiBob.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to HiBob
  • HiBob's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

HiBob people with custom fields, history tables, payroll history, custom tables, time off requests, balances and policies, lists, tasks and onboarding wizards.

HiBob API docs
Source actions
26
Destination actions
5
Data types
21

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Custom table entries3
  • Add custom table entryDestinationNot retried automaticallyApproval before production

    Adds one entry to an employee's custom table.

  • List custom table entriesSource

    One employee's entries in a custom table, keyed by column ID.

  • Update custom table entryDestinationProvider duplicate protectionApproval before production

    Updates columns of one custom table entry.

Custom tables1
  • List custom tablesSource

    Custom table definitions with their columns, types and list links.

Employee employment history1
  • List employment historySource

    Employment entries: contract, type, working pattern, weekly hours and FTE.

Employee fields1
  • List employee fieldsSource

    Field metadata: IDs, categories, types, list links and whether a field is historical. Use the IDs in people search.

Employee lifecycle1
  • List lifecycle historySource

    Lifecycle status changes such as hired, employed, leave and terminated.

Employee salaries1
  • List salary historySource

    Salary entries for one employee: base amount, currency, pay period and frequency.

Employee training1
  • List training recordsSource

    One employee's training records.

Employee work history1
  • List work historySource

    Work history entries: title, department, site, manager and change reason.

Employees5
  • Create employeeDestinationNot retried automaticallyApproval before production

    Creates an employee with email, name, site and start date, plus any other fields from field metadata.

  • Get employeeSource

    One employee by ID or email with selected standard and custom fields.

  • List EmployeesSource

    List operation for Employees.

  • Search people with custom fieldsSource

    Employees with selected standard and custom fields, optionally including inactive employees or filtered by IDs or emails.

  • Update employee fieldsDestinationProvider duplicate protectionApproval before production

    Updates supplied employee fields, including custom fields, using HiBob's nested field structure.

Named lists2
  • Get company listSource

    One company list with its items.

  • List company listsSource

    All company lists (departments, sites, custom list fields) with their items.

Onboarding wizards1
  • List onboarding wizardsSource

    Onboarding (welcome) wizard IDs and names.

Payroll history1
  • Read payroll historySource

    Employees with their current payroll tables (employment type, working pattern, FTE and related history).

Profiles1
  • List employee profilesSource

    Public profile fields of all active employees (directory data).

Tasks1
  • List tasksSource

    Open tasks across the company, or all tasks for one employee.

Time off balances1
  • Get time off balanceSource

    An employee's balance, allowance and time taken for a policy type at a date.

Time off changes1
  • List time off changesSourceIncremental

    Time off requests created, cancelled or deleted since a timestamp (up to six months back).

Time off out today1
  • List who's out todaySource

    Employees out of the office today or on a given date, optionally for one site.

Time off policies2
  • Get time off policySource

    A policy's allowance, balance limits, minimum duration, approval and seniority increases.

  • List time off policy namesSource

    Policy names under one policy type.

Time off policy types2
  • Get time off policy typeSource

    A policy type's activity (paid, unpaid, work time) and unit.

  • List time off policy typesSource

    Names of all time off policy types, such as Holiday or Sick.

Time off requests2
  • Submit time off requestDestinationNot retried automaticallyApproval before production

    Submits a days, hours, half-day or hours-per-day time off request for an employee under a policy type.

  • Get time off requestSource

    One time off request with approval details and duration.

Time off1
  • List who's outSource

    Approved time off overlapping a date range, optionally including pending and hourly requests.

Access and limits

Authentication
Service user ID and token
Plans and access
HiBob customers with API access; service users are created by Bob admins. Each service user sees only the fields and employees its permission group allows; fields without permission are omitted silently.
Test environment
HiBob provides sandbox environments to customers and partners on request.
Rate limits
Per-endpoint limits (people search 50 requests per minute); HTTP 429 with X-RateLimit-Reset. Repeated 401/403 responses can block the source IP for five minutes.
Pagination
HiBob returns full result sets for these endpoints; there is no pagination.
Provider events
Webhooks for employee, time off and task events. Flows can start the moment something happens: when a new employee joins; when an employee's details change; when an employee leaves.

Before you build a flow

  • Active employee reads only. Missing requested fields fail clearly; service-user category permissions and employee audience determine coverage. No HR writes or salary access.
  • No deletes, terminations, access revocation, time off cancellation or balance adjustments. Bank account tables are not read.
  • Time off requests are submitted for the policy's approval flow; skip manager approval works only for admin service users.
  • Creating time off requests and employees returns no request body from HiBob; Nexra returns a record keyed by the request values.
  • Payroll history and salary tables need the service user to have payroll permissions; restricted columns are reported, not errors.
  • People search filters support only root.id or root.email with equals; for large companies search by ID batches.
  • Fields the service user cannot view are omitted from responses without an error.
  • Employee updates change only fields sent; table entries (work, employment, lifecycle) and position fields cannot be updated this way. HiBob answers 304 when nothing changed, which Nexra reports as an error.
  • Reads can lag updates by up to 20 seconds.
  • Salary, payroll and bank fields are not requested by default in people search.
  • HiBob documents no idempotency key; uncertain creates are never repeated automatically.

Developer reference

  1. Create the HiBob credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose HiBob, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/hibob and the Connections API.