The flow
Starts it 1Logic 11Service 5
The steps in the order they run, from what starts it.
- 1Receive Payment FailureWebhookStarts it
- 2Normalize Payment DataSetLogic
- 3Identify Failure TypeFunctionLogic
- 4Route by Failure TypeIfLogic
- 5Notify Team: Payment FailedSlackService
- 6Is This a Fraudulent Payment?IfLogic
- 7Is This a High-Value Order?IfLogic
- 8Notify Team: Fraud DetectedSlackService
- 9Notify Team: Payment FailureSlackService
- 10Notify Customer to Retry PaymentGmailService
- 11Log Fraud CaseSetLogic
- 12Log Hard Failure CaseSetLogic
- 13Wait Before Next Retry AttemptWaitLogic
- 14Save Payment Failure RecordSupabaseService
- 15Increase Retry Attempt CountSetLogic
- 16Has Retry Limit Been Reached?IfLogic
- 17Log Retry Attempt ResultSetLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 17, with 4 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Slack, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Slack and Supabase accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
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.