HiBob
Read and manage HiBob (Bob) employees, time off, tasks, reports and attendance over the Bob public API with a service user.
About
HiBob ships in the w6w first-party pack. It declares 27 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.hibob- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Human Resources · Productivity
Overview
HiBob (Bob) is a modern HR platform, and this app gives a workflow direct access to the people data and processes inside it, through Bob’s public API and a service user’s ID and token.
On the people side, a workflow can search employees in bulk or read one by ID with exactly the fields it needs, read the public profile directory, create new hires, update fields, and terminate employees. Metadata actions list every employee field and company list so a workflow can discover the field ids and list values Bob expects, and history actions read an employee’s work, employment and lifecycle tables.
Time off is covered end to end: submit, read and cancel requests, check balances for a policy type, list policy types, see who is out today or across a date range, and poll for request changes since the last run. Tasks can be listed company-wide or per employee and completed, reports can be listed and downloaded as JSON or CSV, and attendance entries can be searched by employee and date range.
Bob only returns what the service user’s permission group allows, and omits anything else silently, so the app documents where that bites. Health checks track the Public API component on Bob’s status page and the per-endpoint rate limit headroom.
Build with HiBob
Three routes to the same 27 actions. The Workflow tab is generated from HiBob's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Search Attendance Entries
attendance-entries-search Fetch one employee's attendance (clock in/out) entries for a date range of up to 33 days.
List Employment History
employment-history-list List an employee's employment history entries (contract, working pattern, FTE).
List Employee Fields
fields-list List every employee field (id, category, type) including custom fields.
List Lifecycle History
lifecycle-history-list List an employee's lifecycle status history (hired, employed, terminated, ...).
List Company Lists
named-lists-list List all company lists (sites, departments, job titles, ...) with their items.
Search Employees
people-search Read employee fields in bulk, optionally filtered by employee id or email. Returns every match in one response (Bob has no pagination here); fields the service user cannot view are silently omitted.
List Public Profiles
profiles-list Read the public profile section of all active employees the service user can see.
List Employee Tasks
tasks-person-list List the tasks of one employee, optionally only open or only closed.
Get Time Off Balance
timeoff-balance-get Read an employee's time off balance for a policy type as of a date.
Submit Time Off Request
timeoff-request-create Submit a days-based or hours-based time off request for an employee.
Get Time Off Request
timeoff-request-get Read one time off request, optionally with per-day durations.
List Time Off Request Changes
timeoff-requests-changes List changes made to time off requests since a timestamp.
List Work History
work-history-list List an employee's historical work entries (title, department, manager, site).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying HiBob's real ids.
{
"manifestVersion": "2",
"name": "hibob-example",
"steps": [
{
"id": "attendance-entries-search",
"uses": {
"app": "io.w6w.hibob",
"action": "attendance-entries-search",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"employeeId": "<employeeId>",
"fromDate": "<fromDate>",
"toDate": "<toDate>"
}
}
]
}Here are some of the things you can do
-
Search Attendance Entries
searchattendance-entries-search -
List Employment History
reademployment-history-list -
List Employee Fields
readfields-list -
List Lifecycle History
readlifecycle-history-list -
Get Company List
readnamed-list-get
+22 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for HiBob, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to HiBob. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "attendance-entries-search",
payload: {
employeeId: "<value>",
fromDate: "<value>",
toDate: "<value>",
// fields: "<value>",
// limit: "<value>",
// cursor: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action attendance-entries-search --payload '{"employeeId":"<value>","fromDate":"<value>","toDate":"<value>"}'Give an AI agent HiBob — without giving it HiBob's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.hibob#attendance-entries-search",
"input": {
"employeeId": "<employeeId>",
"fromDate": "<fromDate>",
"toDate": "<toDate>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's HiBob connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
HiBob's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. HiBob itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
HiBob declares its own checks, so its health is a property of the app rather than something the host guesses at.
Bob Public API status
The 'Public API' component of status.hibob.io (Atlassian Statuspage). The page also covers payroll, hiring and other modules; those do not affect this verdict.
API request-rate headroom
Reads X-RateLimit-Limit / -Remaining / -Reset off a signed GET /v1/company/people/fields. Bob limits requests per endpoint per minute (50 for people search), so this reports the probe endpoint's bucket, not an account-wide figure.