Recruiting & ATS · Integration
Recruiterflow
Add Recruiterflow to your product for your customers, and give your AI agents governed access to it.
Recruiterflow is built for recruiting agencies rather than in-house teams, and that changes the object model in a way that matters. Alongside jobs and candidates there are deals and clients, because an agency is running a sales process and a hiring process at the same time against the same data. An integration that only reads candidates will miss the half of the business the agency is actually paid for. Candidates are sourced in volume and deduplication is a live concern, so writing a candidate should check before it creates. fastn scopes each agency's key to them and keeps the API upkeep off your side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a recruiting agency connect their own Recruiterflow account so jobs and candidates appear in your product.
Read deals and clients alongside jobs, which is the commercial half agencies care about.
Create or update a candidate with a duplicate check, rather than adding another copy.
React when a candidate or deal changes stage, rather than polling.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which open jobs have no candidates in the final stages.
An agent adds a candidate within governed permissions, with the write audited per tenant.
An agent links a deal to its job and reports the value at risk.
Example prompt
Which open roles have no candidates past first interview, and what are those deals worth?
Set up Recruiterflow in 4 steps
- 01Enable the Recruiterflow connector from your fastn dashboard.
- 02Have each customer authorise their own Recruiterflow account, so calls run under their credentials rather than a shared key.
- 03Decide which job requisitions, candidates and applications your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Recruiterflow integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Recruiterflow integration without building it. Your customers connect their own Recruiterflow 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 Recruiterflow update is not your on-call problem.
- One integration serves your product and your agents. The same governed Recruiterflow 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
Recruitee
Greenhouse
LeverOften used alongside
Tools the same teams tend to run next to Recruiterflow, across other categories.
Slack
Notion
Box
DocusignRecruiterflow integration FAQ
How do I add a Recruiterflow integration to my product?
Enable the Recruiterflow connector in your fastn dashboard, then let each customer authenticate their own Recruiterflow account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Recruiterflow client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Recruiterflow account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Recruiterflow 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 Recruiterflow 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 reports which open jobs have no candidates in the final stages.
Who maintains the Recruiterflow integration?
fastn does. When Recruiterflow 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 Recruiterflow 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 Recruiterflow?
Yes, through event triggers: a stage move where Recruiterflow 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 Recruiterflow integration?
A common starting point: let a recruiting agency connect their own Recruiterflow account so jobs and candidates appear in 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 Recruiterflow integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Recruiterflow does not change your per-connector cost. You can start free with 3 connected accounts.
Add Recruiterflow to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.