The moment it happens
Get emailed about Gumroad refunds and membership cancellations
You hear straight away when a buyer is refunded or a member cancels.
- Runs
- The moment it happens
- Apps
- Gumroad
- AI
- Not needed
- Access
- access token
Send this to your assistant
Create a ClickRuntime automation: email me whenever a Gumroad sale is refunded or a membership is cancelled, with the product, the buyer's email and the amount.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Revenue leaks quietly. A buyer asks for a refund, a member cancels a monthly membership, and unless you open Gumroad you may not hear about it until the monthly totals look off. A creator who sells a course or a membership community needs to know early, because a refund is often the only direct feedback they get about what disappointed someone, and a cancellation is the last chance to ask why.
As soon as Gumroad reports a refund or a membership cancellation, you get an email with the details. You read it the same day and can reply to the customer, fix a problem with the product or adjust your offering.
It is useful for membership owners, course creators and anyone who wants to learn from refund patterns rather than just see them in a report.
What you get out of it
Chances to win customers back
A quick, kind message after a cancellation sometimes saves the membership, or at least yields a reason you can learn from. A quick, kind message after a cancellation sometimes saves the membership, or at least gives you a real reason.
Refund reasons guide improvements
If three people refund the same course within a week, you probably have a problem with the description, the audio or the content. You hear about it while it is still fixable. If three people refund the same course within a week, you probably have a problem with the description, audio or content, and you hear about it while it is still fixable.
No surprises at month-end
Revenue figures match what you expect, because you were told about each refund as it happened. Revenue matches expectations because each refund was noticed as it happened. That makes month-end reconciliation with Gumroad payouts a short job.
Support issues are caught
A refund often follows a failed download or a confusing delivery email. Seeing it quickly lets you fix the cause for the next buyer. A refund often follows a failed download or a confusing email, and seeing it quickly lets you repair the cause for the next buyer. Fixing that early protects the next ten buyers. That fix tends to pay back quickly, since every later buyer then gets a smoother start.
Honest picture of churn
Memberships can look healthy in gross sales while cancellations erode the base. Individual alerts make churn tangible. Memberships can look healthy in gross sales while cancellations quietly erode the base, and individual alerts make churn tangible.
How it works
What happens, step by step
When a Gumroad sale is refunded or a membership is cancelled, Gumroad tells ClickRuntime straight away.
ClickRuntime works out whether it is a refund or a cancellation and reads the product, buyer and amount.
You get an email saying which it was, with the product, the buyer's email and the amount.
Before it runs live
- Connect Gumroad
- 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 Gumroad steps into one automation
Under the hood
The code that runs this automation
from urllib.parse import parse_qs
from clickruntime import on_event, notify
@on_event
def handle(event):
ping = {k: v[0] for k, v in parse_qs(event.body).items()}
if ping.get("refunded") == "true":
what, email = "Refund", ping.get("email")
amount = f"${int(ping.get('price', 0)) / 100:,.2f}"
elif ping.get("cancelled") == "true" or "cancelled_at" in ping:
what, email, amount = "Membership cancelled", ping.get("user_email"), "n/a"
else:
return {"emailed": False}
notify.email_me(f"Gumroad {what.lower()}: {ping.get('product_name')}",
f"{what}\nProduct: {ping.get('product_name')}\nBuyer: {email}\nAmount: {amount}")
return {"type": what}FAQ
Common questions
Does it cover both one-time refunds and membership cancellations?
Does the email say why the person refunded?
Can I send refund alerts to a different address than cancellations?
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
Post each Gumroad sale to Slack
Every sale appears in your channel with the product and price the moment it's made.
See how it worksGet an instant email when a Gumroad payment is disputed
As soon as a buyer opens a chargeback you have the product, buyer and amount in your inbox.
See how it worksGet one evening email with the day's Gumroad sales
Instead of an email per sale, you get a single roundup each evening with totals for each product.
See how it worksKeep exploring
Set up “Get emailed about Gumroad refunds and membership cancellations” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.