Back to Catalog

Automated template delivery system with Stripe, GPT-4o & Gmail

Rahul JoshiRahul Joshi
690 views
2/3/2026
Official Page

๐Ÿ“Š Description

Automate post-purchase workflows by instantly fetching successful Stripe payments, matching them to corresponding automation templates in Google Sheets, and sending customers personalized access emails using AI-generated content. This system ensures each buyer receives their digital template, password, and onboarding details automatically after payment. ๐Ÿ’ณ๐Ÿ“ฉ๐Ÿค–

What This Template Does

  • Step 1: Triggers daily at 7:00 AM IST to fetch all successful payment charges from Stripe. โฐ
  • Step 2: Retrieves payment intent and product details for each successful charge to enrich context. ๐Ÿ’ฐ
  • Step 3: Validates required fields (order reference, product name, customer name, email). โœ…
  • Step 4: Matches purchased product with the automation record in Google Sheets via AI lookup. ๐Ÿ”
  • Step 5: Combines Stripe and Sheet data into one record, ensuring accuracy and completeness. ๐Ÿ”„
  • Step 6: Filters out already-processed customers to avoid duplicate sends. ๐Ÿงฎ
  • Step 7: Generates a personalized thank-you email using Azure OpenAI (GPT-4o-mini) including access links, password, and onboarding tips. ๐Ÿ’Œ
  • Step 8: Sends the email through Gmail to the customer automatically. ๐Ÿ“ง
  • Step 9: Logs each transaction and email delivery into Google Sheets for tracking and auditing. ๐Ÿ“Š

Key Benefits

โœ… Fully automated Stripe-to-email delivery flow โœ… Zero manual intervention โ€” instant template delivery โœ… AI-personalized HTML emails with customer details โœ… Centralized purchase logging and analytics โœ… Eliminates duplicates and ensures smooth customer experience

Features

  • Scheduled daily trigger (7:00 AM IST)
  • Stripe API integration for payment and product details
  • Google Sheets lookup for automation files and passwords
  • GPT-powered email content generation
  • Gmail API integration for delivery
  • Google Sheets logging for audit trail

Requirements

  • Stripe API credentials
  • Google Sheets OAuth2 credentials
  • Gmail OAuth2 credentials
  • Azure OpenAI API credentials

Target Audience

  • SaaS or digital product sellers using Stripe
  • Automation template marketplaces
  • Small teams delivering digital assets via email
  • Businesses seeking instant customer fulfillment

n8n Automated Template Delivery System with Stripe, GPT-4o, and Gmail

This n8n workflow automates the delivery of personalized templates to customers upon successful Stripe payments. It leverages AI (GPT-4o via Azure OpenAI) to generate custom content based on customer data and then sends this content as an email via Gmail.

What it does

This workflow simplifies the process of delivering digital products or personalized content after a purchase, ensuring a seamless and automated customer experience.

  1. Triggers on a Schedule: The workflow is set to run periodically to check for new Stripe payments.
  2. Fetches Stripe Payments: It retrieves recent successful payments from Stripe.
  3. Filters for New Payments: It checks if a payment has already been processed by comparing it against a Google Sheet of processed orders.
  4. Generates Personalized Content (AI Agent): For each new payment, an AI Agent (using Azure OpenAI Chat Model) generates a personalized template or message based on the customer's purchase details.
  5. Parses AI Output: A Structured Output Parser extracts the relevant information from the AI Agent's response.
  6. Sends Personalized Email: The generated content is then used to send a personalized email to the customer via Gmail.
  7. Records Processed Orders: The details of the processed order are added to a Google Sheet to prevent duplicate processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Account: A running instance of n8n.
  • Stripe Account: Configured with a webhook or API access to fetch payment data.
  • Azure OpenAI Account: With access to a GPT-4o (or similar) chat model.
  • Gmail Account: To send personalized emails.
  • Google Sheets Account: To maintain a record of processed orders.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Stripe: Set up your Stripe API credentials.
    • Azure OpenAI: Configure your Azure OpenAI Chat Model credentials, including API key, endpoint, and model name (e.g., gpt-4o).
    • Gmail: Set up your Gmail OAuth 2.0 credentials.
    • Google Sheets: Configure your Google Sheets OAuth 2.0 credentials.
  3. Configure Google Sheets Node (ID: 18):
    • Specify the Spreadsheet ID and Sheet Name where processed orders will be recorded.
    • Ensure the sheet has columns for relevant order details (e.g., Stripe Payment ID, Customer Email, Template Sent Date).
  4. Configure Stripe Node (ID: 499):
    • Set the Operation to retrieve payments.
    • Adjust the Limit and Date Range as needed for your polling interval.
  5. Configure AI Agent Node (ID: 1119):
    • Select the Azure OpenAI Chat Model (ID: 1253) as the Language Model.
    • Provide a clear System Message and User Message to guide the AI in generating the desired template content. The user message should include dynamic data from the Stripe payment (e.g., {{ $json.data.customer_details.email }} or {{ $json.data.amount_total }}).
    • Define the Tools the AI Agent can use if necessary (though none are explicitly configured in this basic structure).
  6. Configure Structured Output Parser Node (ID: 1179):
    • Define the Schema for the expected JSON output from the AI Agent (e.g., { "subject": "string", "body": "string" }).
  7. Configure Gmail Node (ID: 356):
    • Set the Recipient Email using an expression like {{ $json.customer_email }} from the parsed AI output or Stripe data.
    • Set the Subject and Body of the email using expressions from the Structured Output Parser's output (e.g., {{ $json.subject }} and {{ $json.body }}).
  8. Activate the Workflow: Enable the workflow to start running on its defined schedule.

Make sure to test the workflow thoroughly with test payments in Stripe before deploying it to a production environment.

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch ๐Ÿ”— LinkedIn โ€“ Wessel Bulte

Wessel BulteBy Wessel Bulte
247