Handle retail payment failures with retry emails, Slack alerts and Supabase logging
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 17 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Slack, Gmail and Supabase.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Normalize Payment Data (Edit Fields (Set)): sets or maps fields
- Identify Failure Type (Function): runs custom JavaScript (legacy Function node)
- Route by Failure Type (If): checks a condition and branches into true / false
- Notify Team: Payment Failed (Slack): uses Slack
- Is This a Fraudulent Payment? (If): checks a condition and branches into true / false
- Is This a High-Value Order? (If): checks a condition and branches into true / false
- Notify Team: Fraud Detected (Slack): uses Slack
- Notify Team: Payment Failure (Slack): uses Slack
- Notify Customer to Retry Payment (Gmail): uses Gmail
- Log Fraud Case (Edit Fields (Set)): sets or maps fields
…plus 6 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Identify Failure Type: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Identify Failure Type | Code node, mode 'Run Once for All Items' |
Nodes used (8)
- If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Function
n8n-nodes-base.function - Slack
n8n-nodes-base.slack - Gmail
n8n-nodes-base.gmail - Wait
n8n-nodes-base.wait - Supabase
n8n-nodes-base.supabase - Webhook
n8n-nodes-base.webhook
From the author
Retail Payment Failure Alerts with Retry Emails, Slack & Supabase This n8n workflow automatically handles failed payment events from payment gateways such as Stripe, Shopify, PayPal or WooCommerce. It receives payment failure webhooks, standardizes the…