The moment it happens
Post every new Close lead to Slack
Each lead created in Close shows up in Slack with the company and main contact.
- Runs
- The moment it happens
- Apps
- Close
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: when a lead is created in Close, post the company name, contact name and email to #new-leads in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Speed to lead decides a lot of sales outcomes. When a Close lead is created by a web form, an import or a rep, the sooner somebody contacts them the more likely they are to answer. Yet in many teams the new lead sits in a Smart View until someone remembers to refresh it, and an inbound request can wait hours.
As soon as Close reports a new lead, this fetches the lead's details and posts them to Slack. The post gives the team the company, the contact and the source in one message, so the right person can claim it straight from the channel.
Inbound-heavy teams, such as those with a demo request form, use it to make sure no new lead goes unseen. The post is created from the lead exactly as it exists in Close, so the team sees the real record and does not have to wait for someone to type up the details.
What you get out of it
Respond to inbound leads within minutes
Prospects who fill in a form expect a fast reply. A Slack message the moment the lead exists lets the first available rep respond, while the prospect is still at their desk.
Avoid leads falling between reps
In a shared channel, someone replies with a claim, and everyone sees who has it. This avoids two reps calling the same lead or, worse, nobody calling at all. Claiming a lead with a quick reply in the thread means two reps do not call the same person and nobody leaves them waiting.
See lead quality at a glance
The post shows the company and source, so you can recognise a strong lead immediately. A high-value account gets escalated, and a clearly poor fit can be skipped. A strong lead from a known company gets escalated to the right rep in minutes, and a poor fit can be dismissed quickly.
Notice problems with lead capture
If the channel goes quiet when you expect traffic, a form or integration may be broken. You find out within the day instead of discovering a week of missing leads. Silence after a campaign or a website change is an early sign that a form or integration is broken and needs urgent attention.
Give marketing instant feedback
Marketing sees leads from a campaign appear in real time. That makes it easy to connect a launch to its results without waiting for a monthly attribution report. Marketing sees results from a campaign as the leads arrive, which makes it easier to talk about quality with sales.
How it works
What happens, step by step
Each time a lead is created in Close, Close tells ClickRuntime straight away.
The automation looks up the lead to get the company name and main contact.
A message goes to #new-leads with the company and the contact's name and email.
Before it runs live
- Connect Close
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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
from clickruntime import on_event, credentials, http, notify
@on_event
def handle(event):
ev = (event.json or {}).get("event", {})
if ev.get("object_type") != "lead" or ev.get("action") != "created":
return {"skipped": f"{ev.get('object_type')} {ev.get('action')}"}
lead = http.get(f"https://api.close.com/api/v1/lead/{ev['object_id']}/",
auth=(credentials.secret("CLOSE_API_KEY"), "")).json()
contact = (lead.get("contacts") or [{}])[0]
email = (contact.get("emails") or [{}])[0].get("email", "no email")
notify.slack(f"New lead: *{lead['display_name']}*\nContact: {contact.get('name', '-')} ({email})\n{lead['html_url']}",
channel="#new-leads")
return {"lead": lead["id"]}FAQ
Common questions
Does it post leads created by imports too?
What details does the Slack message include?
How quickly does the post appear?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Hear when a Close lead becomes Qualified
I'm told the moment a lead moves into Qualified.
See how it worksShare a summary of each call logged in Close
Every logged call appears in Slack with the lead, duration and a short summary of the notes.
See how it worksPost new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
See how it worksKeep exploring
Set up “Post every new Close lead to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.