Every 10 minutes
Know when a cadence email gets a reply or bounces
I get a Slack message when a prospect replies to a cadence email or one of our emails bounces.
- Runs
- Every 10 minutes
- Apps
- Salesloft
- AI
- Not needed
- Access
- read emails
Send this to your assistant
Create a ClickRuntime automation: every 10 minutes, check Salesloft cadence emails and send me a Slack DM for each reply or bounce, with the person, subject and cadence name.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An SDR running 150 prospects through a Salesloft cadence is judged on pipeline, but the two events that matter most are easy to miss: a prospect replying, and an email bouncing. A reply sits in the inbox while the SDR is on calls, and the prospect who wrote 'send me pricing' cools off by the afternoon. A bounce is worse in a quiet way, because the cadence keeps stepping toward an address that does not exist and the contact never gets reached at all.
Every ten minutes the automation lists Salesloft activities and emails updated since its last run, keeps only the ones marked as replied or bounced, and posts each to a chat channel. You see who answered or whose address failed, along with the cadence they were in. It does not need anyone to open Salesloft to find out. It is useful for SDR managers and for reps who live in chat during the day.
What you get out of it
Replies get answered while they are warm
A prospect who replies is interested right now. Hearing about it within ten minutes lets the rep respond before the person moves to the next email, which is when most buying conversations are won or lost.
Bad addresses fixed before the cadence ends
A bounce notice tells the rep to look for a corrected email or another contact at the company. Without it the whole twelve-step cadence runs against a dead address and the account is written off by mistake.
Managers see response patterns
A channel full of reply alerts, or a suspicious number of bounces, shows quickly whether a new template or list is working. A batch of bounces from one import points to a list quality problem worth fixing today.
Fewer missed positive replies
Reply notifications in Salesloft's own inbox are easy to overlook among other mail. A message in a team channel is visible to several people, so a rep's absence does not leave a hot reply unanswered.
Protects sender reputation
Repeated sends to addresses that bounce hurt deliverability for the whole team. Spotting bounces early gives you the chance to remove those contacts before mailbox providers start treating the domain as careless.
How it works
What happens, step by step
Every 10 minutes, ClickRuntime checks Salesloft for cadence emails that changed since its last check.
It keeps only the emails that got a reply or bounced, and remembers when it last looked so nothing is posted twice.
For each one it looks up the cadence name.
It posts a message to #sales-replies in Slack saying whether it was a reply or a bounce, with the recipient, subject line and cadence.
Before it runs live
- Connect Salesloft
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 Salesloft steps into one automation
Under the hood
The code that runs this automation
from datetime import datetime, timezone
from clickruntime import on_trigger, state_initializer, credentials, notify, http, state, report_fetched
API = "https://api.salesloft.com/v2"
@state_initializer
def init():
state.set("since", datetime.now(timezone.utc).isoformat())
@on_trigger
def run(event):
headers = {"Authorization": f"Bearer {credentials.connection('salesloft', 'work')}"}
since = state.get("since")
now = datetime.now(timezone.utc).isoformat()
emails = http.get(f"{API}/activities/emails", headers=headers,
params={"updated_at[gt]": since, "per_page": 100}).json()["data"]
hits = [e for e in emails if e.get("status") == "bounced" or (e.get("counts") or {}).get("replies")]
report_fetched(len(hits))
if not hits:
return {"alerts": 0}
for e in hits:
cadence_id = (e.get("cadence") or {}).get("id")
cadence = http.get(f"{API}/cadences/{cadence_id}", headers=headers).json()["data"]["name"] if cadence_id else "no cadence"
kind = "Bounce" if e.get("status") == "bounced" else "Reply"
notify.slack(f"{kind}: {e['recipient_email_address']} on \"{e['subject']}\" ({cadence})",
channel="#sales-replies")
state.set("since", now)
return {"alerts": len(hits)}FAQ
Common questions
What exactly counts as a reply in this alert?
Does it alert on soft bounces and hard bounces equally?
Can I see alerts only for one cadence or one rep?
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
Get new Salesloft leads in Slack
New people added to Salesloft show up in Slack within 10 minutes, with their title and account.
See how it worksPost booked Salesloft meetings to Slack
When a meeting is booked in Salesloft, #wins shows who it's with, when it is and which rep booked it.
See how it worksSee new job listings as they're posted
Jobs that match your keywords show up in a Slack channel, each one only once.
See how it worksKeep exploring
Set up “Know when a cadence email gets a reply or bounces” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
