The moment it happens

Post list sign-ups and unsubscribes to Slack

Your team sees each person who joins or leaves your list in Slack as it happens.

Runs: The moment it happens
Apps: Campaign Monitor
AI: Not needed
Access: API key (full account)

Send this to your assistant

Create a ClickRuntime automation: whenever someone subscribes to or unsubscribes from my Campaign Monitor 'Newsletter' list, post their email and whether they joined or left 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

For a membership group, a community newsletter or a small shop, every subscriber is a real person, and the list is a living thing. When someone signs up, the owner wants to welcome them or tell the sales rep. When someone leaves, they want to know whether it was one quiet departure or the start of a trend. Campaign Monitor tracks both, but only in reports that few people open.

ClickRuntime creates a webhook on your Campaign Monitor list. Whenever a subscriber joins or leaves, Campaign Monitor calls it, and a message goes to Slack with the email address and the type of event. The post is made as the change happens, so the channel works as a live view of the list.

It helps organizers who want to react to list changes the same day without logging in to review reports.

What you get out of it

New members can be welcomed personally
Seeing a signup in a channel lets someone send a friendly note within minutes. A personal welcome stands out from automated email and tends to build loyalty. Quick, human attention at the moment of joining makes a visible difference to how new members feel about your group.
Departures are noticed one by one
A single unsubscribe from an important contact is worth a gentle question. Seeing each departure lets you understand why people leave, rather than just watching the total drop. Understanding why individuals leave helps far more than watching a total shrink without any explanation.
Spikes are visible immediately
If twenty people unsubscribe within an hour of a send, the channel shows it. You can pause the next campaign and investigate while the cause is fresh. If twenty people leave within an hour of a send, you can pause the next campaign and find the cause while it is fresh.
Sales and community teams stay informed
People who do not use Campaign Monitor still see list changes. A rep can reach out to a new lead, and a community manager can greet a new member. Staff who never open Campaign Monitor still see changes to the list, and can act on them straight away.
Odd signups are caught
A sudden run of strange addresses may be a bot hitting your signup form. Seeing it live lets you add protection before the list fills with junk. Spotting bots early stops a junk-filled list from hurting deliverability.

How it works

What happens, step by step

When someone joins or leaves your Campaign Monitor list, Campaign Monitor tells ClickRuntime straight away.
ClickRuntime checks whether each change is a sign-up or an unsubscribe and ignores anything else.
It posts a one-line message to #marketing in Slack saying who joined or left the list.

Before it runs live

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

What you get

RunsThe moment it happens

Post list sign-ups and unsubscribes to Slackjust nowSucceeded

Slack · #marketingdana@northwind.com joined the Newsletter list

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 Campaign Monitor 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.

new_subscriber_unsubscribe_alerts.pyexample

from clickruntime import on_event, notify

LABELS = {"Subscribe": "joined", "Deactivate": "left"}

@on_event
def handle(event):
    posted = 0
    for e in (event.json or {}).get("Events", []):
        action = LABELS.get(e.get("Type"))
        if action:
            notify.slack(f"{e['EmailAddress']} {action} the Newsletter list", channel="#marketing")
            posted += 1
    return {"posted": posted}

FAQ

Common questions

Does the alert show which list the person joined or left?

The webhook is created for a specific list, so the alert reflects that list. If you run several lists, you can create a webhook for each and include the list name in the message so the channel makes sense.

Can I post unsubscribes and signups to different channels?

Yes. Each event arrives with a type, so the workflow can send signups to one channel and unsubscribes to another, such as a growth channel and a retention channel. Say what you prefer to your AI assistant.

Does it need special permission in Campaign Monitor?

Creating a list webhook needs API access to the list, using your API key. The key is kept as a secret by ClickRuntime. You can review or delete the webhook in Campaign Monitor at any time.

What permissions does it need?

API key (full account). 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.

Daily