Human Resources · Integration
HiBob
Add HiBob to your product for your customers, and give your AI agents governed access to it.
Embed a HiBob integration so your customers can bring their own people data into your product instead of maintaining a spreadsheet next to it. HR data is sensitive and its access rules are stricter than most systems, so access is scoped per tenant, limited to the fields you map, and every call is logged. fastn handles per-customer authentication, field mapping, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync their own employee records and org structure into your product.
Read reporting lines so your product routes approvals to the right manager.
Read time off so your product knows who is out before it assigns or schedules work.
Trigger your product when someone joins, changes role, or leaves so downstream steps follow.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about a team's structure from live records, within scoped permissions.
An agent reads upcoming time off before proposing a plan.
An agent reacts to a leaver and starts removal steps across the customer's other systems, with each action logged.
Example prompt
List employees who changed manager in the last month and show the new reporting line.
Set up HiBob in 4 steps
- 01Open the HiBob connector from your fastn dashboard.
- 02Have each customer authenticate their own HiBob account.
- 03Map only the employee fields your product needs, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the HiBob integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a HiBob integration without building it. Your customers connect their own HiBob account inside your product and work their employees, employment records and working time there, with no per-customer code on your side.
- Handle the part that actually costs time: HR data is sensitive and its access rules are stricter than most systems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a HiBob update is not your on-call problem.
- One integration serves your product and your agents. The same governed HiBob connection powers in-product features and gives AI agents scoped, audited access, so you keep people data current without manual re-entry without wiring it twice.
Used by these teams
Compare with
BambooHR
Gusto
NamelyOften used alongside
Tools the same teams tend to run next to HiBob, across other categories.
Slack
NetSuite
Notion
BoxHiBob integration FAQ
How do I add a HiBob integration to my product?
Enable the HiBob connector in your fastn dashboard, then let each customer authenticate their own HiBob account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HiBob client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own HiBob account?
Yes. Every connection is scoped to the individual customer, so each authorises their own HiBob account and only ever sees their own employees, employment records and working time. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this HiBob integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers a question about a team's structure from live records, within scoped permissions.
Who maintains the HiBob integration?
fastn does. When HiBob changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is sensitive HiBob employee data handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. You expose only what your product actually needs rather than the whole employee record.
Can joiner, mover and leaver changes be automated?
Yes. Where HiBob is where a hire, a role change or a departure is recorded, that change can trigger downstream provisioning or removal across the customer's other connected systems. Where HiBob sits downstream of the HR system of record, the same event can be pushed into it so its worker list, schedules and access stay in step, which is where most of the manual effort sits.
What can I build with the HiBob integration?
A common starting point: sync their own employee records and org structure into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HiBob integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HiBob does not change your per-connector cost. You can start free with 3 connected accounts.
Add HiBob to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.