Human Resources · Integration
Fairsail
Add Fairsail to your product for your customers, and give your AI agents governed access to it.
Embed a Fairsail integration so your customers can work their own employee records, org structure, absence, and performance data from inside your product. 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 instead of exposing the whole employee record. fastn handles per-customer authorisation and API upkeep, so onboarding another organisation is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync employee records and org structure from their own Fairsail instance into your product.
Read absence and leave data so your product plans against real availability.
Update employee details from your product so an HR admin does not make the same change twice.
Trigger your product when an employee joins, changes role, or leaves, so downstream access follows.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about team structure or absence using live records within scoped permissions.
An agent updates an employee record within governed permissions, with every action attributed and audited.
An agent reacts to a joiner or leaver event and runs provisioning across the customer's other systems.
Example prompt
Show employees whose manager changed in the last month and list the teams affected.
Set up Fairsail in 4 steps
- 01Open the Fairsail connector from your fastn dashboard.
- 02Have each customer authenticate their own Fairsail instance.
- 03Map the employee fields, absence types, and org data 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 Fairsail integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Fairsail integration without building it. Your customers connect their own Fairsail 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 Fairsail update is not your on-call problem.
- One integration serves your product and your agents. The same governed Fairsail 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
Workday
BambooHRWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to Fairsail, across other categories.
Slack
NetSuite
Notion
BoxFairsail integration FAQ
How do I add a Fairsail integration to my product?
Enable the Fairsail connector in your fastn dashboard, then let each customer authenticate their own Fairsail account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Fairsail client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Fairsail account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Fairsail 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 Fairsail 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 team structure or absence using live records within scoped permissions.
Who maintains the Fairsail integration?
fastn does. When Fairsail 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 Fairsail 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 Fairsail 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 Fairsail 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 Fairsail integration?
A common starting point: sync employee records and org structure from their own Fairsail instance 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 Fairsail integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Fairsail does not change your per-connector cost. You can start free with 3 connected accounts.
Add Fairsail to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.