Skip to content
Custom Connectors

Full read-write Claude connector for Workable

Let Claude advance candidates and add evaluations in Workable

Stop clicking through profiles one at a time to keep the pipeline current. Claude moves candidates to the next stage, leaves scorecards and comments, and tags shortlists where the hiring data already lives, with gated actions waiting for your approval.

Workable is a recruiting and applicant tracking system teams use to post jobs, manage candidates, and run hiring pipelines. People want Claude to do more than read candidate lists: to move applicants through stages, leave evaluations, and keep pipelines organized inside Workable.

What is a Workable MCP server?

A Workable MCP server is a small hosted service that exposes Workable's data and actions to Claude over the Model Context Protocol, so Claude can people, time, and pay inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Workable's current connector do today?

Workable now publishes an official MCP connector for Claude, so out of the box Claude can read and act through a standard set of hiring tools. A custom Workable connector goes further, shaping the exact stage moves, scorecards, custom fields, and approval steps your process needs, with human-in-the-loop controls, so Claude works the way your pipeline actually runs.

What does full read-write Workable access unlock?

Full read-write Workable access lets Claude move a candidate to the next stage, add evaluation scorecards and comments, tag candidates, disqualify with a reason, and copy or relocate a candidate to another job, all once you approve. The pipeline hygiene that used to mean clicking through each profile happens where the hiring data already lives.

  • Move a candidate to the next stage in a job pipeline
  • Add an evaluation comment or scorecard to a candidate profile
  • Tag or label candidates so a shortlist is easy to filter
  • Disqualify a candidate with a documented reason after you approve
  • Create a candidate record from a sourced profile
  • Copy or relocate a candidate to another job pipeline

Can Claude move candidates through stages in Workable?

Moving candidates through stages is a core write action. With a custom Workable connector, Claude advances an applicant to the next step in a job pipeline through the API, keeping the existing history intact. It reads the pipeline first, then makes the change only on the candidates you point it at.

Can Claude add evaluations and tag candidates in Workable?

Yes. Claude can add an evaluation comment or scorecard to a candidate profile and tag or label candidates so a shortlist is easy to filter. These writes go through Workable's API under your scoped token, so Claude builds the hiring record in place instead of you clicking through each profile by hand.

Will Claude disqualify a candidate in Workable without approval?

Disqualifying a candidate in Workable is a separate, gated write that records a reason. Claude can prepare the change and surface the candidates it would affect, but the action runs only after you approve it. You decide which write actions are automatic and which always require a confirmation step.

How a Workable connector works

We build a small MCP server that connects to Workable through its API with a scoped access token, requesting only the permissions the work needs. Read tools (search candidates, read a pipeline) and write tools (advance, comment, tag, disqualify) are separated, and destructive or outbound actions like disqualify require your confirmation. Claude never has more access than the Workable account it runs under, and we can add IP allowlisting where your plan supports it.

Frequently asked questions

Can Claude move candidates through stages in Workable, not just read them?
Yes. The official connector covers standard stage moves, and a custom Workable connector goes further, exposing a stage-advance tool tuned to your pipeline so Claude moves a candidate through Workable's API while keeping history intact. A purpose-built connector adds the scoped permissions, custom fields, and gating the standard tool set leaves out.
Will Claude disqualify or reject a candidate without my approval?
No. Disqualifying is a separate, gated write action that records a reason. Claude can prepare the change and surface the candidates it would affect, but the action only runs after you approve it. You decide which write actions are automatic and which always require a confirmation step.
Does the connector get more access than my Workable account has?
No. The connector authenticates with a scoped Workable access token and inherits the permissions tied to it, so it cannot reach jobs or candidates your own role cannot. It never grants Claude more access than you already have, and write scopes can be narrowed further or left out entirely.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.