Human Resources · Integration
TriNet
Add TriNet to your product for your customers, and give your AI agents governed access to it.
TriNet is a professional employer organisation, which is a different arrangement from an HR system a company runs for itself. Under co-employment TriNet is the employer of record for payroll, benefits and compliance while the client directs the work, so employee, payroll and benefit records live on TriNet's side and the client reads them rather than owning the system. That shapes an embedded TriNet integration in two ways. What you can read is scoped to one client company at a time, and access is granted rather than self served: TriNet reviews and approves developer access before production credentials exist, so onboarding a customer includes their approval as a real step rather than an OAuth click. The data is payroll and benefits detail, about as sensitive as employee data gets, so only the fields you mapped ever travel and each read is recorded. Credentials sit with fastn, scoped to one client at a time.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each client connect their own TriNet account so your product reads their people data without anybody exporting a payroll report.
Read employee and company records so your product references the roster TriNet actually holds rather than a stale copy.
Read payroll results so downstream steps in your product run on what was really paid, not on what was expected.
Read time off so scheduling, capacity or approval steps in your product account for who is genuinely away.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about a client's headcount from the records TriNet holds, with the read logged.
An agent reports who is away in a given week before anybody commits to a delivery date.
An agent explains what changed between two payroll runs without exposing fields your product never mapped.
Example prompt
How many people are on the roster for this client, and who is scheduled to be off next week?
Set up TriNet in 4 steps
- 01Enable the TriNet connector in your fastn dashboard.
- 02Have each client complete TriNet's approval process and supply their own credentials, since production access is granted rather than self served.
- 03Map only the employee, payroll and time off fields your product genuinely needs, and leave the rest unmapped.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the TriNet integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TriNet integration without building it. Your customers connect their own TriNet 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 TriNet update is not your on-call problem.
- One integration serves your product and your agents. The same governed TriNet 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
Gusto
BambooHR
PaylocityOften used alongside
Tools the same teams tend to run next to TriNet, across other categories.
Slack
NetSuite
Notion
BoxTriNet integration FAQ
How do I add a TriNet integration to my product?
Enable the TriNet connector in your fastn dashboard, then let each customer authenticate their own TriNet account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TriNet client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TriNet account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TriNet 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 TriNet 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 a client's headcount from the records TriNet holds, with the read logged.
Who maintains the TriNet integration?
fastn does. When TriNet 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 TriNet 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 TriNet 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 TriNet 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 TriNet integration?
A common starting point: let each client connect their own TriNet account so your product reads their people data without anybody exporting a payroll report. 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 TriNet integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TriNet does not change your per-connector cost. You can start free with 3 connected accounts.
Add TriNet to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.