Recruiting & ATS · Integration
LiveHire
Add LiveHire to your product for your customers, and give your AI agents governed access to it.
Embed a LiveHire integration so your customers can work their own talent pipeline from inside your product rather than a separate console. 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 and API upkeep, so a customer with an unusual hiring process 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 LiveHire account so your product reads their candidates and talent pools.
Create a candidate from an application captured in your product, so nothing is retyped.
Read requisitions and their status so your product shows what a customer is hiring for.
Read application stages so a hiring manager sees progress without a second login.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a candidate's stage and history before drafting an update.
An agent reports which requisitions have candidates waiting on a decision.
An agent updates a candidate record within governed permissions, with each action audited.
Example prompt
List candidates in this talent pool who applied in the last 30 days and show the stage each one reached.
Set up LiveHire in 4 steps
- 01Open the LiveHire connector from your fastn dashboard.
- 02Have each customer authenticate their own LiveHire account.
- 03Map the candidate, talent pool and requisition fields your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the LiveHire integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a LiveHire integration without building it. Your customers connect their own LiveHire 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 LiveHire update is not your on-call problem.
- One integration serves your product and your agents. The same governed LiveHire 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
LeverWorks well with
WorkdayOften used alongside
Tools the same teams tend to run next to LiveHire, across other categories.
Slack
Notion
Box
DocusignLiveHire integration FAQ
How do I add a LiveHire integration to my product?
Enable the LiveHire connector in your fastn dashboard, then let each customer authenticate their own LiveHire account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LiveHire client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own LiveHire account?
Yes. Every connection is scoped to the individual customer, so each authorises their own LiveHire 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 LiveHire 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 history before drafting an update.
Who maintains the LiveHire integration?
fastn does. When LiveHire 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 LiveHire 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 LiveHire?
Yes, through event triggers: a stage move where LiveHire 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 LiveHire integration?
A common starting point: connect their own LiveHire account so your product reads their candidates and talent pools. 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 LiveHire integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LiveHire does not change your per-connector cost. You can start free with 3 connected accounts.
Add LiveHire to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.