- Home
- Resources
- Integrations
- Workable
Claude Workable connectorWhat Claude can do in your Workable account.
The Claude Workable connector exposes 45 tools. 30 read your jobs, candidates, offers, employees and time off, and 15 act on candidates, offers, requisitions and departments. Here: what Claude does, what it asks first, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Workable
Recruiting eats time in small clicks: opening a profile, checking a stage, chasing an approval. With the connector, you ask Claude in plain words and it reads the jobs, candidates, events and requisitions for you, then moves candidates, records reviews or approves requests when you tell it to, from the same conversation.
A pipeline check before the weekly hiring meeting. get_jobs lists the published roles, get_candidates shows who sits at which stage, and get_events adds this week's interviews, so Claude hands you a one-page status.
After an interview, the paperwork done. add_review records your rating, add_comment posts your notes with the right visibility, and move_candidate moves the person to the next stage.
Headcount without the back-and-forth. create_requisition files a new request with salary and department, and approve_requisition or reject_requisition closes the loop once budget is known.
Now what it does not do. On the HR side, the sheet only reads: employees, time off balances and requests, schedules. Workable's own page describes many more tools, such as updating a candidate, inviting members or time tracking, that the Claude sheet does not list. And nothing runs by itself: no tool fires when a candidate applies. For that kind of background job, see the Workable n8n integration.
The vocabulary in one minute
Five words you will meet while plugging Workable in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it changes your account. Not the same thing as approving an offer or a requisition in Workable.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Workable.
Plug Workable into Claude in three steps
- 01
Find Workable in Claude
In Claude's settings, open Customize, then Connectors, and look for Workable in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, then each member connects on their own.
- 02
Start the connection
Click Connect on its row and sign in to Workable in the window Workable opens itself. If the link breaks later, use Disconnect and plug it back in from the same row.
- 03
Read the authorization screen
Read the screen before you accept. It belongs to Workable, not to Claude, and it sets what the access covers. You can withdraw that access later from your Workable account as well.
The 45 Claude Workable connector tools, grouped by what they do
Workable gives Claude 45 tools: 30 that read your account, 15 that change something in it.
Two groups: what Claude reads, and what it changes. The names stay exactly as Claude shows them.
- 30 read
- 15 write
Tools index
- get_candidates
- get_candidate
- get_candidate_activities
- get_candidate_activity
- get_disqualification_reasons
- get_candidate_offer
- get_account_custom_attributes
- get_departments
- get_employees
- get_employee
- get_events
- get_event
- get_jobs
- get_job
- get_job_stages
- get_job_custom_attributes
- get_job_members
- get_job_recruiters
- get_job_application_form
- get_job_activities
- get_legal_entities
- get_members
- get_offer
- get_requisitions
- get_requisition
- get_stages
- get_timeoff_balances
- get_timeoff_requests
- get_timeoff_categories
- get_work_schedules
What Claude reads (30)
30 toolsTools that look at jobs, candidates, offers, requisitions, members, employees and time off without touching them.
get_candidates
Lists the candidates of one job, filterable by pipeline stage, email and date, which is the starting point of most hiring questions.
get_candidate
Pulls the full profile of one candidate, the details a recruiter checks before a call or a debrief.
get_candidate_activities
Reads a candidate's activity log, including stage transitions and comments, so the story of an application comes back in order.
get_candidate_activity
Opens a single entry of a candidate's activity log in detail, when one event needs checking on its own.
get_disqualification_reasons
Lists the disqualification reasons configured in your account. Workable says they are required before a candidate can be disqualified.
get_candidate_offer
Fetches the offer attached to a given candidate, so terms and status can be checked without searching.
get_account_custom_attributes
Returns the custom attributes set at account level, the extra fields your team added to Workable.
get_departments
Lists every department in the account, the structure jobs and employees hang from.
get_employees
Lists employees with search, status filtering and ordering by department or division, the basic HR lookup.
get_employee
Reads the full details of one employee's record in Workable's HR side.
get_events
Lists calls, interviews and meetings, filterable by job, candidate, member, type and date range.
get_event
Opens the full details of a single event, such as a call, an interview or a meeting, the three event types Workable names.
get_jobs
Lists jobs filtered by state, published, draft, archived or closed.
get_job
Opens one job in full from its shortcode, Workable's short identifier for a role.
get_job_stages
Returns the pipeline stages configured for one job, which Claude needs before advancing anyone.
get_job_custom_attributes
Gets the custom attributes configured for a specific job, the extra fields that role carries.
get_job_members
Shows the team members assigned to a job, so you know who is on the hiring team.
get_job_recruiters
Lists the external recruiters assigned to a job, the agencies working the role alongside your team.
get_job_application_form
Gets the questions of a job's application form, what candidates are asked when they apply.
get_job_activities
Reads the activity log of one job, the trail of what happened on the role over time.
get_legal_entities
Returns the legal entities configured in the account, useful when a company hires through several companies or countries.
get_members
Lists the members of the Workable account, filterable by role, status, email and job.
get_offer
Reads the details of a specific offer from its ID.
get_requisitions
Lists requisitions, the headcount requests behind hiring, filterable by state, job and date.
get_requisition
Reads one requisition in detail from its code: title, owner, hiring manager, salary and department.
get_stages
Returns every recruitment pipeline stage available across the account.
get_timeoff_balances
Gets time off balances for one employee or for all of them.
get_timeoff_requests
Retrieves time off requests within a date range, filterable by employee, category and state.
get_timeoff_categories
Lists the time off categories configured, such as vacation or sick leave.
get_work_schedules
Returns the work schedules configured in the account, the schedules a new hire can be placed on.
What Claude changes (15)
15 toolsTools that add, move, rate, disqualify, approve, reject or restructure. No source gives any of them its own confirmation rule: the general rule below applies.
disqualify_candidate
Approval: see the ruleDisqualifies a candidate with a reason, either rejected or withdrew, which closes their application on the job.
move_candidate
Approval: see the ruleMoves a candidate to a different pipeline stage and, at hire, can link a requisition.
add_comment
Approval: see the ruleAdds a comment to a candidate, with visibility controls deciding who in the team can read it.
create_candidate
Approval: see the ruleAdds a new candidate and attaches them to a specific job, with resume, social profiles, education, experience and application answers.
create_talent_pool_candidate
Approval: see the ruleAdds a candidate to the talent pool without tying them to a job, for people worth keeping in view.
add_review
Approval: see the ruleAdds a rating or review to a candidate, on a thumbs, stars or numeric scale.
create_department
Approval: see the ruleCreates a new department, optionally nested under a parent department.
update_department
Approval: see the ruleUpdates a department's name or its parent, the two things Workable lists for this tool.
delete_department
Approval: see the ruleDeletes a department by its ID and, with a force option, even when the department still holds data.
merge_department
Approval: see the ruleMerges a source department into a target one and moves all associated data across.
approve_offer
Approval: see the ruleApproves an offer, the sign-off step before it goes to the candidate.
reject_offer
Approval: see the ruleRejects an offer, with an optional reason for the team.
create_requisition
Approval: see the ruleFiles a new headcount requisition with job title, owner, hiring manager, salary and department.
approve_requisition
Approval: see the ruleApproves a requisition from its code, the go-ahead to start hiring.
reject_requisition
Approval: see the ruleRejects a requisition, with an optional rejection reason you can dictate in the same sentence.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out 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 limit what a connector may do for the whole organisation, keeping lookups open and closing every change, for example. That setting applies to everyone and nobody overrides it from their own account. And Claude works with your Workable rights and nothing more: a job or employee record you cannot open stays closed to it too.
Which plans it is available on
None of the 819 directory sheets shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organisation before members can connect individually. For the current state, check Workable's sheet in the official directory. One more point: this connector is documented only by Workable itself, with no Claude help page of its own.
Where the Claude Workable connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a candidate applies, an offer is signed or a leave request arrives.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in only what comes from a publisher you trust. Workable's page was last updated in June, earlier than the directory sheet, so the two can drift. Other connectors are gathered on the Integrations hub.
Need help connecting Workable to Claude?
A person reads every message.