Claude Teamtailor connectorWhat Claude can do in your Teamtailor account.
The Claude Teamtailor connector exposes 45 tools. 26 read your recruiting data, 19 change it (moves, tags, to-dos, questions, job edits). Below: what Claude can see, what it can change once your Company Admin allows it, and who can cut it off.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for a recruiting team
Instead of clicking from a job to its pipeline, then to a candidate, their scorecards and their messages, you ask Claude. It reads the same data your Teamtailor login shows, summarises it, and, if your role allows it, carries out the change you ask for. By default, though, Teamtailor only opens reading.
Prepare an interview in two minutes. get_candidate brings back the profile and history, list_scorecards lines up previous evaluations, and get_meeting_event_transcript gives the exact words of the last call.
See where hiring is stuck. get_job_pipeline counts candidates per stage across your open roles, and list_applications pulls the ones waiting in a given stage with a given rating.
Act on what you find. move_application_to_stage moves the finalist to the offer stage, create_todo sets tomorrow's follow-up, and update_job rewrites an ad that is not attracting anyone.
Now what the sheet does not say. Every write depends on your Company Admin: Teamtailor gives all roles read access by default, and Create & modify or Delete must be granted role by role. Claude also cannot create a candidate or add one to a job with the tools listed here, even though Teamtailor's article mentions such actions. And nothing runs on its own: no tool fires when an application arrives. For that, an automation tool does a different job; the Integrations hub covers it.
The vocabulary in one minute
Five words you will meet while plugging Teamtailor in.
- Connector
- The link you set up once between Claude and an account you already use, so Claude can work in it while answering.
- Tool
- One named action a connector opens to Claude. Claude picks the tools it needs by itself; the directory sheet lists them all.
- Authorization
- The service's own sign-in screen, where you give Claude the access it will use. Granted once per person and revocable.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the conversation at that point.
- MCP
- The common standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Plug Teamtailor into Claude in three steps
- 01
Find Teamtailor in Claude
In Claude's settings, open Customize, then Connectors, and find Teamtailor in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first so each member can then sign in individually.
- 02
Start the connection
Click Connect on its row, then sign in to Teamtailor in the window Teamtailor opens. If you have several Teamtailor accounts, pick the one to connect. When the link breaks, use Disconnect and connect again.
- 03
Read the authorization screen
Go through Teamtailor's authorization screen before clicking to accept. That screen belongs to Teamtailor, not to Claude, and it sets what the access covers. You can withdraw it later from Teamtailor as well.
The 45 tools, sorted by what they do
Teamtailor gives Claude 45 tools: 26 that read your account, 19 that change something in it.
Two groups: what Claude reads, and what it changes. Names stay as Claude shows them, in English. Teamtailor itself sorts the writes into Create & modify and Delete access levels.
- 26 read
- 19 write
What Claude reads (26)
26 toolsTwenty-six tools that consult jobs, candidates, meetings and settings without changing anything.
get_application
Opens one application in full: the scorecards filled in by interviewers, internal comments, messages exchanged with the candidate and the activity around it, all in one read.
get_candidate
Pulls a candidate's profile with their applications, attached files, competencies and recent activity, so Claude can summarise who they are and where they stand.
get_job
Reads a job in detail: the ad content, the application form and the recruitment process attached to it.
get_job_pipeline
Shows the recruitment pipeline of one or several jobs, with how many candidates sit at each stage.
get_meeting_event
Gives the details of one meeting with a candidate: participants, and the Co-pilot summaries attached to it.
get_meeting_event_transcript
Retrieves the full transcript of a recorded candidate meeting, so Claude can quote what was actually said rather than a summary.
get_question
Shows a single screening question with its answer options and its translations.
list_applications
Lists applications to your jobs and filters them by job, by stage or by rating, which makes shortlists quick to pull.
list_candidates
Searches your candidate base by name, email, tags, status, job, stage and more.
list_comments
Reads the internal comments your team left on a candidate, the notes the candidate never sees.
list_custom_fields
Lists the custom fields your account uses and the options each one accepts.
list_departments
Returns the list of departments defined in your Teamtailor account.
list_divisions
Returns the divisions set up in your account, the second grouping level Teamtailor lists beside departments.
list_employees
Lists the people in your Teamtailor account and filters them by role, department, division or location.
list_interview_kits
Lists your reusable interview kit templates, the sets of questions and guidance interviewers follow.
list_jobs
Lists jobs and filters them by status or down to the ones you own.
list_locations
Returns the locations recorded in your account, the offices or sites jobs and employees are attached to.
list_meetings
Lists upcoming and past meetings with candidates.
list_messages
Shows the history of messages exchanged with one candidate.
list_questions
Lists the screening questions available in your account.
list_roles
Returns the user roles defined in your Teamtailor account.
list_scorecards
Reads the scorecards and evaluations filed for a candidate.
list_skills_and_traits
Lists the skills and traits available for scorecards in your account.
list_tags
Lists the tags already used on candidates and jobs.
list_timeline
Walks through a candidate's activity over time.
list_todos
Lists to-dos across jobs, candidates and applications, so pending follow-ups stop hiding in different screens.
What Claude changes (19)
19 toolsNineteen tools that edit your account. Each one needs the matching access level on your Teamtailor role, and no source details a confirmation specific to it.
add_job_interview_kit
Approval: see the ruleAttaches an interview kit to a job, or to one stage of it, so interviewers get the right guide at the right moment.
add_job_question
Approval: see the ruleAdds a question to a job's application form.
add_job_skill_or_trait
Approval: see the ruleAdds a skill or trait to a job's scorecard, so interviewers rate candidates on it.
add_tag
Approval: see the rulePuts a tag on a candidate or a job.
archive_question
Approval: see the ruleArchives a screening question. Teamtailor files this one under its Delete access level.
complete_todo
Approval: see the ruleMarks a to-do as done, or reopens it if it was closed too soon.
create_question
Approval: see the ruleCreates a new screening question in your account.
create_todo
Approval: see the ruleCreates a to-do, with a due date and an assignee if you want them.
delete_todo
Approval: see the ruleDeletes a to-do. Teamtailor classes this action at the Delete access level.
move_application_to_stage
Approval: see the ruleMoves a candidate to another stage of the recruitment process.
remove_job_interview_kit
Approval: see the ruleDetaches an interview kit from a job.
remove_job_question
Approval: see the ruleTakes a question off a job's application form.
remove_job_skill_or_trait
Approval: see the ruleRemoves a skill or trait from a job's scorecard.
remove_tag
Approval: see the ruleRemoves a tag from a candidate or a job.
set_custom_field
Approval: see the ruleSets, updates or clears the value of a custom field on a candidate or a job.
unarchive_question
Approval: see the ruleBrings an archived screening question back into use.
update_job
Approval: see the ruleEdits a job's details, such as its title, its description or the settings of its application form.
update_question
Approval: see the ruleEdits an existing screening question, its wording or its setup, without having to archive it and start over.
update_todo
Approval: see the ruleChanges a to-do's text, due date or assignee.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The prompt shows up in the chat, right when it matters.
Two layers stack here. On the Claude side, Team and Enterprise owners decide whether a member may let some actions through without being asked, and they can cap what a connector may do for the whole organization. On the Teamtailor side, Company Admins choose which roles may connect an assistant and whether each role gets read, Create & modify or Delete access. An action has to pass both your own Teamtailor permissions and that role level. Everything Claude does is logged in Teamtailor's Audit log under your name.
Which plans it is available on
Of the 819 sheets in the official directory, none shows availability per plan. The per-connector answer is published nowhere: a real gap in the catalogue.
The general rule is public: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can sign in. On Teamtailor's side, the MCP add-on has to be switched on by a Company Admin. For the current state on Claude's side, look at the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a candidate applies, a stage changes or an interview ends.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools nor guarantee their behaviour. Teamtailor adds its own disclaimer: it runs the server, not the assistant you connect. Only Teamtailor documents this connector, with no Claude help article. For an HR tool that plays a different role, see the Claude bamboohr connector.
Need help connecting Teamtailor to Claude?
A person reads every message.
