The moment it happens
Get 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.
- Runs
- The moment it happens
- Apps
- Gumroad
- AI
- Not needed
- Access
- access token
Send this to your assistant
Create a ClickRuntime automation: when a Gumroad sale is disputed, email me right away with the product, the buyer's email and the disputed amount.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
When a buyer disputes a payment, the clock starts. Gumroad and the payment processor give the seller a short window to respond, and a dispute noticed after the deadline is a lost dispute: the sale is reversed and a fee is added. Creators who check email once a day, or who sell while traveling, may find out about a chargeback days later, when the evidence window has already closed. The cost compounds: lost revenue, a fee, and a mark on the account.
The moment Gumroad reports a dispute, an email arrives with the sale details included: the product, the amount, the buyer's email and the sale ID. You can answer the same day, with proof of delivery in hand.
It is worth having for anyone selling digital goods, where disputes are more common because there is no shipping record.
What you get out of it
More disputes can be won
Responding quickly with proof of delivery or download activity gives you a stronger case than a late, rushed reply. Prompt proof of delivery, download logs or a friendly explanation usually works better than anything assembled in the last hour before the deadline.
No missed deadlines
The alert reaches you while the response window is open, which protects revenue you have already earned. Revenue you have already earned stays yours when the evidence goes in on time, and that protects a creator whose month depends on a few large sales.
Contact the buyer before it escalates
Sometimes a buyer just did not recognize the charge. A friendly note from you, sent early, can lead them to withdraw the dispute. A disputed charge is often a recognition problem, such as an unfamiliar statement descriptor, and a quick note from you can clear it up before it escalates to a formal chargeback.
All details in the message
The email includes sale details, so you do not have to search Gumroad to work out which purchase is involved. No digging through the Gumroad sales list, because the product, amount, buyer email and reference arrive in the message itself.
Patterns become visible
Repeated disputes on one product or from one region may point to unclear descriptions or fraud, which you can only see if each one is noticed. If disputes cluster on one product or one sort of buyer, you may need clearer descriptions, a visible refund policy or better fraud checks, and each alert is a data point.
A written record for your own files
Every alert is a dated email. If a dispute is escalated, or you need to show how quickly you responded, you have a clear timeline in your inbox and nothing to reconstruct.
How it works
What happens, step by step
When a buyer disputes a Gumroad payment with their bank, Gumroad tells ClickRuntime straight away.
ClickRuntime reads the product, the buyer and the disputed amount from the sale details Gumroad includes.
You get an email with the product, the buyer's email and the disputed amount, so you can gather evidence quickly.
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("disputed") != "true":
return {"emailed": False}
amount = int(ping.get("price", 0)) / 100
notify.email_me(f"⚠️ Gumroad dispute: {ping['product_name']}",
f"Product: {ping['product_name']}\nBuyer: {ping.get('email')}\n"
f"Disputed amount: {ping.get('currency', 'usd').upper()} {amount:,.2f}\nSale ID: {ping.get('sale_id')}")
return {"sale": ping.get("sale_id")}FAQ
Common questions
Does this stop the chargeback?
What details are in the email?
Can the alert also go to Slack or a teammate?
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 emailed about Gumroad refunds and membership cancellations
You hear straight away when a buyer is refunded or a member cancels.
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 an instant email when a Gumroad payment is disputed” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.