Human Resources · Integration
BreatheHR
Add BreatheHR to your product for your customers, and give your AI agents governed access to it.
Embed a BreatheHR integration so your customers can work their own employee records, absences, and HR documents from inside your product, with governed agent access to the same data. HR data is sensitive, so access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. fastn handles each customer's auth and API upkeep, so onboarding another HR account is configuration rather than a deploy.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own BreatheHR account and read employee records and the org structure into your product.
Read and book absences and holiday requests so time off is handled where your users already work.
Read and file HR documents against an employee record without leaving your product.
Trigger your product when an employee joins or leaves so provisioning and offboarding run automatically.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks who is on leave next week before scheduling work, using only the fields you mapped.
An agent books or amends an absence within governed permissions, with the action logged.
An agent reacts to a new starter and kicks off onboarding across the customer's other connected systems.
Example prompt
List employees with unapproved holiday requests and show who each request is waiting on.
Set up BreatheHR in 4 steps
- 01Open the BreatheHR connector from your fastn dashboard.
- 02Have each customer authenticate their own BreatheHR account with least-privilege scopes.
- 03Map the employee, absence, and document fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the BreatheHR integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BreatheHR integration without building it. Your customers connect their own BreatheHR 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 BreatheHR update is not your on-call problem.
- One integration serves your product and your agents. The same governed BreatheHR 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
Works well with
Bridge
Brainshark
SlackOften used alongside
Tools the same teams tend to run next to BreatheHR, across other categories.
NetSuite
Notion
Box
ShopifyBreatheHR integration FAQ
How do I add a BreatheHR integration to my product?
Enable the BreatheHR connector in your fastn dashboard, then let each customer authenticate their own BreatheHR account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BreatheHR client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BreatheHR account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BreatheHR 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 BreatheHR 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 checks who is on leave next week before scheduling work, using only the fields you mapped.
Who maintains the BreatheHR integration?
fastn does. When BreatheHR 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 BreatheHR 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 BreatheHR 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 BreatheHR 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 BreatheHR integration?
A common starting point: connect their own BreatheHR account and read employee records and the 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 BreatheHR integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BreatheHR does not change your per-connector cost. You can start free with 3 connected accounts.
Add BreatheHR to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.