Collects as they arrive, acts daily

Get a daily list of Drip unsubscribes

Each evening I get one email listing everyone who unsubscribed from Drip that day.

Runs: Collects as they arrive, acts daily
Apps: Drip
AI: Not needed
Access: API token

Send this to your assistant

Create a ClickRuntime automation: collect everyone who unsubscribes in Drip during the day and email me the list at 6pm.

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

A store owner or lifecycle marketer sends a Drip campaign on Tuesday and sees the unsubscribe count creep up, but Drip shows it as a number, not a list of who left and when. Reading each unsubscribe as it happens would flood an inbox, while ignoring them means nobody learns that one particular email, perhaps the discount reminder, is driving people away. The signal that a campaign is hurting the list arrives too late to act on.

As each unsubscribe event arrives from Drip, the automation stores it. At 18:00 it emails you a single list of everyone who unsubscribed that day, then clears the store so tomorrow starts fresh. You get one calm email instead of dozens of interruptions.

Marketers running frequent campaigns, ecommerce owners and agencies managing client lists will value the daily pattern.

What you get out of it

Link unsubscribes to the email that caused them
A day with a spike of departures, read next to what you sent that morning, points straight at the campaign that annoyed people. You can pause or rewrite it before the next send makes the damage larger.
One email instead of a stream of alerts
Collecting the events and sending them together at 18:00 keeps your inbox calm. You read one list when you have time, not twenty single-line notices that interrupt the work you were doing.
Customers who left can be reviewed
Seeing the names lets you spot a high-value customer or a long-standing subscriber who left, and decide whether a personal note or a fix to their preferences would bring them back.
A clean list is easier to protect
Understanding who leaves and why helps you keep complaint rates and list quality healthy. A list that shrinks because of one bad template is a problem you can fix once you see it.
A daily record without exporting
Each email is a dated record of that day's unsubscribes. There is no CSV to download from Drip, which makes it simple to look back when a client asks what happened on a particular send.

How it works

What happens, step by step

Each time someone unsubscribes from all your Drip emails, Drip tells ClickRuntime and the email address is added to today's list.
Every evening, ClickRuntime checks whether anyone is on the list.
If so, you get one email with the count and every address, and the list is cleared for the next day.

Before it runs live

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

What you get

RunsCollects as they arrive, acts daily

Get a daily list of Drip unsubscribestoday, 9:00Succeeded

Email · Drip unsubscribesDrip unsubscribes today: 3 jo@acme.com old@northwind.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.

daily_unsubscribe_digest.pyexample

from clickruntime import on_event, on_trigger, notify, state

@on_event
def handle(event):
    e = event.json or {}
    if e.get("event") != "subscriber.unsubscribed_all":
        return {"stored": False}
    email = ((e.get("data") or {}).get("subscriber") or {}).get("email")
    pending = state.get("unsubscribes") or []
    pending.append(email)
    state.set("unsubscribes", pending)
    return {"stored": True}

@on_trigger
def run(event):
    pending = state.get("unsubscribes") or []
    if pending:
        notify.email_me(f"Drip unsubscribes today: {len(pending)}", "\n".join(pending))
        state.set("unsubscribes", [])
    return {"sent": len(pending)}

FAQ

Common questions

Why collect events and email once a day?

Drip sends an event for every unsubscribe as it happens, and emailing each one separately would be noisy. The automation stores them and sends one summary at 18:00, which gives you the whole picture of the day in a single message.

What if nobody unsubscribed today?

With nothing stored, there is nothing to list, so the email can be skipped or sent as a short note saying no one left. Most people prefer the quiet version, so the email only arrives when there is something to read.

How do I connect Drip to it?

In Drip, add a webhook for the unsubscribed event and paste the ClickRuntime webhook address. From then on Drip sends each unsubscribe to the automation, which stores it until the evening summary goes out at 18:00, so you never need to do anything per event.

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 each time it checks. Checks that find nothing new and stop right away aren't counted.

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