The moment it happens

See new Ashby applications in Slack

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

Runs: The moment it happens
Apps: Ashby
AI: Not needed
Access: candidates read, jobs read

Send this to your assistant

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.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A recruiter at a growing startup opens roles in Ashby, and good candidates apply at all hours. The hiring manager only learns about them when the recruiter forwards a link or when someone checks the pipeline during the weekly sync. By then, a strong applicant who also applied elsewhere has been interviewed twice, and a role that needed one more decent candidate has sat for days without anyone reading new applications.

When a candidate applies for a job in Ashby, Ashby sends ClickRuntime a signal, and ClickRuntime formats the candidate's name, the role they applied for and a link to their profile, and posts a message in Slack. Hiring managers and recruiters see each new applicant within moments of the submission.

It is most valuable for roles that are hard to fill, where speed to first reply affects who accepts an offer. That also makes it easy to share applicant flow with an executive sponsor.

What you get out of it

Strong candidates get a faster first reply
Candidates compare responses across companies. Acknowledging a good applicant within hours, not days, makes your company the one that seemed interested, which helps close offers. Speed of response often decides who accepts.
Hiring managers stay close to the funnel
Seeing each application as it arrives keeps managers aware of the quality coming in. They can tell the recruiter to adjust a job post early if the wrong people are applying.
Recruiters avoid forwarding links
Posting to a shared channel removes the repetitive task of pinging managers about each candidate. Recruiting time goes to screening and conversations. Recruiters get time back for screening. Fewer manual messages are needed.
Referrals and internal applicants stand out
A familiar name in the channel, such as a referral, prompts someone to flag that candidate for fast review. Friendly signals are less likely to be missed. Referred applicants get quick attention.
Applicant volume is visible without reports
A glance at the channel shows whether a role is getting five applications a day or none. That prompts sourcing work sooner than a monthly pipeline report would. Sourcing can start earlier.

How it works

What happens, step by step

When an application is submitted in Ashby, Ashby tells ClickRuntime straight away.
ClickRuntime picks out the candidate's name and the job.
A message with both and a link to the candidate is posted to your Slack channel.

Before it runs live

Connect Ashby
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

See new Ashby applications in Slackjust nowSucceeded

Slack · #talentNew application: Kai Turner for Staff Platform Engineer https://app.ashbyhq.com/candidates/3f9e…

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. 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.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Ashby steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

new_application_alert_ashby.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    payload = event.json or {}
    if payload.get("action") != "applicationSubmit":
        return {"posted": False}
    app = payload["data"]["application"]
    notify.slack(f"New application: {app['candidate']['name']} for {app['job']['title']}\n"
                 f"https://app.ashbyhq.com/candidates/{app['candidate']['id']}", channel="#talent")
    return {"posted": True}

FAQ

Common questions

Does the message include the candidate's resume?

No. It shows basic details such as the name and the job, plus a link to the candidate in Ashby, where access controls still apply. Keeping the resume out of Slack avoids spreading personal data across channels.

Can I post only for certain jobs?

Yes. The incoming event includes the job title and ID, so ClickRuntime can post only for specific roles or send different jobs to different channels, such as engineering applicants to one channel and sales applicants to another. Other jobs are simply ignored.

How quickly does the message arrive?

Ashby sends the webhook when the candidate submits the form, and ClickRuntime posts as soon as it is received, usually within a few seconds. There is no polling interval, so the delay is mostly the time Ashby takes to send the event.

What permissions does it need?

candidates read, jobs read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens