Human Resources · Integration
Legion
Add Legion to your product for your customers, and give your AI agents governed access to it.
Embed a Legion integration so your customers can see workforce schedules and worked hours inside your product instead of a separate console. Employee data is sensitive, so access is scoped per tenant, limited to the fields and locations you map, and every read and write is logged. fastn handles per-customer authentication, pagination and API upkeep, so a customer with an unusual location 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 connect their own Legion account so your product reads employee schedules and shifts.
Read worked hours and time records so your product reports on labour without a manual export.
Read and write availability or time off where a customer permits it, so a change reaches the schedule.
Scope reads to the locations and fields your product needs, so the rest of the employee record stays put.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks who is scheduled for a shift before answering a staffing question.
An agent summarises hours by location for a manager, with each read logged.
An agent submits a schedule or time-off change within governed permissions, audited per tenant.
Example prompt
Show shifts scheduled for next week at this location and flag any that are still unassigned.
Set up Legion in 4 steps
- 01Open the Legion connector from your fastn dashboard.
- 02Have each customer authenticate their own Legion account.
- 03Map the employee, schedule and time 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 Legion integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Legion integration without building it. Your customers connect their own Legion 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 Legion update is not your on-call problem.
- One integration serves your product and your agents. The same governed Legion 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
Gusto
BambooHROften used alongside
Tools the same teams tend to run next to Legion, across other categories.
Slack
NetSuite
Notion
BoxLegion integration FAQ
How do I add a Legion integration to my product?
Enable the Legion connector in your fastn dashboard, then let each customer authenticate their own Legion account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Legion client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Legion account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Legion 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 Legion 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 checks who is scheduled for a shift before answering a staffing question.
Who maintains the Legion integration?
fastn does. When Legion 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 Legion 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 Legion 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 Legion 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 Legion integration?
A common starting point: connect their own Legion account so your product reads employee schedules and shifts. 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 Legion integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Legion does not change your per-connector cost. You can start free with 3 connected accounts.
Add Legion to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.