Claude Ashby connectorWhat Claude can do in your Ashby account.
The Claude Ashby connector exposes 16 tools. 12 read your recruiting data, 4 change something in it. Below: what Claude finds in your ATS, what it can move or create, the admin switch that comes first, and the limits Ashby publishes.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your hiring team
Instead of clicking through the pipeline board, candidate tabs and your task inbox, you ask Claude in plain words. It picks the right Ashby tool, pulls the profile, the stage counts or your pending scorecards, and answers in the conversation. Four tools go further and change records, one of them only after you approve a draft.
Walk into every interview prepared. get_upcoming_interviews lists your week, then get_interview_details hands you the candidate's background, the panel and the hiring team for the next slot. No more opening three tabs in the lobby.
Read the pipeline without building a report. get_job_pipeline counts people per stage and compares several jobs, and filter_records answers pointed questions like how many offers are still out this month.
Log decisions while they are fresh. After a debrief, change_application_stage moves the finalist and add_note_to_candidate drafts the summary note you then approve.
What it will not do: nothing runs on its own. No tool wakes up when a candidate applies or a scorecard lands; Claude acts only while you talk to it. It never sees more than your Ashby role allows, and your own scorecards are the only ones it can pull. For background jobs triggered by ATS events, an automation tool is the right fit; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while plugging Ashby in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, revocable anytime.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Ashby.
Connect Ashby to Claude in three steps
- 01
Find Ashby in Claude
In Claude's settings, open Customize, then Connectors, and look for Ashby in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on the Ashby row, then log in to Ashby in the window Ashby opens on its own side. If the link ever breaks later, hit Disconnect and connect again.
- 03
Read the authorization screen
Go through Ashby's access screen before you approve it. That screen belongs to the service, not to Claude, and it sets what the access covers. You can also withdraw that access later from the Ashby side.
The 16 Claude Ashby connector tools, sorted by what they do
Ashby gives Claude 16 tools: 12 that read your account, 4 that change something in it.
Two groups: what Claude reads, and what it changes. Names stay exactly as Claude shows them.
- 12 read
- 4 write
What Claude reads (12)
12 toolsTwelve tools that look at your recruiting data without touching it.
describe_object_fields
Works backstage: before a filtered search, Claude uses it to learn which fields a given record type can be filtered on. You never call it yourself, and it shows you nothing on its own.
filter_records
Pulls every record that matches your criteria across candidates, applications, jobs, postings, openings, scheduled interviews and offers. It can also return a bare count instead of the full list.
search_records_by_name
Turns a name you type into the right Ashby record: a candidate, a job, an application or an email template. Most conversations start here, because the other tools need the record it finds.
get_record_details
Fetches the complete content of records Claude has already located, for jobs, postings, applications, email templates, openings, scheduled interviews and offers. Think of it as the second step after a search.
get_candidate
Opens a candidate's file in depth: resume, interview feedback, emails, texts, notes, interview transcripts, referrals, follow-ups and form submissions. Claude can then summarize or search inside all of it.
get_interview_plan
Lays out the sequence of stages a candidate goes through for one job or one application, from first screen to the last step your team configured.
get_interview_details
Builds a prep sheet for one specific interview: who the candidate is, a résumé summary, who sits on the panel and who leads hiring. Ashby suggests calling it just before you walk in.
get_job_pipeline
Counts the candidates sitting at each stage of a job's pipeline, and can line several jobs up side by side for comparison.
get_pending_tasks
Gathers what Ashby is waiting on from you: scorecards you still owe, approvals, follow-ups, candidate reviews and survey requests.
get_submitted_feedback
Brings back the scorecard feedback you personally submitted on a candidate or an interview, so you can reread what you wrote.
get_upcoming_interviews
Lists the interviews coming up on your calendar with the candidate's name, the job title, the time slot and the meeting link.
search_product_docs
Answers how-to questions about Ashby itself by searching the product documentation, and returns the answer with links to the matching articles.
What Claude changes (4)
4 toolsFour tools that write to Ashby. Only the note tool has a documented confirmation step.
add_note_to_candidate
Asks you firstWrites a note on a candidate's profile, or a reply under an existing note, as a draft rather than a saved entry.
change_application_stage
Approval: see the ruleShifts a candidate's application to another stage of that job's interview process, the same move you would drag on the pipeline board.
consider_candidate_for_job
Approval: see the rulePuts an existing candidate into consideration for a job by opening a new application at the very first stage of that job's process.
create_candidate
Approval: see the ruleAdds a brand-new person to Ashby with a name and contact details, ready to be attached to a job afterwards.
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 request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads open and closing writes, for instance. That setting applies to everyone and no one overrides it from their own account. And Claude works with your rights, nothing more: a candidate your Ashby role hides stays hidden in the chat.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. The answer, connector by connector, is not published anywhere: that is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the current state, check the Ashby sheet in the official directory, the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a candidate applies, an interview ends or an offer is signed.
This connector is documented only by its publisher: no Claude help article covers it, so everything here comes from Ashby's own page, which still labels the server a beta. The tool list is an observed floor, not a promise; Ashby says it keeps adding tools, write actions included. The partner badge in the directory is not a security audit either, and Anthropic states on every sheet that it does not pick the tools a publisher exposes nor guarantee how they behave. For another people-side connector, see the Claude bamboohr connector.
Need help connecting Ashby to Claude?
A person reads every message.
