Block 1 - Parse & Enrich Payment Data
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
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...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis 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.
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.
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.
| 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 |
Use the JSON export at /data/workflows/15873/15873.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.