Skip to content

Start building

Integration · HR and recruiting

AI agents for Workable

List jobs and their candidates, read a candidate, add candidates to a job and comment on candidates in a Workable account.

Actions
6
Read
4
Write
2

Actions

What your agents can do in Workable

6 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 4

Look things up. Nothing changes.

  • List jobs

    Lists the account's jobs, oldest first, optionally only draft, published, archived or closed ones, or those updated since a time.

  • List candidates for a job

    Lists the candidates on a job, by the job's shortcode, optionally only those in a pipeline stage (its slug, like applied or interview), with an email address, or updated since a time.

  • Get a candidate

    Reads one candidate by their ID: name, headline, job and stage, disqualification, contact details, summary, cover letter, education, experience, skills, answers to the job's questions.

  • List members

    Lists the account's hiring team members, optionally by email, exact full name, recruiting role (admin, simple, reviewer) or status, or only the collaborators on a job.

Write 2

Create, change or send.

  • Add a candidate to a job

    Adds a candidate to a job, by the job's shortcode, with a first and last name and an email, and optionally a headline, summary, phone, address, cover letter, skills, tags.

  • Comment on a candidate

    Adds a comment to a candidate's timeline, posted as the connection's "comment as" member or another member ID (find IDs with List members).

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Workable account.

What you enter

  • API access token

Settings

  • Account subdomain

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Workable data

    Ask a question in plain words. The agent can list jobs, list candidates for a job or get a candidate in Workable, then answers with what it found.

  • 02

    Let an agent update Workable

    Have the agent add a candidate to a job or comment on a candidate in Workable as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Workable and Slack: it can list jobs in Workable and post a summary to a Slack channel in the same run.

FAQ

Workable and MyDeepAgents

Can MyDeepAgents connect to Workable?

Yes. The Workable connector has 6 actions: 4 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Workable?

Paste an API key from your Workable account. You'll need: API access token. The connection also asks for: Account subdomain. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Workable without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use Workable in workflows as well as agents?

Yes. Every Workable action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Workable to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.