The moment it happens

Post Mailchimp unsubscribes to Slack

When someone unsubscribes, your team sees who it was and which campaign it came from.

Runs: The moment it happens
Apps: Mailchimp
AI: Not needed
Access: read+write (to create webhook)

Send this to your assistant

Create a ClickRuntime automation: whenever someone unsubscribes from my Mailchimp audience, post their email and the campaign to #marketing 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

Every unsubscribe is a small piece of feedback that arrives with no one reading it. A customer who leaves after an order confirmation, a long-time reader who opts out after a price change and a key account that quietly drops off the list all look like one line in a total. Without a prompt, the account owner never gets the chance to ask what went wrong.

ClickRuntime registers a webhook on your Mailchimp audience. When someone unsubscribes, it parses the event for the person's email and the reason when one is recorded, and posts that to Slack straight away. A teammate can then reach out, fix a data problem or note the pattern.

It is most useful for B2B newsletters and customer lists where each contact matters, and for teams that want to find out why a campaign provoked unsubscribes.

What you get out of it

A chance to win someone back
A short personal note sent the same day, asking whether something was wrong, saves some relationships that a silent opt-out would have ended. That works far better than finding out a quarter later.
Account owners hear about key contacts leaving
When an important customer unsubscribes, the person managing that account sees it in Slack. They can check whether the cause is too many emails or a real service problem. A quick call can also catch a billing or service problem early.
Patterns show up after a single campaign
Five alerts in ten minutes after a send point to a specific email, not general fatigue. You can pause the next one in the series before more readers leave. Reacting early also protects your sender reputation across the rest of the list.
Reasons are captured where the team reads them
If Mailchimp recorded why the person left, that reason is in the message. Over time you collect honest feedback without running a survey. Those comments tell you which topics, frequency and offers readers actually dislike, in their own words, without anyone having to export and read through a separate report.
Accidental opt-outs can be reversed
Some people click unsubscribe by mistake and would happily stay. Seeing the event quickly lets you send a link to resubscribe while they still remember the email. A one-line apology and a link often brings them back at no cost.

How it works

What happens, step by step

When someone unsubscribes from your Mailchimp audience, Mailchimp tells ClickRuntime straight away.
It picks out the email address, the campaign and the reason.
A message goes to your #marketing Slack channel with those details.

Before it runs live

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

What you get

RunsThe moment it happens

Post Mailchimp unsubscribes to Slackjust nowSucceeded

Slack · #marketingUnsubscribed: ops@acme.example (campaign 4f2a91c0de, reason: manual)

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

unsubscribe_alert.pyexample

from urllib.parse import parse_qs
from clickruntime import on_event, notify

@on_event
def handle(event):
    form = {k: v[0] for k, v in parse_qs(event.body or "").items()}
    if form.get("type") != "unsubscribe":
        return {"posted": False}
    notify.slack(f"Unsubscribed: {form.get('data[email]')} (campaign {form.get('data[campaign_id]') or 'none'}, "
                 f"reason: {form.get('data[reason]', 'manual')})", channel="#marketing")
    return {"posted": True}

FAQ

Common questions

Does Mailchimp always tell me why someone unsubscribed?

No. A reason is only available when Mailchimp collects one, for example through a survey on the unsubscribe page. When no reason was given, the Slack message shows the email address and the audience without one.

Will it flag people who were unsubscribed by me or by a cleanup?

The webhook can report different sources of unsubscribe events, such as the subscriber clicking a link or an admin action, depending on how it is set up. Choose which sources should trigger an alert so cleanups do not flood the channel.

Can I send the alert only for certain segments, like customers?

Yes. The message can be filtered by tag or merge field so only unsubscribes from, say, paying customers reach Slack, while the rest are ignored. Ask your AI assistant to add the condition and approve it.

What permissions does it need?

read+write (to create webhook). 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