Resources · Claude connector

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

Overview

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.

Vocabulary

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.
Connect

Plug Workable into Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (30)

30 tools

Tools 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.

When it helps
you ask who reached the interview stage for the sales role this month.
Watch out
it works job by job, so someone parked in the talent pool without a job will not appear here.

Sourceworkable.readme.io · June 10, 2026 ↗

get_candidate

Pulls the full profile of one candidate, the details a recruiter checks before a call or a debrief.

When it helps
before a second interview you want a summary of the candidate's background and answers.
Watch out
it opens one person at a time; for a whole stage, the job-level candidate list is quicker.

Sourceworkable.readme.io · June 10, 2026 ↗

get_candidate_activities

Reads a candidate's activity log, including stage transitions and comments, so the story of an application comes back in order.

When it helps
a candidate says nobody followed up and you want the timeline of what happened.
Watch out
it replays past steps such as stage transitions and comments, without undoing any of them.

Sourceworkable.readme.io · June 10, 2026 ↗

get_candidate_activity

Opens a single entry of a candidate's activity log in detail, when one event needs checking on its own.

When it helps
you want the exact wording of the note left after the phone screen.
Watch out
Claude starts from the full log to pick out the right entry.

Sourceworkable.readme.io · June 10, 2026 ↗

get_disqualification_reasons

Lists the disqualification reasons configured in your account. Workable says they are required before a candidate can be disqualified.

When it helps
Claude is about to close a candidate and needs the reason your team normally uses.
Watch out
a reason missing from the list has to be configured in Workable; no tool on the sheet adds one.

Sourceworkable.readme.io · June 10, 2026 ↗

get_candidate_offer

Fetches the offer attached to a given candidate, so terms and status can be checked without searching.

When it helps
the hiring manager asks where the offer for the new designer stands.
Watch out
it only reads the offer; approving or rejecting it is the job of two separate tools.

Sourceworkable.readme.io · June 10, 2026 ↗

get_account_custom_attributes

Returns the custom attributes set at account level, the extra fields your team added to Workable.

When it helps
you want to know which custom fields exist before asking Claude to filter on one.
Watch out
these fields apply account-wide; one role's own extra fields come from a separate tool.

Sourceworkable.readme.io · June 10, 2026 ↗

get_departments

Lists every department in the account, the structure jobs and employees hang from.

When it helps
you want the department list before reorganising two small teams.
Watch out
the structure shown here is what the department tools further down act on, so check it first.

Sourceworkable.readme.io · June 10, 2026 ↗

get_employees

Lists employees with search, status filtering and ordering by department or division, the basic HR lookup.

When it helps
you ask how many people are active in the Lisbon division.
Watch out
for one person's full record, Claude then opens it with the single-employee tool.

Sourceworkable.readme.io · June 10, 2026 ↗

get_employee

Reads the full details of one employee's record in Workable's HR side.

When it helps
a manager needs the start date and role of a new team member before a review.
Watch out
HR records can be read here, but nothing on the sheet lets Claude alter them.

Sourceworkable.readme.io · June 10, 2026 ↗

get_events

Lists calls, interviews and meetings, filterable by job, candidate, member, type and date range.

When it helps
you want this week's interviews for the support role in one list.
Watch out
it lists what is already scheduled; booking a new interview is not among the sheet's tools.

Sourceworkable.readme.io · June 10, 2026 ↗

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.

When it helps
you want to confirm the panel for Thursday's final interview.
Watch out
for a whole week of interviews, the event list is the faster route.

Sourceworkable.readme.io · June 10, 2026 ↗

get_jobs

Lists jobs filtered by state, published, draft, archived or closed.

When it helps
you ask which roles are still published and which sit in draft.
Watch out
drafts and archived roles come back too, so name the state you want.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job

Opens one job in full from its shortcode, Workable's short identifier for a role.

When it helps
a hiring manager wants the exact requirements posted for the data role.
Watch out
Claude needs the shortcode, which the job list returns.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_stages

