Recruiting & ATS · Integration
Ashby
Add Ashby to your product for your customers, and give your AI agents governed access to it.
Embed an Ashby integration so your customers can work their own jobs, candidates, applications, interviews, and offers from inside your product, and so your agents can read that hiring data under per-tenant governance. Candidate data is sensitive, so access is scoped per tenant and limited to the fields you map, and every read and write is logged. fastn handles each customer's authentication and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read open jobs and their pipelines into your product.
Read candidates and applications so hiring context sits next to the rest of your product's data.
Create candidates, add notes, or advance an application stage from inside your product.
Trigger your product when an interview is scheduled, a stage changes, or an offer is made.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a candidate's application history and interview feedback before drafting a summary.
An agent advances or rejects an application within governed permissions, with the action attributed.
An agent reacts to a signed offer and starts the onboarding workflow.
Example prompt
List candidates in the onsite stage with no interview scheduled and show how long they have waited.
Set up Ashby in 4 steps
- 01Open the Ashby connector from your fastn dashboard.
- 02Have each customer authenticate their own Ashby account with the required scopes.
- 03Map the job, candidate, and interview 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 Ashby integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Ashby integration without building it. Your customers connect their own Ashby account inside your product and work their job requisitions, candidates and applications there, with no per-customer code on your side.
- Handle the part that actually costs time: candidate records are personal data with consent and retention rules attached. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Ashby update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ashby connection powers in-product features and gives AI agents scoped, audited access, so you keep hiring pipelines moving without manual re-entry without wiring it twice.
Used by these teams
Works well with
AngelList
Slack
NotionOften used alongside
Tools the same teams tend to run next to Ashby, across other categories.
Box
Docusign
Jira
AsanaAshby integration FAQ
How do I add an Ashby integration to my product?
Enable the Ashby connector in your fastn dashboard, then let each customer authenticate their own Ashby account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ashby client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ashby account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ashby account and only ever sees their own job requisitions, candidates and applications. 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 Ashby 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 reads a candidate's application history and interview feedback before drafting a summary.
Who maintains the Ashby integration?
fastn does. When Ashby 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 candidate data from Ashby handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. That matters more here than in most systems, because candidate records are personal data that carry consent and retention obligations.
Can my product react when a candidate's status changes in Ashby?
Yes, through event triggers: a stage move where Ashby owns the pipeline, or a completed assessment, a returned report or a finished reference where it owns one step in it. Events are delivered per tenant and can be replayed after an outage, so a hiring team does not silently lose an update while your product was unreachable.
What can I build with the Ashby integration?
A common starting point: read open jobs and their pipelines into your product. 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 Ashby integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ashby does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ashby to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.