Human Resources · Integration
Xemplo
Add Xemplo to your product for your customers, and give your AI agents governed access to it.
Xemplo manages the employment lifecycle for a workforce that is not all employees. Contractors, casuals and permanent staff sit in one system with the same onboarding, the same document trail and the same compliance obligations, which is the problem it was built for and the reason its records look a little different from a conventional HRIS. An embedded Xemplo integration reads worker records and their employment details, starts onboarding or offboarding when a hire or a departure happens in your product, reads documents and signed forms, and pulls leave and timesheet data where a customer exposes it. Because the platform is organised around compliance rather than convenience, what a customer will let you see is narrower than the full record, so scope is agreed per tenant and only mapped fields ever travel. fastn holds those credentials per customer and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Xemplo account so worker data reaches your product without a spreadsheet in the middle.
Read worker records covering employees and contractors alike, since both sit in the same lifecycle here.
Start onboarding or offboarding from an event in your product, so paperwork and access follow the decision automatically.
Read documents, signed forms and leave where a customer permits it, mapped field by field rather than wholesale.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers which workers are engaged on what basis and from when, from one customer's records.
An agent starts an onboarding inside scoped permissions, and the worker it acted on is recorded.
An agent reports which onboarding steps are outstanding for people due to start soon.
Example prompt
Who is due to start in the next fortnight, and which onboarding steps are still open for them?
Set up Xemplo in 4 steps
- 01Enable the Xemplo connector in your fastn dashboard.
- 02Have each customer authorise their own account and agree which parts of the worker record are in scope.
- 03Map only those fields, then enable the onboarding and offboarding actions your product genuinely drives.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Xemplo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Xemplo integration without building it. Your customers connect their own Xemplo 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 Xemplo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Xemplo 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
HiBob
PersonioOften used alongside
Tools the same teams tend to run next to Xemplo, across other categories.
Slack
NetSuite
Notion
BoxXemplo integration FAQ
How do I add a Xemplo integration to my product?
Enable the Xemplo connector in your fastn dashboard, then let each customer authenticate their own Xemplo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Xemplo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Xemplo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Xemplo 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 Xemplo 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 workers are engaged on what basis and from when, from one customer's records.
Who maintains the Xemplo integration?
fastn does. When Xemplo 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 Xemplo 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 Xemplo 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 Xemplo 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 Xemplo integration?
A common starting point: let each customer connect their own Xemplo account so worker data reaches your product without a spreadsheet in the middle. 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 Xemplo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Xemplo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Xemplo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.