Skip to main content

Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets

Workflow preview

Workflow preview
100%
Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets preview
Open on n8n.io

1. Workflow Overview

How it works This workflow automatically handles every failed Stripe payment by collecting all details, assessing severity, and taking immediate action — alerting your team, creating recovery tasks...

Best for

  • CRM automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.clickup, n8n-nodes-base.googlesheets, n8n-nodes-base.gmail, n8n-nodes-base.stripetrigger, n8n-nodes-base.hubspot

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets
Workflow name
Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets

How it works

This workflow automatically handles every failed Stripe payment by collecting all details, assessing severity, and taking immediate action — alerting your team, creating recovery tasks, escalating repeat failures, notifying the customer, and logging everything — without any manual effort.

Step-by-step

  • Trigger & parse

  • Stripe Trigger – Listens for charge.failed, invoice.payment_failed, and payment_intent.payment_failed events from Stripe.

  • Parse & Enrich Payment Data – Extracts and normalizes customer name, email, plan, amount, failure code, attempt count, and assigns severity (LOW / MEDIUM / HIGH / CRITICAL) and ClickUp priority based on payment amount.

  • High value check

  • High Value Check – Checks if the failed payment is $1,000 or more to route it to a critical or standard alert path.

  • Slack — Critical Alert – Posts a urgent CRITICAL PAYMENT FAILURE message to Slack with full payment and customer details.

  • Slack — Standard Alert – Posts a standard payment failed message to Slack for lower-value failures.

  • Task creation

  • ClickUp — Create Recovery Task – Creates a prioritized recovery task in ClickUp with due date set to 24h (critical) or 48h (standard) from failure time.

  • Repeat failure check

  • Retry Count Check – Checks if the payment has failed more than twice to determine if escalation is needed.

  • Slack — Escalation Alert – Sends a ESCALATION message tagging the billing manager when repeated failures are detected.

  • Customer notification & logging

  • Send a message – Sends an HTML-formatted Gmail to the customer explaining the failure, reason, and next retry date.

  • Log to Google Sheets – Appends all payment failure details including severity, attempt count, failure code, and Stripe links to a tracking sheet.

  • Create or update a contact – Creates or updates the customer record in HubSpot with their name, email, and plan details.

Why use this?

  • Instantly catches every Stripe payment failure across all event types with zero manual monitoring
  • Severity-based routing ensures critical high-value failures get immediate escalated attention
  • Auto-creates ClickUp recovery tasks so every failure has an owner and a deadline
  • Escalates repeated failures automatically so chronic issues never slip through unnoticed
  • Keeps customers informed with professional failure emails while logging everything for reporting and CRM hygiene

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 - Parse & Enrich Payment Data

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

Block 2 - High Value Check

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

Block 3 - Slack — Critical Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 4 - Slack — Standard Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 5 - ClickUp — Create Recovery Task

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

Block 6 - Retry Count Check

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

Block 7 - Slack — Escalation Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 8 - Log to Google Sheets

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

Block 9 - Send a message

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 10 - Stripe Trigger

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

Block 11 - Create or update a contact

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2.2

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

Block 14 - Sticky Note2

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

Block 15 - Sticky Note3

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

Block 16 - Sticky Note4

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

Block 17 - Sticky Note5

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

Block 18 - Sticky Note6

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

3. Summary Table

Workflow Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets
Complexity advanced
Nodes 18
Categories CRM
Author Avkash Kakdiya
Published 21 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15873/15873.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 Handle failed Stripe payments with Slack, ClickUp, Gmail and Google Sheets do?

How it works This workflow automatically handles every failed Stripe payment by collecting all details, assessing severity, and taking immediate action — alerting your team, creating recovery tasks...

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 CRM use case.