Returns the pipeline stages configured for one job, which Claude needs before advancing anyone.

When it helps
your engineering roles have an extra take-home stage and Claude must use the right one.
Watch out
stages can differ from one role to another, so Claude checks them per job.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_custom_attributes

Gets the custom attributes configured for a specific job, the extra fields that role carries.

When it helps
you want to see the budget code recorded on a role before approving spend.
Watch out
these are the role's own fields, distinct from the account-wide ones.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_members

Shows the team members assigned to a job, so you know who is on the hiring team.

When it helps
a candidate asks who they will meet and you want the list of interviewers.
Watch out
these are internal team members; agencies show up with the recruiters tool.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_recruiters

Lists the external recruiters assigned to a job, the agencies working the role alongside your team.

When it helps
you want to know which agency is sourcing for the finance role.
Watch out
agency recruiters are listed here, not your internal hiring team.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_application_form

Gets the questions of a job's application form, what candidates are asked when they apply.

When it helps
you want to check whether the form asks about work permits before screening.
Watch out
it shows the questions, not what each candidate answered.

Sourceworkable.readme.io · June 10, 2026 ↗

get_job_activities

Reads the activity log of one job, the trail of what happened on the role over time.

When it helps
you want to see when the role was last touched and by whom.
Watch out
it covers the role itself; one candidate's trail comes from the candidate log.

Sourceworkable.readme.io · June 10, 2026 ↗

get_members

Lists the members of the Workable account, filterable by role, status, email and job.

When it helps
you want to know who has admin rights before an audit.
Watch out
these are Workable users of the account, not candidates and not employees.

Sourceworkable.readme.io · June 10, 2026 ↗

get_offer

Reads the details of a specific offer from its ID.

When it helps
finance asks for the salary and start date in the offer sent last week.
Watch out
Claude needs the offer's ID; from a candidate, the candidate-offer tool gets there directly.

Sourceworkable.readme.io · June 10, 2026 ↗

get_requisitions

Lists requisitions, the headcount requests behind hiring, filterable by state, job and date.

When it helps
you want every requisition still pending approval this quarter.
Watch out
pending, approved and rejected requests all come back together, so name the state you want.

Sourceworkable.readme.io · June 10, 2026 ↗

get_requisition

Reads one requisition in detail from its code: title, owner, hiring manager, salary and department.

When it helps
before approving, you want to see the salary range on the requisition.
Watch out
Claude needs the requisition code, which the list returns.

Sourceworkable.readme.io · June 10, 2026 ↗

get_stages

Returns every recruitment pipeline stage available across the account.

When it helps
you are standardising pipelines and want the full list of stages in use.
Watch out
this is the account-wide list; one job's own stages come from the job-level tool.

Sourceworkable.readme.io · June 10, 2026 ↗

get_timeoff_balances

Gets time off balances for one employee or for all of them.

When it helps
an employee asks how many days they have left before booking a trip.
Watch out
balances are read only; nothing on the sheet books or approves leave.

Sourceworkable.readme.io · June 10, 2026 ↗

get_timeoff_requests

Retrieves time off requests within a date range, filterable by employee, category and state.

When it helps
you want to see who is off during the product launch week.
Watch out
approving or refusing a pending request is not among the tools on the Claude sheet.

Sourceworkable.readme.io · June 10, 2026 ↗

get_timeoff_categories

Lists the time off categories configured, such as vacation or sick leave.

When it helps
you want to check whether parental leave is set up as its own category.
Watch out
categories are configured in Workable; the sheet has no tool to add one.

Sourceworkable.readme.io · June 10, 2026 ↗

get_work_schedules

Returns the work schedules configured in the account, the schedules a new hire can be placed on.

When it helps
a new part-time hire starts Monday and you need the right schedule for them.
Watch out
schedules are only read here; nothing on the sheet assigns one to a person.

Sourceworkable.readme.io · June 10, 2026 ↗

