Notify Slack On Refund
Monitors WooCommerce for refunded orders over 100 and posts an alert to your Slack channel.
founders and execsops and IT teams
What it does
Monitors WooCommerce for order status updates specifically when an order is refunded. It checks if the refund amount exceeds a set threshold (e.g., over 100). If the condition is met, it automatically posts a notification to a designated Slack channel.
Step by step
- Parse the WooCommerce webhook payload to extract order_id and refund_amount fields.
- Compare the extracted refund_amount against the configured threshold value using standard numeric comparison operators.
- Construct a formatted JSON message object containing the order details for the Slack API request.
Where the LLM does the work
- Draft engaging and concise notification text that highlights the urgency of high-value refunds without sounding alarmist.
- Design the visual structure of the Slack block kit elements to ensure readability on both mobile and desktop interfaces.
Watch out for
Currency mismatches between WooCommerce and your code can lead to incorrect threshold comparisons so always normalize amounts to cents or a consistent decimal format before comparing.
Tools that fit
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Notify Slack On Refund: Monitors WooCommerce for refunded orders over 100 and posts an alert to your Slack channel. ## Specification - What it does: Monitors WooCommerce for order status updates specifically when an order is refunded. It checks if the refund amount exceeds a set threshold (e.g., over 100). If the condition is met, it automatically posts a notification to a designated Slack channel. - Trigger: Triggered by an event (Event · on order refund) - Autonomy: Fully hands-off - Expected setup effort: under an hour - Tools/services involved: - WooCommerce: Detecting refunded orders - Slack: Posting notifications to channel ## Known pitfalls, handle each one explicitly in your implementation 1. Currency mismatches between WooCommerce and your code can lead to incorrect threshold comparisons so always normalize amounts to cents or a consistent decimal format before comparing. ## Reference implementation https://n8n.io/workflows/1460 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/notify-slack-on-refund/ via usecasesforagents.com
Frequently asked questions
Can I use a different Ecommerce than WooCommerce?
Yes. WooCommerce is only the example ecommerce in this recipe. The same flow works with Adobe Commerce (Magento 2), AliExpress Affiliate API, Shopify and Zoho Commerce. Swap the ecommerce connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for founders and execs who need e-commerce handled without hiring for it.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.