Human Resources · Integration
BambooHR
Add BambooHR to your product for your customers, and give your AI agents governed access to it.
BambooHR is the HR system a mid-sized company runs day to day, so the records are employees with their job info and compensation history, time off requests and the balances behind them, and the custom tables an admin adds for whatever the standard fields miss. Two practical things shape the integration. Authentication is an API key issued inside one company subdomain, so key and subdomain travel together and rotating either cuts access immediately. And history is table-based: job title and pay live in dated rows instead of single fields, so reading a current value means picking the right row, and writing one appends to history rather than replacing what was there. Credentials stay per tenant with fastn, which also carries the API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own BambooHR subdomain with a key scoped to that company and nothing else.
Read an employee's current job info from the dated rows, rather than treating title and pay as flat values.
Create and approve time off requests from your product, and show the balance that request draws down.
Map the custom tables an HR admin built themselves, so one company's extra fields are configuration on your side.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers which people in a department are away next week, for that company alone.
An agent files a time off request on someone's behalf within the permissions granted, and the entry is logged.
An agent reads an employee's job history and says when the last change took effect.
Example prompt
Who is away in this department next week, and how much of their allowance is left?
Set up BambooHR in 4 steps
- 01Enable the BambooHR connector from your fastn dashboard.
- 02Have each customer authorise their own BambooHR account, so calls run under their credentials rather than a shared key.
- 03Decide which employees, employment records and working time your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the BambooHR integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BambooHR integration without building it. Your customers connect their own BambooHR 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 BambooHR update is not your on-call problem.
- One integration serves your product and your agents. The same governed BambooHR 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
HiBob
Gusto
NamelyOften used alongside
Tools the same teams tend to run next to BambooHR, across other categories.
Slack
NetSuite
Notion
BoxBambooHR integration FAQ
How do I add a BambooHR integration to my product?
Enable the BambooHR connector in your fastn dashboard, then let each customer authenticate their own BambooHR account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BambooHR client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BambooHR account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BambooHR 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 BambooHR 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 which people in a department are away next week, for that company alone.
Who maintains the BambooHR integration?
fastn does. When BambooHR 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 BambooHR 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 BambooHR 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 BambooHR 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 BambooHR integration?
A common starting point: let each customer connect their own BambooHR subdomain with a key scoped to that company and nothing else. 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 BambooHR integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BambooHR does not change your per-connector cost. You can start free with 3 connected accounts.
Add BambooHR to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.