The flow
Starts it 1Logic 11Service 5
The steps in the order they run, from what starts it.
- 1Zendesk – New Refund Ticket TriggerZendesk triggerStarts it
- 2IfIfLogic
- 3Normalize Zendesk Ticket DataCodeLogic
- 4WooCommerce – Fetch Order by IDWoo CommerceService
- 5Merge Ticket and Order DataMergeLogic
- 6Normalize WooCommerce Order DataCodeLogic
- 7Is Refund Reason = Damaged Item?IfLogic
- 8Check Order Status (Completed or Processing)IfLogic
- 9Slack – Notify Damaged Item RefundSlackService
- 10Route Refund Type (Wrong / Partial / Full)SwitchLogic
- 11Check If Order Already RefundedIfLogic
- 12Prepare Email – Wrong Item Proof RequestSetLogic
- 13Prepare Email – Partial Refund ReviewSetLogic
- 14Prepare Email – Full Refund Return RequiredSetLogic
- 15Email Customer – Request Proof (Wrong Item)GmailService
- 16Email Customer – Partial Refund Under ReviewGmailService
- 17Email Customer – Return Required for RefundGmailService
How it's built
- Starts on
- An event in a connected app
- Steps
- 17, with 5 branches
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Slack, WooCommerce
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Slack and WooCommerce accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 17 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 17 steps before you point it at anything that matters.