Human Resources · Integration
KeyPay
Add KeyPay to your product for your customers, and give your AI agents governed access to it.
Embed a KeyPay integration so your customers can bring their own payroll data into your product without exporting spreadsheets. Payroll data is sensitive, so access is scoped per tenant, limited to the fields you map, credentials are encrypted, and every read and write is logged. fastn handles per-customer authentication and API upkeep, so a business with its own pay structure needs no code from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own employee records into your product, mapped to the fields you need.
Submit timesheets from your product so hours captured by users flow into payroll.
Read pay run results so your product can show what was paid without re-entry.
Read leave balances and requests so entitlements are visible where users already work.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an employee's leave balance before answering a question about time off.
An agent submits or corrects a timesheet within governed permissions, with each write logged.
An agent flags timesheets that are missing before a pay run closes.
Example prompt
Show employees with unsubmitted timesheets for this pay period and their remaining leave balance.
Set up KeyPay in 4 steps
- 01Open the KeyPay connector from your fastn dashboard.
- 02Have each customer authenticate their own KeyPay account.
- 03Map the employee, timesheet, and leave fields your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the KeyPay integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a KeyPay integration without building it. Your customers connect their own KeyPay 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 KeyPay update is not your on-call problem.
- One integration serves your product and your agents. The same governed KeyPay 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
Workday
GustoOften used alongside
Tools the same teams tend to run next to KeyPay, across other categories.
Slack
NetSuite
Notion
BoxKeyPay integration FAQ
How do I add a KeyPay integration to my product?
Enable the KeyPay connector in your fastn dashboard, then let each customer authenticate their own KeyPay account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no KeyPay client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own KeyPay account?
Yes. Every connection is scoped to the individual customer, so each authorises their own KeyPay 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 KeyPay 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 reads an employee's leave balance before answering a question about time off.
Who maintains the KeyPay integration?
fastn does. When KeyPay 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 KeyPay 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 KeyPay 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 KeyPay 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 KeyPay integration?
A common starting point: read their own employee records into your product, mapped to the fields you need. 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 KeyPay integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding KeyPay does not change your per-connector cost. You can start free with 3 connected accounts.
Add KeyPay to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.