The moment it happens

Hear about bounces and unsubscribes in lemlist

Bounced addresses and opt-outs are posted with the lead and campaign, so you can fix a bad list early.

Runs: The moment it happens
Apps: lemlist
AI: Not needed
Access: API key

Send this to your assistant

Create a ClickRuntime automation: when a lemlist email bounces or a lead unsubscribes, post the email address, campaign and event type to #deliverability 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

Cold email lives or dies on deliverability. In lemlist, a sudden cluster of bounces tells you that a list was bad or a domain has a problem, and a spike of unsubscribes tells you that the message or the targeting is off. Most senders only see these numbers in a campaign report after the sequence has finished, when hundreds more emails have already gone out to the same bad list.

Whenever lemlist records a bounce or an unsubscribe, ClickRuntime is notified and posts the lead and the campaign name to Slack. The person managing outreach sees each one as it happens and can pause a campaign before the damage spreads.

Agencies sending on behalf of several clients can use it to see which client's campaign is struggling. Each alert is a chance to protect the domain.

What you get out of it

Bad lists are stopped early
If the first fifteen emails in a sequence bounce, the list is probably poor. Seeing those bounces in Slack within minutes lets you pause the campaign instead of finishing a send that harms your domain.
Domain reputation is protected
Repeated bounces teach mailbox providers that your domain sends to dead addresses, and future emails land in spam. Quick action keeps the reputation you spent months warming up. Fixing the list early is far cheaper than recovering the domain.
Unsubscribes reveal mismatched targeting
Several people opting out of one campaign signals the wrong audience or an unwelcome message. Spotting it in real time lets you adjust before the rest of the list receives it.
Compliance is easier to show
Each unsubscribe is posted with a timestamp, so you can demonstrate that opt-outs were noticed promptly. That helps if a recipient later complains or an inbox provider asks questions. That clarity helps when several senders are active at once.
Client campaigns get individual attention
With the campaign name in each message, an agency can tell at a glance which client account is running into trouble and who needs to look into it. That keeps both sender and recipient on good terms.

How it works

What happens, step by step

When an email bounces or a lead unsubscribes in lemlist, lemlist tells ClickRuntime straight away.
ClickRuntime ignores every other kind of lemlist activity.
It posts a one-line message to #deliverability in Slack saying Bounced or Unsubscribed, with the lead's email and the campaign.

Before it runs live

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

What you get

RunsThe moment it happens

Hear about bounces and unsubscribes in lemlistjust nowSucceeded

Slack · #deliverabilityBounced: ops@acme.com in Q4 Ops outreach

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

bounce_unsubscribe_activity_alert.pyexample

from clickruntime import on_event, notify

EVENTS = {"emailsBounced": "Bounced", "emailsUnsubscribed": "Unsubscribed"}

@on_event
def handle(event):
    e = event.json or {}
    kind = EVENTS.get(e.get("type"))
    if not kind:
        return {"posted": False}
    notify.slack(f"{kind}: {e.get('leadEmail')} in {e.get('campaignName')}", channel="#deliverability")
    return {"posted": True, "type": kind}

FAQ

Common questions

Is a bounce the same as an unsubscribe in the alert?

They arrive as different event types and the message says which one it is. A bounce means the email could not be delivered, while an unsubscribe means the recipient chose to opt out. Both include the lead and the campaign.

Can I be alerted only after a certain number of bounces?

Yes. Instead of posting each one, the automation can count events and post when a campaign passes a threshold, such as five bounces in an hour. That is useful when you run big campaigns and single bounces are routine.

Does it handle hard and soft bounces differently?

It reports what lemlist sends. If lemlist labels the type of bounce, that detail can be included in the message so you can tell a permanently invalid address from a full mailbox. Hard bounces are the ones that should lead to list cleaning.

What permissions does it need?

API key. 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