What Claude changes (15)

15 tools

Tools 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 rule

Disqualifies a candidate with a reason, either rejected or withdrew, which closes their application on the job.

What Claude asks for
no source describes a confirmation of its own here, so the general approval rule applies.
When it helps
a candidate declined the process by email and their application should be closed as withdrawn.
Watch out
Workable requires one of your configured disqualification reasons.

Sourceworkable.readme.io · June 10, 2026 ↗

move_candidate

Approval: see the rule

Moves a candidate to a different pipeline stage and, at hire, can link a requisition.

What Claude asks for
a stage change has no documented confirmation of its own; the general approval rule is what applies.
When it helps
after a strong interview you want the candidate moved to the offer stage.

Sourceworkable.readme.io · June 10, 2026 ↗

add_comment

Approval: see the rule

Adds a comment to a candidate, with visibility controls deciding who in the team can read it.

What Claude asks for
comments carry no documented confirmation of their own; the general approval rule decides.
When it helps
you want your phone-screen notes on the profile, visible to the hiring team only.

Sourceworkable.readme.io · June 10, 2026 ↗

create_candidate

Approval: see the rule

Adds a new candidate and attaches them to a specific job, with resume, social profiles, education, experience and application answers.

What Claude asks for
nothing documents a dedicated check before a new candidate is added, so the general approval rule applies.
When it helps
a referral sent a CV by email and you want the person in the pipeline for the right role.

Sourceworkable.readme.io · June 10, 2026 ↗

create_talent_pool_candidate

Approval: see the rule

Adds a candidate to the talent pool without tying them to a job, for people worth keeping in view.

What Claude asks for
talent pool entries have no documented confirmation of their own; the general approval rule applies.
When it helps
a strong profile does not fit any open role today but should not be lost.

Sourceworkable.readme.io · June 10, 2026 ↗

add_review

Approval: see the rule

Adds a rating or review to a candidate, on a thumbs, stars or numeric scale.

What Claude asks for
recording a rating comes with no documented confirmation; the general approval rule governs it.
When it helps
you want your scorecard from the final interview recorded before the debrief.
Watch out
check the scale your team uses before Claude records a score.

Sourceworkable.readme.io · June 10, 2026 ↗

create_department

Approval: see the rule

Creates a new department, optionally nested under a parent department.

What Claude asks for
a new department has no confirmation described for it; the general approval rule decides.
When it helps
you are opening a customer success team and it needs its own department under Sales.

Sourceworkable.readme.io · June 10, 2026 ↗

update_department

Approval: see the rule

Updates a department's name or its parent, the two things Workable lists for this tool.

What Claude asks for
department edits carry no documented confirmation of their own; the general approval rule decides.
When it helps
Growth moves from under Marketing to under Sales after a reorganisation.

Sourceworkable.readme.io · June 10, 2026 ↗

delete_department

Approval: see the rule

Deletes a department by its ID and, with a force option, even when the department still holds data.

What Claude asks for
no source describes a confirmation before a department is deleted; the general approval rule applies.
When it helps
an empty test department created by mistake should disappear.
Watch out
the force option removes a department that still has data; ask what is attached first.

Sourceworkable.readme.io · June 10, 2026 ↗

merge_department

Approval: see the rule

Merges a source department into a target one and moves all associated data across.

What Claude asks for
no source documents a merge-specific confirmation; the general approval rule is the one to rely on.
When it helps
two regional sales teams become one and their departments should follow.
Watch out
after the merge, everything lives under the target; plan names before approving.

Sourceworkable.readme.io · June 10, 2026 ↗

approve_offer

Approval: see the rule

Approves an offer, the sign-off step before it goes to the candidate.

What Claude asks for
offer approvals have no documented confirmation of their own; the general approval rule applies.
When it helps
you are the approver and the terms were agreed on a call.

Sourceworkable.readme.io · June 10, 2026 ↗

reject_offer

Approval: see the rule

