Human Resources · Integration
WorkPro
Add WorkPro to your product for your customers, and give your AI agents governed access to it.
WorkPro is employment compliance rather than an HR system of record. It runs and stores the checks an employer needs before and during employment: police and background checks, work rights and visa entitlement verification, licence and qualification validation, and the industry induction modules a worker has to complete. The reason to embed it is that those records expire. A licence lapses, a visa condition changes, an induction goes out of date, and the integration worth having is the one that notices before somebody turns up to work unqualified. WorkPro is designed to sit beside an applicant tracking system, an HR system and payroll rather than replace any of them, so what your product reads is a compliance profile attached to a worker who already exists elsewhere. This is about as sensitive as people data gets, so your product should carry the narrowest slice of it a feature needs, and every read is recorded. fastn holds each customer's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own WorkPro account so compliance evidence stays in the system their auditors already accept.
Trigger a check or an induction when somebody is hired in your product, instead of a coordinator emailing a form.
Read verification and induction status per worker so your product can tell whether someone is cleared to be scheduled.
React when a licence, work right or induction approaches expiry, while there is still time to renew it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which workers have compliance records expiring inside the next month.
An agent checks whether a named worker is cleared for a role before anybody schedules them.
An agent orders a check inside scoped permissions, and the employer it was ordered for is recorded on the call.
Example prompt
Who on this roster has a licence or induction expiring in the next thirty days?
Set up WorkPro in 4 steps
- 01Enable the WorkPro connector in your fastn dashboard.
- 02Have each customer authorise their own account so checks are ordered and billed against them.
- 03Map only the check types, induction modules and expiry fields your product needs, and leave the rest of the profile untouched.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the WorkPro integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WorkPro integration without building it. Your customers connect their own WorkPro 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 WorkPro update is not your on-call problem.
- One integration serves your product and your agents. The same governed WorkPro 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
Personio
DeputyOften used alongside
Tools the same teams tend to run next to WorkPro, across other categories.
Slack
NetSuite
Notion
BoxWorkPro integration FAQ
How do I add a WorkPro integration to my product?
Enable the WorkPro connector in your fastn dashboard, then let each customer authenticate their own WorkPro account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WorkPro client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own WorkPro account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WorkPro 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 WorkPro 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 reports which workers have compliance records expiring inside the next month.
Who maintains the WorkPro integration?
fastn does. When WorkPro 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 WorkPro 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 WorkPro 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 WorkPro 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 WorkPro integration?
A common starting point: let each customer connect their own WorkPro account so compliance evidence stays in the system their auditors already accept. 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 WorkPro integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WorkPro does not change your per-connector cost. You can start free with 3 connected accounts.
Add WorkPro to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.