Recruiting & ATS · Integration
CATS
Add CATS to your product for your customers, and give your AI agents governed access to it.
CATS is applicant tracking, so the records are candidates and their resumes, job orders waiting to be filled, the pipelines that connect one to the other, submissions to a client or hiring manager, and the activities logged along the way. Pipelines are the part worth understanding. A candidate is not simply at a stage, because they sit in a pipeline per job order, so the same person can be advancing on one role and rejected on another at the same moment, and any status your product displays has to say which job order it belongs to. Resumes and notes are personal data carrying retention expectations, which is why field-level scoping matters here. fastn keeps every account's credentials isolated per tenant and maintains the connector as the API moves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each recruiting team connect their own CATS account so an application your product captures becomes a candidate on the right job order.
Read a candidate's pipelines so your product shows status per job order instead of one misleading stage.
Log activities and record submissions from your product, keeping the hiring trail complete without double entry.
React when a candidate advances or a job order is filled, exposing only the candidate fields you mapped.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists who is in a job order's pipeline and what the last activity on each was.
An agent moves a candidate forward or records a submission inside scoped permissions, with the action attributed.
An agent drafts a summary of one candidate against one role, reading a single account's data.
Example prompt
Which candidates are in this job order's pipeline, and who has heard nothing since their submission?
Set up CATS in 4 steps
- 01Enable the CATS connector from your fastn dashboard.
- 02Have each customer authorise their own CATS account, so calls run under their credentials rather than a shared key.
- 03Decide which candidates, job orders, pipelines and submissions your product needs, and note that a candidate sits in a pipeline per job order, so any status must say which order it refers to.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the CATS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CATS integration without building it. Your customers connect their own CATS 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 CATS update is not your on-call problem.
- One integration serves your product and your agents. The same governed CATS 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
Crelate
JobAdder
ManatalOften used alongside
Tools the same teams tend to run next to CATS, across other categories.
Slack
Notion
Box
DocusignCATS integration FAQ
How do I add a CATS integration to my product?
Enable the CATS connector in your fastn dashboard, then let each customer authenticate their own CATS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CATS client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CATS account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CATS 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 CATS 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 lists who is in a job order's pipeline and what the last activity on each was.
Who maintains the CATS integration?
fastn does. When CATS 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 CATS 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 CATS?
Yes, through event triggers: a stage move where CATS 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 CATS integration?
A common starting point: let each recruiting team connect their own CATS account so an application your product captures becomes a candidate on the right job order. 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 CATS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CATS does not change your per-connector cost. You can start free with 3 connected accounts.
Add CATS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.