The moment it happens
Get refund details in Slack
Every refund, partial ones included, is posted with the order number, amount and reason.
- Runs
- The moment it happens
- Apps
- WooCommerce
- AI
- Not needed
- Access
- read (write to create webhook)
Send this to your assistant
Create a ClickRuntime automation: when an order is refunded in my WooCommerce store, fully or partly, post the order number, refunded amount and reason to #support in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Refunds in a WooCommerce shop can be created by any staff member with the right permissions, and each one is money leaving the business. Without a signal, the owner sees them only in the monthly accounts. A pattern, such as a product with many refunds, a staff member issuing large refunds without a note, or a customer refunded repeatedly, goes unnoticed for weeks, long after something could have been done about it.
When a refund is registered, WooCommerce sends an event. The automation checks the order's status and refunds, fetches the refund reason, and posts the order number, amount and reason to Slack so the owner sees every refund as it happens.
It is a good control for shops with several staff, and for owners who want to track why customers ask for money back.
What you get out of it
Spot refund patterns early
Three refunds for the same product in a week suggest a quality problem. Seeing each one live lets you check the product while there is still stock to inspect. A product pulled from sale early costs less than a month of refunds.
Oversight of staff-issued refunds
A visible message for every refund gives the owner a light-touch control, so an unusual amount or a missing reason is questioned the same day. A control that costs nothing in staff time is easy to keep running.
Reasons feed product decisions
The refund reason shows whether items are arriving damaged, not matching photos, or simply wrong in size. That guides what to fix in the listing or packaging. Small fixes to a description or box can cut the same complaint in future orders.
Reconciliation is easier
The channel history lists each refund with its amount and date, which your bookkeeper can match against payment processor reports without chasing. That saves the finance person from reconstructing refund dates at month end.
Possible fraud is visible
Repeated refunds for one customer, or a refund soon after a large order, stand out when they appear in a feed rather than inside a table of orders. Patterns like these are almost impossible to see inside a long table of orders.
How it works
What happens, step by step
When an order in your WooCommerce store is refunded, in full or in part, ClickRuntime picks it up.
It reads the refunded amount and the reason given for the refund.
A message goes to your #support Slack channel with the order number, amount and reason, so the team can see why it happened.
Before it runs live
- Connect WooCommerce
- 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 WooCommerce steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, state, notify
STORE = "https://yourstore.com/wp-json/wc/v3"
@on_event
def handle(event):
order = event.json
if not order.get("refunds"):
return {"posted": False}
auth = (credentials.secret("WC_CONSUMER_KEY"), credentials.secret("WC_CONSUMER_SECRET"))
refunds = http.get(f"{STORE}/orders/{order['id']}/refunds", auth=auth).json()
seen = set(state.get(f"refunds:{order['id']}") or [])
new = [r for r in refunds if r["id"] not in seen]
for r in new:
kind = "Full" if order["status"] == "refunded" else "Partial"
notify.slack(f"{kind} refund on order #{order['number']}: {order['currency']} {r['amount']}\n"
f"Reason: {r.get('reason') or 'none given'}", channel="#support")
state.set(f"refunds:{order['id']}", [r["id"] for r in refunds])
return {"posted": len(new)}FAQ
Common questions
Does it fire for partial refunds?
What if no reason was entered?
Is the refund also sent back to the customer's payment method?
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
Keep WooCommerce products in sync with a supplier feed
Products sent to your link are created when the SKU is new, otherwise their price and stock are updated.
See how it worksPost big WooCommerce orders to Slack
Orders above your threshold show up in Slack with the number, total and a link as they come in.
See how it worksFlag risky WooCommerce orders before you ship
Orders that match your warning signs are posted to Slack and noted on the order itself.
See how it worksKeep exploring
Set up “Get refund details in Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.