Skip to main content

🚀 Automated Stripe payment recovery: track failures & follow-up emails

Workflow preview

Workflow preview
100%
🚀 Automated Stripe payment recovery: track failures & follow-up emails preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Automated Stripe Payment Recovery Workflow (n8n) Detect failed payments, log them, and send polite follow up emails to recover revenue — all automated with n8n. Part A – Detect & log failed pa...

Best for

  • Invoice Processing automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stripetrigger, n8n-nodes-base.set, n8n-nodes-base.googlesheets, n8n-nodes-base.removeduplicates, n8n-nodes-base.scheduletrigger, n8n-nodes-base.switch, n8n-nodes-base.sendinblue, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by iamvaar.

Original n8n.io source

1.1 Workflow description

Title
🚀 Automated Stripe payment recovery: track failures & follow-up emails
Workflow name
🚀 Automated Stripe payment recovery: track failures & follow-up emails

🚀 Automated Stripe Payment Recovery Workflow (n8n)

Detect failed payments, log them, and send polite follow-up emails to recover revenue — all automated with n8n.


Part A – Detect & log failed payments

What it does:

  • Listens for failed Stripe payments.
  • Extracts customer & payment info.
  • Logs them neatly in Google Sheets for follow-up.

🧩 Nodes:

1️⃣ Stripe Trigger

  • Listens to:

    payment_intent.payment_failed
    

2️⃣ Set node

  • Extracts & maps fields:

    • Name, Email, Amount (in cents), Currency
    • payment_intent_id
    • added_at → {{ $now }}
    • email_sent_count → 0

3️⃣ Remove Duplicates

  • Keeps the sheet clean (avoids duplicate rows).

4️⃣ Google Sheets node

  • Append or update row:

    • Name, Email, Amount/100, Currency, payment_intent_id, added_at, email_sent_count

> 📌 This builds your “failed payments queue” to drive the follow-up emails later.


🔁 Part B – Daily follow-up emails

What it does:

  • Runs daily.
  • Checks which users haven’t received 2 emails yet.
  • Sends reminder emails and tracks how many were sent.

🧩 Nodes: 1️⃣ Schedule Trigger

  • Runs every day at 10 AM (0 10 * * *)

2️⃣ Get Payment Failure Leads

  • Reads rows from Google Sheet.

3️⃣ Switch node (Check for no. of emails sent)

  • If email_sent_count < 1 → send first email.
  • Else if email_sent_count < 2 → send second email.
  • Else → mark as "quit sending emails".

4️⃣ Send First Email

  • Sends a gentle reminder with billing page button.

5️⃣ Update Email Count

  • Increments email_sent_count by +1 in Google Sheets.

6️⃣ Send Second Email

  • Sends final, urgent reminder.

7️⃣ Quit Sending Emails to these Leads

  • Marks that no more emails should be sent.

📝 Headline

> 🚀 Automated Stripe Payment Recovery: Track Failures & Send Follow-Up Emails via n8n


Why this matters:

  • Catch failed payments automatically.
  • Log every attempt & follow-up count.
  • Recover lost revenue while staying polite and respectful.
  • Avoid spamming by capping follow-ups to 2 emails.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Detect Failed Payments

Type / Role
n8n-nodes-base.stripeTrigger - stripeTrigger
Config choices
Version 1

Block 2 - Extract User and Payment Info

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 3 - Append or update row in sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 4 - Remove Duplicates

Type / Role
n8n-nodes-base.removeDuplicates - removeDuplicates
Config choices
Version 2

Block 5 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 6 - Update Email Count

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 7 - Get Payment Failure Leads

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 8 - Check for no. of emails sent

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 9 - Send First Email

Type / Role
n8n-nodes-base.sendInBlue - sendInBlue
Config choices
Version 1

Block 10 - Send Second Email

Type / Role
n8n-nodes-base.sendInBlue - sendInBlue
Config choices
Version 1

Block 11 - Quit Sending Emails to these Leads

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 12 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow 🚀 Automated Stripe payment recovery: track failures & follow-up emails
Complexity intermediate
Nodes 13
Categories Invoice Processing
Author iamvaar
Published 05 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5702/5702.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does 🚀 Automated Stripe payment recovery: track failures & follow-up emails do?

Automated Stripe Payment Recovery Workflow (n8n) Detect failed payments, log them, and send polite follow up emails to recover revenue — all automated with n8n. Part A – Detect & log failed pa...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Invoice Processing use case.