Back to Catalog

Recover failed Stripe payments with AI emails (by FlyCode)

FlyCodeFlyCode
24 views
2/3/2026
Official Page

⚙️ Automated Stripe Failed Payment Recovery (with Postmark + AI Email Generator)

Recover failed Stripe subscription payments with AI-personalized emails sent via Postmark.

📝 Template Description

Recover failed subscription payments automatically with Stripe, Postmark, and AI.

This workflow listens for Stripe invoice.payment_failed webhooks, checks that the event is related to an auto-charged subscription, and then automatically sends a personalized email (generated with AI) to the customer. The email is polite, branded, but also urgent — encouraging the customer to pay quickly and avoid service cancellation.


🛠️ How it works

  1. 📣 Webhook
    Listens for Stripe webhook events. Make sure to connect it in your Stripe dashboard (see setup below).

  2. 🧹 Filter (Guard)
    Ensures the event is indeed an invoice event and filters out unrelated webhooks.

  3. 💡 Code Node
    Extracts useful fields (firstName, lastName, customer email, amount, currency, invoice number, hosted invoice URL, subscription description, account name).

  4. ✅ If Node
    Verifies that:

    • Event type = invoice.payment_failed
    • Billing reason = subscription_cycle
    • Collection method = charge_automatically

    👉 This ensures only recurring subscription invoices with auto-payment are processed.

  5. 🤖 AI Agent + OpenAI
    Generates a ready-to-send email JSON (to, subject, HTML body) using the extracted Stripe data.
    ✍️ You can customize the prompt here to match your brand’s tone of voice and style.

  6. 🧩 Code Parser
    Parses the AI model’s JSON output into fields (to_email, email_subject, email_body).

  7. 📧 HTTP Request (Postmark)
    Sends the email using Postmark’s API.
    You’ll need your own Postmark Server Token, From address, and Message Stream.


🚀 Setup Instructions

1. Stripe Webhook

👉 Example docs: Stripe: Listen to events with webhooks.

2. Disable Stripe’s Default Failed Payment Emails

  • In Stripe, go to Billing → Settings → Customer emails → Manage failed payments.
  • Turn off “Failed payment” emails under the Revenue Recovery section.
  • This prevents customers from receiving duplicate or conflicting emails.

3. Postmark Setup

  • Create a Postmark account.
  • Add a Server and copy the Server API Token.
  • In n8n, add Postmark credentials with this token.
  • Configure:
    • From = your verified sending email (must be verified in Postmark).
    • MessageStream = typically "outbound" (or any custom stream you set up).

Docs: Postmark API overview.

4. OpenAI Setup

  • Add your OpenAI credentials in n8n.
  • Attach them to the OpenAI Chat Model node.
  • You can modify the prompt in the AI Agent node to fit your company’s style.

✨ Customization Tips

  • Update the AI prompt with your brand’s tone of voice (friendly, formal, playful, etc.).
  • Adjust the HTML email design inside the prompt (button colors, footer, etc.).
  • Add extra guard conditions (e.g., only trigger if invoice_amount > 0).
  • Change the sending service: replace Postmark with Gmail, SMTP, or another provider.
  • 💬 Or talk to our Billing Recovery Experts at flycode.com for hands-on help.

✅ Outcome

Whenever a customer’s subscription payment fails, this workflow:

  • Detects it instantly via Stripe
  • Generates a polite but urgent recovery email
  • Sends it automatically via Postmark

Result: Fewer cancellations, higher recovered revenue, and a smoother customer experience. 💸💌

Recover Failed Stripe Payments with AI Emails

This n8n workflow automates the process of identifying failed Stripe payments and sending personalized recovery emails using AI. It helps businesses reduce churn by proactively engaging customers with delinquent payments.

What it does

  1. Receives Webhook: Listens for incoming webhook events, typically from Stripe, signaling a failed payment.
  2. Filters Events: Checks if the received event is specifically a invoice.payment_failed event.
  3. Extracts Customer Data: If it's a failed payment, it makes an HTTP request to the Stripe API to retrieve detailed customer and invoice information.
  4. Generates AI Email: Uses an AI agent (powered by an OpenAI Chat Model) to craft a personalized email to the customer, informing them about the failed payment and providing instructions for recovery.
  5. Processes Email: A Code node formats the AI-generated email content for further use (e.g., sending via an email service).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Stripe Account: A Stripe account with webhook configured to send invoice.payment_failed events to the n8n webhook URL.
  • Stripe API Key: A Stripe API key with permissions to read customer and invoice data. This will be used in the "HTTP Request" node.
  • OpenAI API Key: An OpenAI API key for the AI Agent to generate email content. This will be configured in the "OpenAI Chat Model" node.
  • Email Sending Service: (Implicit) While the workflow generates the email, you would need to connect an email sending service (e.g., SendGrid, Gmail, Outlook) after the "Code" node to actually dispatch the email.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" to create a new workflow.
    • Go to the "Workflows" menu, click the three dots next to "New", and select "Import from JSON".
    • Paste the JSON and click "Import".
  2. Configure Webhook:
    • Activate the "Webhook" node.
    • Copy the "Webhook URL" provided by n8n.
    • In your Stripe dashboard, navigate to "Developers" -> "Webhooks".
    • Add a new endpoint and paste the n8n Webhook URL.
    • Select invoice.payment_failed as the event to send.
  3. Configure Stripe API Key:
    • In the "HTTP Request" node, add your Stripe API key as an authentication header or parameter as required by Stripe's API documentation. The current setup implies a direct API call to Stripe to fetch customer details.
  4. Configure OpenAI API Key:
    • In the "OpenAI Chat Model" node, configure your OpenAI API key. This is typically done via an n8n credential.
  5. Review and Customize:
    • AI Agent Prompt: Review the prompt in the "AI Agent" node to ensure the email generation aligns with your brand voice and recovery strategy.
    • Code Node: The "Code" node currently processes the AI-generated email. You might need to adjust this script based on the specific email sending service you plan to integrate.
    • Email Sending: Add an email sending node (e.g., "SendGrid", "Gmail", "Outlook") after the "Code" node to send the generated email to the customer.
  6. Activate the Workflow: Once all configurations are complete, activate the workflow.

Now, whenever a Stripe payment fails, this workflow will automatically generate and prepare a personalized recovery email for your customer.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942