Human Resources · Integration
GoCo
Add GoCo to your product for your customers, and give your AI agents governed access to it.
Embed a GoCo integration so your customers can work their own HR data from inside your product, covering employees, time off, and onboarding. Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged, so you expose only what your product needs rather than the whole employee record. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync their employee roster into your product, mapped to the fields you actually need.
Read time off and leave data so scheduling in your product reflects who is away.
Read org structure so approvals and visibility in your product follow the customer's reporting lines.
Trigger your product when someone is hired, changes role, or leaves, so provisioning follows automatically.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up an employee's manager and department before routing a request.
An agent checks upcoming time off before proposing a schedule.
An agent reacts to a new hire or departure and starts the matching provisioning steps within governed permissions.
Example prompt
List employees starting in the next 30 days with their department and manager, plus anyone on leave that week.
Set up GoCo in 4 steps
- 01Open the GoCo connector from your fastn dashboard.
- 02Have each customer authenticate their own GoCo account.
- 03Map the employee, time off, and org fields 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 GoCo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a GoCo integration without building it. Your customers connect their own GoCo 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 GoCo update is not your on-call problem.
- One integration serves your product and your agents. The same governed GoCo 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
ADP Workforce Now
WorkdayOften used alongside
Tools the same teams tend to run next to GoCo, across other categories.
Slack
NetSuite
Notion
BoxGoCo integration FAQ
How do I add a GoCo integration to my product?
Enable the GoCo connector in your fastn dashboard, then let each customer authenticate their own GoCo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no GoCo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own GoCo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own GoCo 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 GoCo 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 looks up an employee's manager and department before routing a request.
Who maintains the GoCo integration?
fastn does. When GoCo 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 GoCo 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 GoCo 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 GoCo 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 GoCo integration?
A common starting point: sync their employee roster into your product, mapped to the fields you actually 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 GoCo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding GoCo does not change your per-connector cost. You can start free with 3 connected accounts.
Add GoCo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.