Skip to main content

Recover failed Stripe payments with HighLevel, Gmail and Google Calendar

Workflow preview

Workflow preview
100%
Recover failed Stripe payments with HighLevel, Gmail and Google Calendar preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow listens for Stripe payment failures, looks up the customer in HighLevel, logs or updates the failure in an n8n Data Table, and—when not recently automated—creates a Str...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.stripetrigger, n8n-nodes-base.highlevel, n8n-nodes-base.if, n8n-nodes-base.datatable, n8n-nodes-base.googlecalendar, n8n-nodes-base.stripe, n8n-nodes-base.gmail

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
Recover failed Stripe payments with HighLevel, Gmail and Google Calendar
Workflow name
Recover failed Stripe payments with HighLevel, Gmail and Google Calendar

Quick Overview

This workflow listens for Stripe payment failures, looks up the customer in HighLevel, logs or updates the failure in an n8n Data Table, and—when not recently automated—creates a Stripe coupon and emails it via Gmail while also creating HighLevel follow-up tasks and Google Calendar events.

How it works

  1. Triggers when Stripe reports an invoice.payment_failed or payment_intent.payment_failed event.
  2. Searches HighLevel for a contact matching the Stripe receipt email and stops if no contact is found.
  3. Looks up the customer’s record in an n8n Data Table by email, then either updates the existing row (including recalculating the 30-day failure count) or creates a new failure row.
  4. Checks the Data Table flag to avoid repeating automation if the customer has been handled in the last 30 days.
  5. For customers whose HighLevel custom field value is above the LTV threshold, creates a 5% off coupon in Stripe and sends the coupon code to the customer via Gmail, then marks the Data Table row as automated.
  6. In parallel, fetches the customer’s existing HighLevel tasks and, if no recent incomplete task exists, creates a new HighLevel task for an account manager, schedules a Google Calendar event, and marks the Data Table row as automated.

Setup

  1. Connect your Stripe account credentials and ensure the Stripe trigger is enabled for invoice.payment_failed and payment_intent.payment_failed events.
  2. Connect your HighLevel OAuth2 account, confirm contacts have an email address, and update the LTV custom field reference and threshold used to classify “high LTV” customers.
  3. Create or select an n8n Data Table for payment failures and ensure it includes fields like Email, ContactID, FailureCount, StripePaymentIntentID, and automated_in_last_30_days, then update the Data Table ID in the workflow if needed.
  4. Connect your Gmail OAuth2 credentials and adjust the recipient, subject, and email HTML template (including any links) to match your brand.
  5. Connect your Google Calendar OAuth2 credentials, select the target calendar, and replace the placeholder account manager email and HighLevel assignee ID used for task assignment and event attendees.

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 - Sticky Note

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

Block 2 - Sticky Note1

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

Block 3 - Sticky Note2

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

Block 4 - Sticky Note3

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

Block 5 - Sticky Note4

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

Block 6 - Sticky Note5

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

Block 7 - Sticky Note6

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

Block 8 - Sticky Note7

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

Block 9 - Sticky Note8

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

Block 10 - Sticky Note9

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

Block 11 - Sticky Note10

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

Block 12 - Stripe Event Trigger

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

Block 13 - Fetch Contacts List

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

Block 14 - If Contact Exists

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

Block 15 - If Payment Failure Exists

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

Block 16 - Create Task

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

Block 17 - Create Task for New Failure

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

Block 18 - Update Failure Count

Type / Role
n8n-nodes-base.dataTable - dataTable
Config choices
Version 1.1

Block 19 - Add Payment Failure Record

Type / Role
n8n-nodes-base.dataTable - dataTable
Config choices
Version 1.1

Block 20 - Create Calendar Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 21 - Create Calendar Event for New

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 22 - Create Stripe Coupon

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

Block 23 - Send Coupon Email

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

Block 24 - Create Stripe Coupon for New

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

Showing the first 24 of 40 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Recover failed Stripe payments with HighLevel, Gmail and Google Calendar
Complexity advanced
Nodes 40
Categories CRM
Author iamvaar
Published 24 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15932/15932.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 Recover failed Stripe payments with HighLevel, Gmail and Google Calendar do?

Quick Overview This workflow listens for Stripe payment failures, looks up the customer in HighLevel, logs or updates the failure in an n8n Data Table, and—when not recently automated—creates a Str...

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.