Recruiting & ATS · Integration
Recruitee
Add Recruitee to your product for your customers, and give your AI agents governed access to it.
Recruitee is collaborative hiring, so pipelines are configured per company and stage names are whatever that team decided, which makes stage mapping configuration rather than an enum you can hardcode. A candidate and an application are separate: the same person can apply to several openings, and treating the application as the unit avoids duplicating people. Notes and evaluations are where hiring decisions actually live, and they are the part a product usually wants to surface rather than the CV. Events are pushed rather than polled, which matters because a hiring pipeline is quiet for days and then moves in an hour. fastn keeps each customer's token scoped to their own account.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Recruitee account so hiring pipelines appear inside your product.
Read applications rather than candidates, so one person applying twice is not two records.
Map each company's own stage names as configuration rather than assuming a standard pipeline.
React when a candidate moves stage, rather than polling a mostly idle pipeline.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises where each candidate sits and which have been waiting longest.
An agent adds a note within governed permissions, with the write audited per tenant.
An agent reacts to a stage change and updates the record your product holds.
Example prompt
Which candidates have been sitting in the same stage for more than a week?
Set up Recruitee in 4 steps
- 01Enable the Recruitee connector from your fastn dashboard.
- 02Have each customer authorise their own Recruitee 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 Recruitee integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Recruitee integration without building it. Your customers connect their own Recruitee 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 Recruitee update is not your on-call problem.
- One integration serves your product and your agents. The same governed Recruitee 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
RecruiterflowOften used alongside
Tools the same teams tend to run next to Recruitee, across other categories.
Slack
Notion
Box
DocusignRecruitee integration FAQ
How do I add a Recruitee integration to my product?
Enable the Recruitee connector in your fastn dashboard, then let each customer authenticate their own Recruitee account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Recruitee client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Recruitee account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Recruitee 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 Recruitee 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 where each candidate sits and which have been waiting longest.
Who maintains the Recruitee integration?
fastn does. When Recruitee 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 Recruitee 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 Recruitee?
Yes, through event triggers: a stage move where Recruitee 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 Recruitee integration?
A common starting point: let a customer connect their own Recruitee account so hiring pipelines appear inside 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 Recruitee integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Recruitee does not change your per-connector cost. You can start free with 3 connected accounts.
Add Recruitee to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.