Recruiting & ATS · Integration
Workable
Add Workable to your product for your customers, and give your AI agents governed access to it.
Workable is an applicant tracking system, so an integration is built around jobs and the candidates moving through the pipeline behind each one. An embedded Workable integration lists jobs and their pipelines, reads candidates with their application answers, attachments and evaluation scorecards, creates a candidate against a job, advances or disqualifies someone, and receives events when a stage changes or a hire is made. Two details shape the work. Every account is addressed by its own subdomain and authorised by its own token, so which customer you are talking to is settled by the hostname before a single field is read. And pipeline stages are defined per account and per job, meaning a stage called Screen in one customer's account is not the same object as the one next door, so stage mapping is setup rather than a constant. Consent and retention obligations ride along with a candidate record, so hold the narrowest set of fields your feature can justify and let the log account for every read. fastn stores those tokens per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Workable subdomain so hiring activity your product drives happens in the account their recruiters use.
Read candidates with their application answers and scorecards so your product works from the evidence, not a name and an email.
Create a candidate against the right job, or advance one, when the trigger for it happens in your product.
Map each account's own pipeline stages once at setup, since no two customers name or order them the same way.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises a candidate's answers and interview scorecards before a hiring manager reads anything.
An agent moves a candidate forward within scoped permissions, with the stage it set recorded.
An agent reports which candidates have been sitting at one stage longer than the team's own threshold.
Example prompt
Who has been stuck at interview stage for this role longest, and what did their scorecards say?
Set up Workable in 4 steps
- 01Enable the Workable connector in your fastn dashboard.
- 02Have each customer supply their own subdomain and access token, since both address and authorise their account.
- 03Map that account's pipeline stages, then map the candidate fields you can justify holding and no others.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Workable integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Workable integration without building it. Your customers connect their own Workable 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 a Workable update is not your on-call problem.
- One integration serves your product and your agents. The same governed Workable 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
Compare with
Greenhouse
Lever
SmartRecruitersOften used alongside
Tools the same teams tend to run next to Workable, across other categories.
Slack
Notion
Box
DocusignWorkable integration FAQ
How do I add a Workable integration to my product?
Enable the Workable connector in your fastn dashboard, then let each customer authenticate their own Workable account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Workable client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Workable account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Workable 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 Workable 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 summarises a candidate's answers and interview scorecards before a hiring manager reads anything.
Who maintains the Workable integration?
fastn does. When Workable 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 Workable 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 Workable?
Yes, through event triggers: a stage move where Workable 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 Workable integration?
A common starting point: let each customer connect their own Workable subdomain so hiring activity your product drives happens in the account their recruiters use. 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 Workable integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Workable does not change your per-connector cost. You can start free with 3 connected accounts.
Add Workable to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.