Human Resources · Integration
Namely
Add Namely to your product for your customers, and give your AI agents governed access to it.
Embed a Namely integration so your product works from the employee data its customers already maintain in their HRIS, without anyone maintaining a second list of people. HR data is sensitive and its access rules are stricter than most systems, so access is scoped per tenant, limited to the fields you map, and every read and write is logged: your product sees what it needs rather than the whole employee record. fastn handles per-customer authentication, token refresh, pagination and API upkeep, so a new hire or a departure can drive the downstream steps automatically.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Namely account so your product reads employees, job titles and reporting lines.
Provision access in your product when someone is hired, and remove it when they leave, driven by the HRIS rather than a ticket.
Read the org structure so your product's approvals and routing follow the customer's real reporting lines.
Map only the employee fields your product needs, so sensitive data you have no use for is never requested.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up an employee's role and manager before it routes an approval.
An agent reads who is out of office this week and adjusts a schedule accordingly.
An agent updates a mapped employee field within governed permissions, with the write logged.
Example prompt
Show everyone who joined in the last 30 days with their manager and confirm each has completed onboarding.
Set up Namely in 4 steps
- 01Open the Namely connector from your fastn dashboard.
- 02Have each customer authenticate their own Namely account with the scopes your product needs.
- 03Map the employee fields, org data and events 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 Namely integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Namely integration without building it. Your customers connect their own Namely 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 Namely update is not your on-call problem.
- One integration serves your product and your agents. The same governed Namely 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
Workday
HiBobOften used alongside
Tools the same teams tend to run next to Namely, across other categories.
Slack
NetSuite
Notion
BoxNamely integration FAQ
How do I add a Namely integration to my product?
Enable the Namely connector in your fastn dashboard, then let each customer authenticate their own Namely account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Namely client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Namely account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Namely 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 Namely 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 role and manager before it routes an approval.
Who maintains the Namely integration?
fastn does. When Namely 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 Namely 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 Namely 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 Namely 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 Namely integration?
A common starting point: connect their own Namely account so your product reads employees, job titles and reporting lines. 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 Namely integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Namely does not change your per-connector cost. You can start free with 3 connected accounts.
Add Namely to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.