Rejects an offer, with an optional reason for the team.

What Claude asks for
turning an offer down carries no documented confirmation of its own; the general approval rule applies.
When it helps
the salary exceeds the approved band and the offer has to go back.

Sourceworkable.readme.io · June 10, 2026 ↗

create_requisition

Approval: see the rule

Files a new headcount requisition with job title, owner, hiring manager, salary and department.

What Claude asks for
requisitions carry no documented confirmation of their own; the general approval rule decides.
When it helps
a manager asks for a second support agent and you want the request filed properly.

Sourceworkable.readme.io · June 10, 2026 ↗

approve_requisition

Approval: see the rule

Approves a requisition from its code, the go-ahead to start hiring.

What Claude asks for
no source describes a check before a requisition is approved, so the general approval rule governs it.
When it helps
budget was confirmed this morning and the requisition can move on.

Sourceworkable.readme.io · June 10, 2026 ↗

reject_requisition

Approval: see the rule

Rejects a requisition, with an optional rejection reason you can dictate in the same sentence.

What Claude asks for
rejections carry no documented confirmation of their own; the general approval rule applies.
When it helps
a hiring freeze means the new role cannot open this quarter.

Sourceworkable.readme.io · June 10, 2026 ↗

Approvals

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.

Plans

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.

Limits

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

Need help connecting Workable to Claude?

A person reads every message.

FAQ

Claude Workable connector: frequent questions

01What can Claude do with the Workable connector?
Claude can work on your recruiting and read your HR data in Workable from a conversation. It lists jobs and their stages, forms, members and recruiters, reads candidates, their activity and offers, checks events, requisitions, departments and legal entities, and on the HR side reads employees, time off and work schedules. On the action side, it adds candidates, moves or disqualifies them, comments and rates, approves or rejects offers and requisitions, opens requisitions, and creates, renames, merges or deletes departments.
02Can Claude change candidates, offers or departments in Workable?
Yes, fifteen documented tools act on your account. Claude can add a candidate to a job or to the talent pool, move a candidate between stages, disqualify with a configured reason, comment and rate, approve or reject an offer, create, approve or reject a requisition, and create, update, merge or delete departments. On the HR side, the sheet only reads: no listed tool approves time off or edits an employee record, even though Workable's own page describes more.
03Does Claude ask before acting in Workable?
By default, yes: Claude asks for a confirmation before each action it carries out on an account for you. No source describes a confirmation specific to any Workable tool, so that default rule covers moving, disqualifying, approving, rejecting and restructuring. On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked, and they can also close every change for the whole organisation while keeping lookups open.
04Which plans is it available on?
No official source publishes availability by plan for each connector, and none of the directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner switching them on first on Team and Enterprise. Workable's sheet in the official directory is the only place showing the current state for your account, so check it there rather than trusting a summary.
05Does Claude see every candidate and employee in Workable?
Claude works through your own Workable sign-in, so it reaches what your Workable role can reach and nothing more. A job, candidate or employee record your role cannot open stays out of the conversation. Workable also supports several accounts from one connection, so Claude has to pick the right one. On top of this, an owner of a Team or Enterprise workspace can restrict what the connector may do for the whole organisation, and a member cannot lift that.
06Why can Claude read Workable time off but not approve it?
Because the Claude sheet only lists reading tools for time off: balances, requests and categories. None of the 45 tools on the sheet approves or rejects leave, so Claude cannot do it here. Workable's own page also describes time tracking and performance review tools that the sheet leaves out. For now, approvals of leave stay in Workable itself, while Claude can tell you who is off and how many days remain.
07Claude or an automation tool for Workable?
They do not answer the same need, so it depends on the task. Claude works inside a conversation: you ask, it reads, moves or approves, and nothing happens once you stop typing. It will not react on its own when a candidate applies or an offer is signed. For something that runs in the background on an event, that is the role of an automation tool. For pipeline reviews, debrief paperwork and approvals on demand, the connector is the right fit.