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