Automate Ashby

Follow your Ashby applications from submission to hire without logging in. Hiring managers see new applications and stage moves in Slack, and you get an email when an offer is created or a candidate is hired. Describe what you want to your AI assistant, check what it will do, and it keeps running.

Add to ChatGPT Add to Claude

Works inChatGPT Claude Claude Code Cursor Codex VS Code Gemini CLI Zed opencode Any MCP client

Try asking

Create a ClickRuntime automation: when an application is submitted in Ashby, post the candidate's name, the job and a link to #talent in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Ashby

Applications in Slack as they're submitted, stage moves for hiring managers, and a note when an offer goes out or someone is hired. These are ready-made starting points. Anything else you can describe works too.

The moment it happens

See new Ashby applications in Slack

Each submitted application shows up in Slack with the candidate and job straight away.

See how it works

The moment it happens

Get an email when an offer is made or someone is hired

You're told as soon as an offer is created in Ashby or a candidate is marked hired.

See how it works

The moment it happens

Tell hiring managers when candidates move stage

Hiring managers see in Slack when a candidate reaches the stages they care about.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Ashby, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Ashby automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Ashby should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every Friday, send me an Ashby summary of applications, interviews and offers this week per open job, and flag jobs with no new applicants.

When an Ashby application moves to offer, post it to our #recruiting Slack channel with the role and hiring manager.

When a candidate is hired in Ashby, create their onboarding page in Notion, add their start date to Google Calendar, and post a welcome note in Slack.

Beyond chat

Have Ashby work when you're not in the chat

Connecting Ashby to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Instant
See new Ashby applications in Slack
The moment it happens
Instant
Get an email when an offer is made or someone is hired
The moment it happens
Instant
Tell hiring managers when candidates move stage
The moment it happens

Setup

Connect Ashby

Ashby connects with an API key an admin creates in your Ashby account. Permissions are set per module, so the key only reaches the parts of Ashby you allow.

Ashby

Recruiting / ATS

Sign in to Ashby as an admin and open Admin, then Integrations, then API Keys.
Create a new key and set read permissions for the modules the automation needs, such as candidates, jobs and offers.
If the automation should include confidential jobs, enable confidential access on the key.
Copy the key, then in the ClickRuntime dashboard open Connections & secrets and save it as a secret for Ashby.

Good to know

Ashby limits that affect automations

Only Ashby admins can create API keys.
Confidential jobs are hidden unless the key has confidential access, so offers and hires on those jobs won't be reported without it.
If Ashby rejects the key, the run fails with an error: a missing key and a wrong or deactivated key show up as different errors, which helps when checking a connection.

FAQ

Questions about automating Ashby

What can ClickRuntime see in Ashby?

Only the modules your key has permission for. The automations here read applications, jobs and offers; they don't change anything in Ashby.

Will offers on confidential jobs be included?

Only if you enable confidential access when creating the key. Without it, those jobs and their offers are left out.

How fast are stage changes posted?

Straight away. Ashby sends an event when an application is updated, and the automation posts it if the new stage is one you asked about.

Can I limit alerts to certain stages?

Yes. Tell your assistant which stages matter, for example Onsite and Offer, and other moves are ignored.

Do I need AI for Ashby automations?

No. These alerts run without AI. If you add summaries later, they use the AI included in every ClickRuntime plan, so no AI key is needed.

Is this a Ashby connector for ChatGPT or Claude?

Not for chatting with Ashby data. A chat connector lets your assistant read and change Ashby while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Ashby event.

Keep exploring