HR & hiring · wired today
Drive HiBob with governed agents
People data is the most sensitive read an agent will ever make. The HiBob connector is one of 205 executable connectors and gives agents 12 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against HiBob
| Tool | What it does |
|---|---|
list_profiles | Read the public profile of every active HiBob employee (name, work email, title, department, site, manager, start date) |
list_company_lists | List every HiBob company named list (departments, sites, reasons and other configurable lists) with their values |
get_company_list | Get one HiBob company named list by its internal name, with its values and nested children |
list_people_fields | List the HiBob employee field definitions (id, display name, category, type, JSON path) — the metadata needed to read or interpret any profile field |
whos_out | List who is out of the office in HiBob across a date range (employee, policy type, status, dates and day portions) |
out_today | List who is out of the office in HiBob today, or on one specified date |
list_time_off_policy_types | List the names of every HiBob time off policy type (Holiday, Sick and any custom types) — the values the balance tool needs |
get_time_off_balance | Get one HiBob employee's time off balance for a policy type at a point in time (starting balance, taken, adjustments, annual allowance) |
list_open_tasks | List all open HiBob tasks (title, owner, who it is requested for, due date, workflow, status) |
list_employee_tasks | List the HiBob tasks of one employee, optionally filtered to open or closed ones |
list_company_reports | List the HiBob company reports available to this service user (id, name, description, type, whether scheduled) |
list_onboarding_wizards | List the HiBob onboarding wizards defined for the company (id and name) |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the HiBob connector needs
You provide API token, service user ID from your HiBob account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: HiBob's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real HiBob API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
HiBob integration FAQ
What can Quox agents do with HiBob?
Agents can run 12 read-only tools against HiBob: list profiles, list company lists, get company list, list people fields, whos out and more. Every call is receipted in the evidence trail.
What does the HiBob integration need?
You provide API token, service user ID from your HiBob account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my HiBob credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the HiBob connector?
This connector was blind shape-proven against the real HiBob API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.