The moment it happens

Hear when a Close lead becomes Qualified

I'm told the moment a lead moves into Qualified.

Runs: The moment it happens
Apps: Close
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: when a Close lead's status changes to Qualified, post the lead name, owner and a link to #sales 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

In a Close pipeline, the status change from Potential to Qualified is the handoff that matters. An SDR spends a week warming a lead up, marks it Qualified, and then the account executive does not see it until their next pipeline review. The prospect has gone cold again by the time anyone calls.

When Close sends a lead status change event, this checks whether the new status is the one you care about, such as Qualified, and posts the lead to Slack only in that case. All other status changes are ignored, so the channel carries one clear message type.

Sales teams with a split between development and closing roles get the most out of it, because it makes the handoff visible to the people who must act. The check is made on the event itself, so a lead that merely changes owner or has its details edited will not trigger a message in the channel and distract the team.

What you get out of it

Speed up the handoff to closers
A message in Slack the moment a lead becomes Qualified means the account executive can call that day. Every day of delay lowers the chance the prospect still remembers the conversation. Prospects respond best soon after qualification, and a fast, informed call can turn a lukewarm lead into a booked demo.
Stop leads sitting unnoticed
Without an alert, a qualified lead can wait in a list view that nobody has open. The channel post creates a shared moment where someone claims the lead or asks who should.
Give SDRs credit and visibility
Seeing qualified leads appear in the team channel makes SDR output visible. Managers recognise good work in real time instead of at the end-of-month report. Managers can recognize good qualification work as it happens, which supports SDRs far better than a monthly spreadsheet of numbers.
Cut the noise of other statuses
Only the status you choose triggers a post. People are not buried under every change from Contacted to Potential, so the alert is read and acted on. Because only the one status triggers a post, people read the channel closely, and the handoff message does not drown among others.
Measure response time honestly
With a Slack timestamp on each qualified lead, you can compare it with the first call logged in Close. That shows how quickly your team really responds. Comparing the Slack time with the first logged call gives you a straight measure of how fast the handoff is really working.

How it works

What happens, step by step

Each time a lead's status changes in Close, Close tells ClickRuntime straight away.
It checks whether the new status is Qualified and ignores every other change.
A message goes to #sales with the lead name, who moved it and a link to the lead.

Before it runs live

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

What you get

RunsThe moment it happens

Hear when a Close lead becomes Qualifiedjust nowSucceeded

Slack · #sales:white_check_mark: *Acme Logistics* is now Qualified (by Morgan) https://app.close.com/lead/lead_8xk…/

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

lead_entered_a_status_alert.pyexample

from clickruntime import on_event, credentials, http, notify

STATUS = "Qualified"

@on_event
def handle(event):
    ev = (event.json or {}).get("event", {})
    if ev.get("object_type") != "lead" or "status_id" not in ev.get("changed_fields", []):
        return {"skipped": "not a status change"}
    if ev.get("data", {}).get("status_label") != STATUS:
        return {"skipped": ev.get("data", {}).get("status_label")}
    auth = (credentials.secret("CLOSE_API_KEY"), "")
    lead = http.get(f"https://api.close.com/api/v1/lead/{ev['object_id']}/", auth=auth).json()
    owner = ev.get("user_id")
    owner_name = http.get(f"https://api.close.com/api/v1/user/{owner}/", auth=auth).json().get("display_name") if owner else "-"
    notify.slack(f":white_check_mark: *{lead['display_name']}* is now {STATUS} (by {owner_name})\n{lead['html_url']}",
                 channel="#sales")
    return {"lead": lead["id"]}

FAQ

Common questions

Can I alert on a different status?

Yes. Qualified is only an example. Tell your AI assistant which status label matters to you, such as Demo Scheduled or Customer, and the revised filter is shown for your approval before it takes over.

Does it work with custom lead statuses?

Close lets you define your own lead statuses, and the check compares against the status label you name. As long as the status exists in your Close account, it can be used as the trigger. Custom statuses work, because the comparison uses the label that you name, and it has to match a status that exists in your account.

Will it post if someone changes a status by mistake?

Yes. It reacts to every change into the chosen status. If a lead is accidentally set to Qualified and then reverted, the message still appears, so the channel may occasionally show a correction. The message appears whenever a lead moves into the status, so a lead set to Qualified by mistake and then changed back still appears.

What permissions does it need?

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