Human Resources · Integration
PeopleDoc
Add PeopleDoc to your product for your customers, and give your AI agents governed access to it.
Embed a PeopleDoc integration so your customers can work their own employee records and employee files from inside your product instead of downloading them. PeopleDoc is HR service delivery, now sold by UKG as UKG HR Service Delivery, and its records are employees, the documents filed against each employee, the categories those documents sit in, and the HR processes and requests that move them along. This is some of the most sensitive data a company holds, so access is scoped per tenant, limited to the fields and categories you map, and every read and write is logged. fastn handles per-customer credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own PeopleDoc environment so your product reads employee records without an export.
File a document your product generates against the right employee and document category, with the write attributed to the tenant that authorised it.
Read HR process and request state so your product can show where an onboarding or a change request sits.
Expose only the employee fields and document categories your product actually needs rather than the whole employee file.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the right employee document within scoped permissions, with every read audited.
An agent files a generated letter or certificate against an employee record, with the action logged per tenant.
An agent reacts to a new hire or a departure and runs the next provisioning or offboarding step.
Example prompt
List employees missing a signed document in the contracts category and show who owns each request.
Set up PeopleDoc in 4 steps
- 01Open the PeopleDoc connector from your fastn dashboard.
- 02Have each customer authorise their own PeopleDoc environment with least-privilege credentials.
- 03Map the employee fields, document categories and processes 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 PeopleDoc integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PeopleDoc integration without building it. Your customers connect their own PeopleDoc 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 PeopleDoc update is not your on-call problem.
- One integration serves your product and your agents. The same governed PeopleDoc 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
BambooHR
PersonioOften used alongside
Tools the same teams tend to run next to PeopleDoc, across other categories.
Slack
NetSuite
Notion
BoxPeopleDoc integration FAQ
How do I add a PeopleDoc integration to my product?
Enable the PeopleDoc connector in your fastn dashboard, then let each customer authenticate their own PeopleDoc account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PeopleDoc client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PeopleDoc account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PeopleDoc 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 PeopleDoc 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 finds the right employee document within scoped permissions, with every read audited.
Who maintains the PeopleDoc integration?
fastn does. When PeopleDoc 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 PeopleDoc 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 PeopleDoc 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 PeopleDoc 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 PeopleDoc integration?
A common starting point: connect their own PeopleDoc environment so your product reads employee records without an export. 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 PeopleDoc integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PeopleDoc does not change your per-connector cost. You can start free with 3 connected accounts.
Add PeopleDoc to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.