Recruiting & ATS · Integration
JobAdder
Add JobAdder to your product for your customers, and give your AI agents governed access to it.
Embed a JobAdder integration so your customers can run their own recruiting data inside your product rather than exporting spreadsheets. 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, field mapping, and API upkeep, so an agency with an unusual JobAdder setup needs no code from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own jobs and candidate records into your product, mapped to their own fields.
Create or update a candidate and attach an application when a submission happens in your product.
Read application stages and placements so hiring progress is visible where users already work.
Trigger your product when a candidate is added or an application changes stage.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads open jobs and shortlisted candidates before it summarises pipeline health.
An agent updates a candidate or moves an application within governed permissions, with each action logged.
An agent reacts to a new application and prepares the screening notes for a recruiter.
Example prompt
List candidates who applied to this job in the last week and show which stage each application is in.
Set up JobAdder in 4 steps
- 01Open the JobAdder connector from your fastn dashboard.
- 02Have each customer authorise their own JobAdder account with OAuth.
- 03Map the job, candidate, and application fields 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 JobAdder integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a JobAdder integration without building it. Your customers connect their own JobAdder 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 JobAdder update is not your on-call problem.
- One integration serves your product and your agents. The same governed JobAdder 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
GreenhouseWorks well with
Workday
BambooHROften used alongside
Tools the same teams tend to run next to JobAdder, across other categories.
Slack
Notion
Box
DocusignJobAdder integration FAQ
How do I add a JobAdder integration to my product?
Enable the JobAdder connector in your fastn dashboard, then let each customer authenticate their own JobAdder account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no JobAdder client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own JobAdder account?
Yes. Every connection is scoped to the individual customer, so each authorises their own JobAdder 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 JobAdder 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 open jobs and shortlisted candidates before it summarises pipeline health.
Who maintains the JobAdder integration?
fastn does. When JobAdder 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 JobAdder 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 JobAdder?
Yes, through event triggers: a stage move where JobAdder 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 JobAdder integration?
A common starting point: read their own jobs and candidate records into your product, mapped to their own fields. 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 JobAdder integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding JobAdder does not change your per-connector cost. You can start free with 3 connected accounts.
Add JobAdder to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.