Recruiting & ATS · Integration
Jobscience
Add Jobscience to your product for your customers, and give your AI agents governed access to it.
Embed a Jobscience integration so your customers can bring their own recruiting records into your product instead of exporting them. Recruiting data is sensitive, so access is scoped per tenant, restricted to the fields you map, and every read and write is logged. fastn handles per-customer authentication and field mapping, so a customer with a heavily customised Jobscience 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 requisitions and candidate records into your product, mapped to their fields.
Create or update a candidate and its application when someone applies through your product.
Read application stages so hiring progress shows up where recruiters already work.
Trigger your workflows when a candidate is created 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 requisitions and their candidates before summarising pipeline status.
An agent updates a candidate record within governed permissions, with each write audited.
An agent reacts to a stage change and prepares the next step for the recruiter.
Example prompt
List open requisitions with fewer than three active candidates and show the newest application on each.
Set up Jobscience in 4 steps
- 01Open the Jobscience connector from your fastn dashboard.
- 02Have each customer authenticate their own Jobscience instance.
- 03Map the requisition, 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 Jobscience integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Jobscience integration without building it. Your customers connect their own Jobscience 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 Jobscience update is not your on-call problem.
- One integration serves your product and your agents. The same governed Jobscience 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
Salesforce
WorkdayOften used alongside
Tools the same teams tend to run next to Jobscience, across other categories.
Slack
Notion
Box
DocusignJobscience integration FAQ
How do I add a Jobscience integration to my product?
Enable the Jobscience connector in your fastn dashboard, then let each customer authenticate their own Jobscience account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Jobscience client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Jobscience account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Jobscience 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 Jobscience 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 requisitions and their candidates before summarising pipeline status.
Who maintains the Jobscience integration?
fastn does. When Jobscience 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 Jobscience 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 Jobscience?
Yes, through event triggers: a stage move where Jobscience 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 Jobscience integration?
A common starting point: read their own requisitions and candidate records into your product, mapped to their 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 Jobscience integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Jobscience does not change your per-connector cost. You can start free with 3 connected accounts.
Add Jobscience to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.