The moment it happens

Announce subscriptions, cancellations and failed payments in Slack and Telegram

Every new subscription, cancellation and failed payment is posted to your revenue channel in Slack and sent to you on Telegram.

Runs: The moment it happens
Apps: Slack, Telegram
AI: Not needed
Access: Telegram bot token; Slack chat:write

Send this to your assistant

Create a ClickRuntime automation: when LemonSqueezy sends a subscription webhook, post it to #revenue in Slack and to my Telegram.

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 two-founder SaaS business bills through LemonSqueezy. A failed card payment means a customer is about to lose access, and a cancellation is a chance to ask why. Both founders mean to check the billing dashboard daily, but in a busy week a failed payment goes unnoticed until the customer is already gone, and nobody asked the cancelling customer a single question.

Seeing every subscription event the moment it happens, in Slack for the team and on Telegram for the founder on the move, means failed payments get a friendly nudge and cancellations get a quick, personal follow-up.

What you get out of it

Save customers with failed payments
A failed payment alert lets you reach out before the customer loses access. A quick note about updating their card often keeps the subscription.
Learn why people cancel
Hearing about a cancellation right away is the best moment to ask for feedback. The answers point to what to fix next.
Celebrate new customers together
New subscriptions appear in the team channel as they happen. Everyone sees the business growing, not only whoever checks the dashboard.
On your phone when it matters
Telegram reaches you away from your desk. A failed payment from a large account does not wait until you are back at your laptop.
A daily count at a glance
Events are counted per day, and each message shows the running total. A day with unusual cancellations stands out immediately.

How it works

What happens, step by step

When LemonSqueezy reports a subscription change, ClickRuntime receives it straight away.
It checks the message came from your store and picks out the event, the customer and the plan.
It adds the event to today's count.
A short message is posted to #revenue in Slack and sent to you on Telegram.

Before it runs live

Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
Connect Telegram
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Announce subscriptions, cancellations and failed payments in Slack and Telegramjust nowSucceeded

Slack · #revenue⚠️ subscription payment failed: Northwind Studio on Team plan, monthly (#1 today)

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 Google Sheets
Combine it with other Slack and Telegram 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.

subscription_event_alerts.pyexample

from clickruntime import on_event, credentials, http, notify, state, verify

TELEGRAM_CHAT_ID = "your-telegram-chat-id"
ICONS = {"subscription_created": "🎉", "subscription_cancelled": "👋", "subscription_payment_failed": "⚠️", "subscription_payment_success": "🔁"}

@on_event
def handle(event):
    if not verify.generic_hmac_sha256(event.body, event.header("X-Signature") or "", credentials.secret("LEMONSQUEEZY_SIGNING_SECRET")):
        return {"skipped": "bad signature"}
    body = event.json or {}
    name = body.get("meta", {}).get("event_name", "")
    a = body.get("data", {}).get("attributes", {})
    state.increment_metric(name or "event", ttl_days=90)
    points = state.query_metric(name or "event")
    count = points[-1]["value"] if points else 1
    text = f"{ICONS.get(name, '💳')} {name.replace('_', ' ')}: {a.get('user_name', '')} on {a.get('product_name', '')} {a.get('variant_name', '')} (#{count} today)"
    notify.slack(text, channel="#revenue")
    http.post(f"https://api.telegram.org/bot{credentials.secret('TELEGRAM_BOT_TOKEN')}/sendMessage", json={"chat_id": TELEGRAM_CHAT_ID, "text": text})
    return {"event": name}

FAQ

Common questions

Which events are announced?

New subscriptions, cancellations, renewals and failed payments, plus any other subscription event you enable in LemonSqueezy's webhook settings. Each type gets its own icon so they are easy to tell apart.

Is each webhook checked to be genuine?

Yes. LemonSqueezy signs every webhook with your signing secret, and messages that do not match are ignored.

Can I use a different billing platform?

Yes. Any billing tool that sends webhooks for subscription changes works the same way. Only the field names and the signature check change.

What permissions does it need?

Telegram bot token; Slack chat:write. 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