Recruiting & ATS · Integration
Lever
Add Lever to your product for your customers, and give your AI agents governed access to it.
Embed a Lever integration so your customers can run recruiting work from inside your product instead of tabbing into their ATS. Candidate data is sensitive, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. fastn handles per-customer authentication, pagination, rate limits and API upkeep, so a customer with an unusual pipeline needs no code from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lever account so your product reads their job postings and candidates.
Create a candidate from an application captured in your product, so nothing is retyped into the ATS.
Read pipeline stages and interview feedback so your product shows where a candidate actually is.
Trigger your workflow when a candidate is hired or archived, so onboarding or removal starts on time.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a candidate's stage and feedback before drafting an update for a hiring manager.
An agent adds a note or moves a candidate within governed permissions, with each action audited.
An agent reports which postings have candidates waiting on a decision.
Example prompt
List candidates in the onsite stage for this posting and show how long each has been waiting.
Set up Lever in 4 steps
- 01Open the Lever connector from your fastn dashboard.
- 02Have each customer authorise their own Lever account with the scopes you need.
- 03Map the postings, candidate fields and stages your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Lever integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lever integration without building it. Your customers connect their own Lever 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 Lever update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lever 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
AshbyWorks well with
WorkdayOften used alongside
Tools the same teams tend to run next to Lever, across other categories.
Slack
Notion
Box
DocusignLever integration FAQ
How do I add a Lever integration to my product?
Enable the Lever connector in your fastn dashboard, then let each customer authenticate their own Lever account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lever client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lever account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lever 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 Lever 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 reads a candidate's stage and feedback before drafting an update for a hiring manager.
Who maintains the Lever integration?
fastn does. When Lever 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 Lever 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 Lever?
Yes, through event triggers: a stage move where Lever 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 Lever integration?
A common starting point: connect their own Lever account so your product reads their job postings and candidates. 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 Lever integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lever does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lever to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.