n8n Workflow: Stripe Failed Payment Recovery

How This Blueprint Works

Involuntary churn from failed payments is every SaaS company’s silent revenue leak. This workflow listens for Stripe invoice.payment_failed events and runs a smart dunning sequence: email the customer, retry the charge on a schedule, escalate to a higher-performing card, and finally downgrade the subscription.

The Execution Sequence

1. Stripe Trigger Node — Uses the Stripe Trigger node to subscribe to invoice.payment_failed events. Fires instantly when a credit card charge fails. Captures invoice ID, customer ID, amount_due, and failure code (card_declined, insufficient_funds, expired_card, etc.).
2. Customer Lookup Node — An HTTP Request node that calls GET /v1/customers/{id} with the Stripe secret key. Retrieves customer email, name, phone, and payment_methods list. Identifies if there is a secondary payment method available for retries.
3. Dunning Sequencer Node — A Code node running the recovery sequence: Day 1 — send email notification + retry charge immediately. Day 3 — send reminder email + retry with updated card if available. Day 7 — final email + retry. Each touch increments urgency tone.
4. Email + Retry Node — An HTTP Request node that sends personalized dunning emails via SendGrid/SMTP. The email includes a secure payment link (Stripe Hosted Invoice Page). The same node retries the charge using Stripe’s /v1/invoices/{id}/pay endpoint.
5. Subscription Downgrader Node — If all retries exhaust, calls Stripe API to update the subscription to a free tier or limited access plan. Logs the downgrade to a Google Sheet for customer success team follow-up.

FAQ

What Stripe events can this workflow handle?

Primary: invoice.payment_failed. Also handles payment_intent.payment_failed, invoice.payment_action_required (SCA 3D Secure), and customer.subscription.updated for post-recovery status tracking.

How does smart card retry work?

The workflow checks the customer’s default_payment_method. If the failure was on a card, and the customer has another card saved, it sets the backup card as the new default and retries. This recovers ~15% of failed payments.

Can I customize the dunning email timing?

Yes. The dunning schedule is configured as variables in the Code node (touch_1_delay, touch_2_delay, touch_3_delay). Default: immediate, 72 hours, 168 hours (7 days). Adjust per business model — SaaS typically gives more time than e-commerce.

The JSON Blueprint Structure

{
  "name": "Stripe Smart Dunning",
  "nodes": [
    { "name": "Stripe Trigger", "type": "n8n-nodes-base.stripeTrigger", "position": [250, 300] },
    { "name": "Customer API", "type": "n8n-nodes-base.httpRequest", "position": [450, 300] },
    { "name": "Dunning Logic", "type": "n8n-nodes-base.code", "position": [650, 300] },
    { "name": "SendGrid Email", "type": "n8n-nodes-base.httpRequest", "position": [850, 300] }
  ]
}

What You Get Inside Your SynthOperator System

This workflow is one of 27,400+ blueprints included in the n8n Business Automation OS ($17, one-time). When you deploy the complete system, you get:

• 27,400+ pre-built workflow JSON files across every business domain
• 15 elite AI agents integrated into your automation pipelines
• Lifetime updates, offline operation, and zero recurring fees

**Deploy your complete automation infrastructure today.