Recruiting & ATS · Integration
Manatal
Add Manatal to your product for your customers, and give your AI agents governed access to it.
Embed a Manatal integration so recruiters work their own applicant tracking inside your product, with each customer connecting their own account rather than routing through a shared key. Jobs, candidates, pipeline stages and activities are read and written per tenant, and access is limited to the fields you map, which matters because candidate data is sensitive and its access rules are stricter than most systems. A new application or a stage change can trigger your product immediately, so screening and scheduling do not wait for a poll. fastn owns the auth, retries and API upkeep, and the same governed connection gives your AI agents scoped, audited access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Manatal account so their jobs and candidates are worked inside your product.
Create or update a candidate from your product, including the source that brought them in.
Move a candidate to the next pipeline stage from your product while the recruiter keeps working in Manatal.
React to a new application or a stage change with an event trigger so screening and scheduling run immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent screens new applications against a role and explains its shortlist, reading the customer's own candidate data.
An agent updates a candidate or adds a note within scoped permissions, with the write audited.
An agent reports which roles are stalling and where candidates drop out of the pipeline.
Example prompt
Which candidates in this Manatal pipeline have been waiting longest, and who should we move forward?
Set up Manatal in 4 steps
- 01Enable the Manatal connector in your fastn dashboard.
- 02Have each customer authorise their own Manatal account so calls run under their credentials.
- 03Map only the job, candidate and pipeline fields your product needs, then enable triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Manatal integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Manatal integration without building it. Your customers connect their own Manatal 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 Manatal update is not your on-call problem.
- One integration serves your product and your agents. The same governed Manatal 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
Lever
JobAdderOften used alongside
Tools the same teams tend to run next to Manatal, across other categories.
Slack
Notion
Box
DocusignManatal integration FAQ
How do I add a Manatal integration to my product?
Enable the Manatal connector in your fastn dashboard, then let each customer authenticate their own Manatal account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Manatal client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Manatal account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Manatal 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 Manatal 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 screens new applications against a role and explains its shortlist, reading the customer's own candidate data.
Who maintains the Manatal integration?
fastn does. When Manatal 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 Manatal 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 Manatal?
Yes, through event triggers: a stage move where Manatal 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 Manatal integration?
A common starting point: connect their own Manatal account so their jobs and candidates are worked inside your product. 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 Manatal integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Manatal does not change your per-connector cost. You can start free with 3 connected accounts.
Add Manatal to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.