Recruiting & ATS · Integration
SmartRecruiters
Add SmartRecruiters to your product for your customers, and give your AI agents governed access to it.
SmartRecruiters has a public job feed on one side and a private pipeline on the other, and an integration usually touches both. An embedded SmartRecruiters integration reads jobs and their postings, reads and creates candidates and applications, attaches resumes and screening results, moves a candidate between statuses, and reacts to webhook events when something changes. The part needing care is that a candidate record carries consent and retention obligations of its own, so your product should hold as little as it can and read the rest on demand. Hiring processes are configurable, so statuses differ from company to company and the stage mapping belongs per tenant rather than in your code. fastn keeps each company's credentials and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SmartRecruiters company so hiring data reaches your product with no per-customer build.
Create a candidate and an application from your product, with the source recorded so attribution survives.
Write a screening or assessment result onto the application so recruiters see it where they already work.
React to a status change so your product acts when a candidate advances rather than on a nightly read.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises a pipeline: how many candidates sit at each status and which have gone quiet.
An agent moves a candidate forward after a human decision, with the transition attributed and audited.
An agent reads an application and its attachments to answer a question about one candidate.
Example prompt
Which candidates on this requisition have been waiting at interview stage for more than a week?
Set up SmartRecruiters in 4 steps
- 01Enable the SmartRecruiters connector in your fastn dashboard.
- 02Have each customer authorise their own SmartRecruiters company so candidate data stays inside it.
- 03Map that company's own statuses and the candidate and application fields your product needs, then enable the events you react to.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SmartRecruiters integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SmartRecruiters integration without building it. Your customers connect their own SmartRecruiters 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 SmartRecruiters update is not your on-call problem.
- One integration serves your product and your agents. The same governed SmartRecruiters 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
Often used alongside
Tools the same teams tend to run next to SmartRecruiters, across other categories.
SmartRecruiters integration FAQ
How do I add a SmartRecruiters integration to my product?
Enable the SmartRecruiters connector in your fastn dashboard, then let each customer authenticate their own SmartRecruiters account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SmartRecruiters client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SmartRecruiters account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SmartRecruiters 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 SmartRecruiters 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 pipeline: how many candidates sit at each status and which have gone quiet.
Who maintains the SmartRecruiters integration?
fastn does. When SmartRecruiters 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 SmartRecruiters 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 SmartRecruiters?
Yes, through event triggers: a stage move where SmartRecruiters 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 SmartRecruiters integration?
A common starting point: let each customer connect their own SmartRecruiters company so hiring data reaches your product with no per-customer build. 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 SmartRecruiters integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SmartRecruiters does not change your per-connector cost. You can start free with 3 connected accounts.
Add SmartRecruiters to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.