Recruiting & ATS · Integration
Teamtailor
Add Teamtailor to your product for your customers, and give your AI agents governed access to it.
Teamtailor is an applicant tracking system with the career site attached, so a job is both a pipeline and a published page, and an integration usually touches both. The records are jobs with their departments and locations, candidates, the applications joining the two, the stages each application moves through, and the custom questions a job asked. Every employer designs their own pipeline, so stage names and question sets belong to them and mapping is configuration rather than code. Candidate records carry consent and retention obligations, so your product sees only the narrow slice of a candidate it mapped, held encrypted per tenant, with each read recorded. Stage changes arrive as events, so your product reacts when somebody moves rather than on the next scheduled read.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each employer connect their own Teamtailor account so jobs and applications flow into your product without an export.
Read a candidate's answers to that job's own questions, since screening detail sits there rather than on the profile.
Create or update a candidate and move an application between the stages that employer defined.
Publish or update a job so the career site and your product describe the same opening.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises the applications sitting at one stage and which of them have gone stale.
An agent moves a candidate forward or adds a note within scoped permissions, with the action attributed.
An agent answers where a named candidate is in the process without anyone opening the ATS.
Example prompt
Which candidates have sat at interview stage for over a week, and what did they answer on the screening questions?
Set up Teamtailor in 4 steps
- 01Enable the Teamtailor connector in your fastn dashboard.
- 02Have each employer authorise their own Teamtailor account with the least access your features need.
- 03Map the job, candidate, application and stage fields that employer uses, including each job's own questions.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Teamtailor integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Teamtailor integration without building it. Your customers connect their own Teamtailor 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 Teamtailor update is not your on-call problem.
- One integration serves your product and your agents. The same governed Teamtailor 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
AshbyOften used alongside
Tools the same teams tend to run next to Teamtailor, across other categories.
Slack
Notion
Box
DocusignTeamtailor integration FAQ
How do I add a Teamtailor integration to my product?
Enable the Teamtailor connector in your fastn dashboard, then let each customer authenticate their own Teamtailor account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Teamtailor client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Teamtailor account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Teamtailor 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 Teamtailor 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 summarises the applications sitting at one stage and which of them have gone stale.
Who maintains the Teamtailor integration?
fastn does. When Teamtailor 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 Teamtailor 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 Teamtailor?
Yes, through event triggers: a stage move where Teamtailor 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 Teamtailor integration?
A common starting point: let each employer connect their own Teamtailor account so jobs and applications flow into your product without an export. 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 Teamtailor integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Teamtailor does not change your per-connector cost. You can start free with 3 connected accounts.
Add Teamtailor to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.