The moment it happens

Get alerted to Drip spam complaints and bounces

The moment someone marks a Drip email as spam or it bounces, the subscriber shows up in Slack.

Runs: The moment it happens
Apps: Drip
AI: Not needed
Access: API token

Send this to your assistant

Create a ClickRuntime automation: whenever a Drip email gets a spam complaint or a bounce, post the subscriber's email to #email-ops 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

Email deliverability breaks quietly. A few spam complaints on one send, or a wave of bounces from an old imported list, can push your sending reputation down, and inbox providers start routing everything to spam. By the time open rates visibly fall, the reputation is already damaged and takes weeks to repair. Drip records each complaint and bounce, but nobody reads those logs until something has gone wrong.

The moment Drip reports a spam complaint or a bounce, a Slack message appears with the details, including who it was and which message triggered it. Because the alert is immediate, you can pause a campaign, remove a bad segment or check the content while the send is still going out.

Email marketers, store owners who send promotions and agencies who are accountable for client deliverability benefit most.

What you get out of it

Stop a bad send before it spreads
Seeing the first complaints while a campaign is still going out lets you pause it. Halting a send halfway protects your sender reputation and spares the remaining recipients from a message that is already annoying people.
Bounces from stale lists get fixed
A cluster of bounces points at old or mistyped addresses, usually from an imported list. Removing them quickly keeps your bounce rate low, which inbox providers watch closely when deciding whether to trust your future sends.
The responsible message is identified
Knowing which email drew the complaint tells you what to change. A subject line that felt clever in the draft might be exactly the one people mark as spam, and you only learn that from the complaint itself.
Complaints can be honored right away
Someone who marks you as spam clearly does not want your emails. Seeing it at once lets you make sure they are suppressed everywhere, and avoids a second send to a person who has already told you to stop.
Proof for clients and partners
Agencies can show a client exactly when a problem was spotted and what was done about it. A timestamped Slack history is far more convincing than a promise that someone was watching the metrics.

How it works

What happens, step by step

When a Drip subscriber marks your email as spam or an email to them bounces, Drip tells ClickRuntime straight away.
ClickRuntime ignores every other kind of Drip activity.
It posts a one-line message to #email-ops in Slack saying Spam complaint or Bounce, with the subscriber's email.

Before it runs live

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

What you get

RunsThe moment it happens

Get alerted to Drip spam complaints and bouncesjust nowSucceeded

Slack · #email-opsSpam complaint: jo@acme.com

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

spam_complaint_bounce_alert.pyexample

from clickruntime import on_event, notify

LABELS = {"subscriber.complained": "Spam complaint", "subscriber.bounced": "Bounce"}

@on_event
def handle(event):
    e = event.json or {}
    label = LABELS.get(e.get("event"))
    if not label:
        return {"posted": False}
    email = ((e.get("data") or {}).get("subscriber") or {}).get("email")
    notify.slack(f"{label}: {email}", channel="#email-ops")
    return {"posted": True}

FAQ

Common questions

What counts as a spam complaint in Drip?

A complaint is recorded when a recipient marks your email as spam in their mail client and the provider reports it back through a feedback loop. Not every provider does this, so Drip sees complaints from some inbox providers and not from others.

What is the difference between a hard and a soft bounce?

A hard bounce means the address is invalid or does not exist, while a soft bounce is a temporary failure such as a full mailbox. Hard bounces need the address removed, whereas soft ones often succeed on a later send.

Will I be alerted for every single bounce?

Each event is posted as it arrives, so a large send with many bounces can produce many messages. If that gets noisy, tell your AI assistant to post bounces in batches while still posting each complaint immediately.

What permissions does it need?

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