The moment it happens
Post new Recurly subscriptions to Slack
Every new subscription shows up with the account, plan and price as soon as it starts.
- Runs
- The moment it happens
- Apps
- Recurly
- AI
- Not needed
- Access
- private API key
Send this to your assistant
Create a ClickRuntime automation: when a Recurly subscription starts, post the account name, plan and price to #wins in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
When a new customer signs up for a paid plan, the whole team benefits from knowing, but Recurly only shows it to people who log in. Sales cannot congratulate the rep who closed the deal, support does not know who to expect questions from, and the founders miss the small daily proof that the business is growing.
Whenever a new subscription is created in Recurly, ClickRuntime receives the notification, fetches the subscription and posts to Slack the plan, the account and the amount. It happens within moments of signup, so the channel becomes a live feed of new customers, the plans they pick and how much they are paying each period.
It is a good choice for early-stage SaaS and membership businesses where each new customer is still worth celebrating.
What you get out of it
Wins are shared in real time
A new paid signup deserves a moment of recognition. Seeing it in a team channel reminds everyone why the work matters, and it is a cheap boost to morale. The people who built the product deserve to see who is paying for it.
Support can prepare for new users
Knowing a customer on a premium plan has just signed up lets support check that onboarding is ready. First impressions matter most in the first days of a subscription. A quick welcome email from a human can set the tone for the whole relationship.
Plan mix is visible at a glance
A feed showing which plans people choose reveals how pricing is working. If nearly everyone picks the cheapest tier, that is useful information for packaging. You will see which price points are working in practice.
Signup problems surface quickly
If the feed goes quiet after a pricing change or a deploy, something may be wrong with checkout. A gap in the stream is as informative as a flood. That may be the first sign that checkout has broken.
Sales and marketing see the results
A campaign launched this morning shows its first paying customers by lunch. Marketers get feedback while they can still adjust copy or budget. Early evidence helps decide whether to double down.
How it works
What happens, step by step
When someone starts a new Recurly subscription, Recurly tells ClickRuntime straight away.
ClickRuntime looks up the subscription to get the account name, the plan and the amount.
A message goes to your #wins Slack channel with those details.
Before it runs live
- Connect Recurly
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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 Recurly steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, notify
API = "https://v3.recurly.com"
def recurly(path):
resp = http.get(f"{API}{path}", auth=(credentials.secret("RECURLY_API_KEY"), ""),
headers={"Accept": "application/vnd.recurly.v2021-02-25+json"})
resp.raise_for_status()
return resp.json()
@on_event
def handle(event):
body = event.json
if (body.get("object_type"), body.get("event_type")) != ("subscription", "created"):
return {"posted": False}
sub = recurly(f"/subscriptions/uuid-{body['uuid']}")
account = sub["account"]
name = account.get("company") or f"{account.get('first_name', '')} {account.get('last_name', '')}".strip()
notify.slack(f"π {name} started *{sub['plan']['name']}* at {sub['currency']} {sub['unit_amount']:,.2f}",
channel="#wins")
return {"subscription": sub["id"]}FAQ
Common questions
Does it announce trials or only paid subscriptions?
Will it post renewals and upgrades?
Can the amount be hidden from the channel?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Track failed Recurly renewals and dunning in Slack
Each failed renewal or dunning step appears in your channel with the account, amount and plan.
See how it worksGet a Slack message when a Recurly subscription is cancelled
You hear about cancellations as they happen, so key accounts get a call before they leave.
See how it worksEmail a weekly count of new and cancelled subscriptions
Each Monday you see how many subscriptions you gained and lost the week before.
See how it worksKeep exploring
Set up βPost new Recurly subscriptions to Slackβ from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
