Recruiting & ATS · Integration
Crelate
Add Crelate to your product for your customers, and give your AI agents governed access to it.
Embed a Crelate integration so your customers can work their own candidates, jobs, contacts, companies, and hiring pipelines from inside your product, with governed agent access to the same records. 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 authorisation and API upkeep, so onboarding another agency or instance is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own Crelate candidates and jobs into your product, mapped to their fields.
Create or update a candidate record from your product so recruiters do not re-key the same details.
Read pipeline stages and activities so hiring progress shows up where your users already work.
Trigger your product when a candidate moves stage, a job opens, or a placement is made.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a candidate's history and current stage before drafting outreach.
An agent updates a candidate or logs an activity within governed permissions.
An agent reacts to a stage change and runs the next recruiter task.
Example prompt
List candidates who have sat in the interview stage for more than 10 days and name the recruiter on each.
Set up Crelate in 4 steps
- 01Open the Crelate connector from your fastn dashboard.
- 02Have each customer authenticate their own Crelate account.
- 03Map the candidate, job, and pipeline 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 Crelate integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Crelate integration without building it. Your customers connect their own Crelate 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 Crelate update is not your on-call problem.
- One integration serves your product and your agents. The same governed Crelate 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
Ashby
CATSWorks well with
BambooHROften used alongside
Tools the same teams tend to run next to Crelate, across other categories.
Slack
Notion
Box
DocusignCrelate integration FAQ
How do I add a Crelate integration to my product?
Enable the Crelate connector in your fastn dashboard, then let each customer authenticate their own Crelate account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Crelate client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Crelate account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Crelate 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 Crelate 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 history and current stage before drafting outreach.
Who maintains the Crelate integration?
fastn does. When Crelate 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 Crelate 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 Crelate?
Yes, through event triggers: a stage move where Crelate 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 Crelate integration?
A common starting point: read their own Crelate candidates and jobs 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 Crelate integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Crelate does not change your per-connector cost. You can start free with 3 connected accounts.
Add Crelate to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.