Zendesk Refund Tickets
New Zendesk refund ticket? It checks the WooCommerce order, alerts Slack for damaged items, or emails customers for proof on other cases.
What it does
You get instant Slack alerts for damaged items when a Zendesk refund is linked to a WooCommerce order, or you receive clear email requests for proof on all other cases. This automation handles the validation and routing so your team can focus on resolving refunds efficiently without manual checks.
Step by step
- Extract the WooCommerce order ID from the Zendesk ticket description using a regex pattern.
- Call the WooCommerce API to fetch order details and verify the refund eligibility status.
- Route the workflow to either Slack or Gmail based on the specific refund reason code.
Where the LLM does the work
- Generate natural language summaries for the internal Slack notifications about damaged items.
- Draft polite, context-aware email templates requesting proof of damage from customers via Gmail.
- Classify ambiguous refund reasons into standard categories like 'damaged' or 'wrong item'.
Watch out for
Zendesk ticket descriptions may lack a valid order ID so add validation to skip malformed tickets gracefully.
Slack webhook URLs expire or change so store them in secure environment variables rather than hardcoding.
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 Zendesk Refund Tickets: New Zendesk refund ticket? It checks the WooCommerce order, alerts Slack for damaged items, or emails customers for proof on other cases. ## Specification - What it does: You get instant Slack alerts for damaged items when a Zendesk refund is linked to a WooCommerce order, or you receive clear email requests for proof on all other cases. This automation handles the validation and routing so your team can focus on resolving refunds efficiently without manual checks. - Trigger: Triggered by an event (Event · on new Zendesk ticket) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - Zendesk: Ticket trigger and data extraction - WooCommerce: Order lookup and validation - Slack: Internal team alerts for damaged items - Gmail: Customer emails for proof or confirmation ## Known pitfalls, handle each one explicitly in your implementation 1. Zendesk ticket descriptions may lack a valid order ID so add validation to skip malformed tickets gracefully. 2. Slack webhook URLs expire or change so store them in secure environment variables rather than hardcoding. ## Reference implementation https://n8n.io/workflows/14861 (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/automate-zendesk-refund-tickets/ via usecasesforagents.com
Frequently asked questions
Can I use a different Support & Ticketing than Zendesk?
Yes. Zendesk is only the example support & ticketing in this recipe. The same flow works with Hiver, Intercom, Marker.io and Syncro. Swap the support & ticketing 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 support teams drowning in inbound and looking to triage faster, not just harder.
Also fits E-commerce Operator.