The flow
Starts it 1Logic 15Service 7
The steps in the order they run, from what starts it.
- 1Run test refundManual triggerStarts it
- 2Refund requestSetLogic
- 3Validate requestCodeLogic
- 4Read Stripe paymentHttp RequestService
- 5Require test paymentCodeLogic
- 6Check refundAllowlyService
- 7Validate decisionCodeLogic
- 8Allowed immediatelyIfLogic
- 9Refund permittedCodeLogic
- 10Needs reviewIfLogic
- 11Create Stripe test refundHttp RequestService
- 12Wait for reviewerWaitLogic
- 13Stop refundStop And ErrorLogic
- 14Refund resultCodeLogic
- 15Validate reviewCodeLogic
- 16Fetch decision receiptHttp RequestService
- 17Confirmation requestedIfLogic
- 18Export refund evidenceCodeLogic
- 19Resolve confirmationAllowlyService
- 20Resolve escalationAllowlyService
- 21Reviewer approvedIfLogic
- 22Recheck refund after reviewAllowlyService
- 23Require final allowCodeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 23, with 4 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. 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?
Take your time. At 23 steps it is large: read it before trusting it with anything live.
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 23 steps before you point it at anything that matters.