Send Stripe purchase templates from Google Drive via Gmail and Discord

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Who it's for This workflow is for indie creators, automation agencies, and digital product sellers who sell n8n workflow templates (or any downloadable file) through Stripe and want to automate pos...

Best for

Content Creation automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatanthropic, n8n-nodes-base.code, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.httprequest, n8n-nodes-base.formtrigger

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Send Stripe purchase templates from Google Drive via Gmail and Discord
Workflow name: Send Stripe purchase templates from Google Drive via Gmail and Discord

Who it's for

This workflow is for indie creators, automation agencies, and digital product sellers who sell n8n workflow templates (or any downloadable file) through Stripe and want to automate post-purchase delivery and team notifications.

How it works

The Stripe Trigger fires when a checkout.session.completed event is detected — a payment has been completed.
An HTTP Request node fetches the full line items from the Stripe Checkout Session using the Stripe API.
In parallel, a Discord notification is sent to a dedicated channel with the customer's name, email, product name, and amount paid.
Simultaneously, Google Drive is searched for a document template whose name matches the purchased product description.
The matching template file is downloaded from Google Drive.
A branded HTML email is sent to the customer via Gmail, with the downloaded template attached as a .json file.

How to set up

Connect your Stripe API credentials to both the Stripe Trigger and HTTP Request nodes
Configure the Discord bot credential and set the target guild and channel IDs
Connect a Google OAuth2 credential with Drive read access to both Google Drive nodes
Set the Google Drive folder ID where your templates are stored
Connect a Gmail OAuth2 credential to the Gmail node

Requirements

Stripe account with API key
Discord bot with permissions to post in a channel
Google Drive with template files named after your products
Gmail account with OAuth2 access

How to customize

Adapt the Discord message to include additional order details such as coupon codes or quantity.
Replace the Gmail step with another email provider (SendGrid, SMTP) for higher sending volumes.
Add a Google Sheets logging step after the Stripe trigger to keep a record of all purchases.

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 Note13

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

Block 2 - Sticky Note16

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

Block 3 - Sticky Note

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

Block 4 - Sticky Note1

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

Block 5 - Sticky Note2

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

Block 6 - Sticky Note3

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

Block 7 - Sticky Note4

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

Block 8 - Sticky Note5

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

Block 9 - Sticky Note6

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

Block 10 - Workflow Generator Agent

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 11 - Claude Model for Generator

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 12 - Parse and Validate JSON

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

Block 13 - Set Workflow Config Variables

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 14 - Logical Groups Agent

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 15 - Claude Model for Groups

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 16 - Groups Structured Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 17 - Parse Nodes for Renaming

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

Block 18 - Node Renaming Agent

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 19 - Claude Model for Renaming

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 20 - Renaming Structured Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 21 - Prepare and Parse Grid Data

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

Block 22 - Calculate Layout and Stickies

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

Block 23 - Apply Node Renames

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

Block 24 - Create Workflow via n8n API

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

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

3. Summary Table

Workflow	Send Stripe purchase templates from Google Drive via Gmail and Discord
Complexity	advanced
Nodes	29
Categories	Content Creation
Author	Allan Vaccarizi
Published	19 May 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15812/15812.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Content Creation workflows

Frequently asked questions

What does Send Stripe purchase templates from Google Drive via Gmail and Discord do?

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 Content Creation use case.

Allan Vaccarizi

39 workflows

Nodes

n8n-nodes-base.stickynote @n8n/n8n-nodes-langchain.agent @n8n/n8n-nodes-langchain.lmchatanthropic n8n-nodes-base.code n8n-nodes-base.set @n8n/n8n-nodes-langchain.outputparserstructured n8n-nodes-base.httprequest n8n-nodes-base.formtrigger

Complexity

advanced

Published 19 May 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15812/15812.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Send daily LinkedIn post drafts with Tavily, Groq Llama 3.3 and Gmail

## Quick overview This workflow runs daily at 8 AM to rotate through a topic list, research it with Tavily web search, generate a LinkedIn post and image prompt with Groq (Llama 3.3 70B), create a Pollinations.ai image URL, and email you the post with the image attached via Gmail. ## How it works 1. Runs every day at 8:00 AM on a schedule. 2. Selects today’s topic from a rotating list based on the day of the year. 3. Searches the web with Tavily to fetch up-to-date results for the selected topic. 4. Uses a Groq-hosted Llama model to write a LinkedIn post and a matching image prompt grounded in the Tavily results. 5. Builds a Pollinations.ai image generation URL from the image prompt and downloads the generated image file. 6. Emails the post text with the image attached via Gmail, and sends a text-only fallback email if image generation or download fails. ## Setup 1. Add a Groq API credential to the Groq Chat Model node. 2. Create a Tavily API key and configure HTTP Header Auth with `Authorization: Bearer <YOUR_TAVILY_KEY>` for the Tavily Search request. 3. Connect a Gmail OAuth2 credential and update the recipient email address in both Gmail send steps. 4. Edit the topic list in the topic-selection code step if you want different rotating themes. ## Requirements - Groq API key (free tier available) - Tavily API key (free tier — 1,000 searches/month) - Gmail account (OAuth2) ## Customization - Edit the topic list inside the "Pick Today's Topic" code node to change what subjects the post rotates through. - Change the Groq model in the "Groq Chat Model" node if you want a different LLM (e.g. a smaller/faster or larger Groq model). - Adjust the schedule trigger if you want a different posting time, or swap the Gmail "send to" address to deliver the draft to someone else for review. ## Additional info This workflow emails you a draft for manual review before posting — it does not post to LinkedIn automatically. If image generation fails, a text-only fallback email is sent instead so you never miss the post text.

View

Generate VEO3 videos from form ideas with ChatGPT, fal.ai, Drive and Gmail

## Quick overview This workflow collects a video idea via an n8n Form, uses OpenAI to turn it into an optimized prompt, generates an 8-second VEO3 video with native audio via fal.ai, saves the MP4 to Google Drive, and emails the Drive link via Gmail. ## How it works 1. Receives a submission from an n8n Form with the requester’s email, a plain-English video idea, and a selected style. 2. Uses OpenAI (via an AI Agent) to convert the idea and style into a structured VEO3 title and detailed prompt returned as JSON. 3. Cleans and parses the AI JSON, creates a filename-safe title, and sets the generation parameters to 16:9 and 8 seconds. 4. Submits the prompt to fal.ai’s queue endpoint for the fal-ai/veo3 model and gets a request ID. 5. Polls fal.ai every 30 seconds until the job status returns COMPLETED. 6. Retrieves the final MP4 URL from fal.ai, downloads the video, uploads it to Google Drive, and emails the Google Drive web link to the requester via Gmail. ## Setup 1. Create a fal.ai account, generate an API key, and replace `YOUR_FAL_AI_API_KEY` in the fal.ai HTTP request headers. 2. Add an OpenAI API credential in the OpenAI Chat Model node and select the model you want to use. 3. Connect Google Drive OAuth2 and replace `YOUR_GDRIVE_FOLDER_ID` with the target folder ID where videos should be saved. 4. Connect Gmail OAuth2 for sending emails, then activate the workflow and use the Form URL (path `veo3-video-generator`) to submit requests.

View

Generate presentation decks from prompts with Encelade

## Quick overview This workflow starts a presentation generation job in Encelade from a prompt and outline hints, polls Encelade for completion, and outputs the finished deck link (or stops with an error if generation fails). ## How it works 1. Starts when you manually execute the workflow in n8n. 2. Sends the topic, slide count, audience, tone, theme settings, and outline hints to Encelade to generate a 6-slide presentation. 3. Waits 20 seconds and then checks the Encelade session status using the returned session ID. 4. If the session phase is not finished, it keeps waiting and rechecking until the phase changes. 5. When the phase is "done", it returns the generated deck link and project PID. 6. When the phase is "failed", it stops the workflow and raises an error with the failure details. ## Setup 1. Install and configure Encelade credentials in n8n for the Encelade node. 2. Update the generation inputs (topic, page count, outline hints, audience/tone, theme mode, and media provider) to match the deck you want to create. 3. Ensure the workflow has enough time to complete by adjusting the 20-second wait interval if your Encelade generations typically take longer.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Send Stripe purchase templates from Google Drive via Gmail and Discord

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Who it's for

How it works

How to set up

Requirements

How to customize

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Sticky Note13

Block 2 - Sticky Note16

Block 3 - Sticky Note

Block 4 - Sticky Note1

Block 5 - Sticky Note2

Block 6 - Sticky Note3

Block 7 - Sticky Note4

Block 8 - Sticky Note5

Block 9 - Sticky Note6

Block 10 - Workflow Generator Agent

Block 11 - Claude Model for Generator

Block 12 - Parse and Validate JSON

Block 13 - Set Workflow Config Variables

Block 14 - Logical Groups Agent

Block 15 - Claude Model for Groups

Block 16 - Groups Structured Parser

Block 17 - Parse Nodes for Renaming

Block 18 - Node Renaming Agent

Block 19 - Claude Model for Renaming

Block 20 - Renaming Structured Parser

Block 21 - Prepare and Parse Grid Data

Block 22 - Calculate Layout and Stickies

Block 23 - Apply Node Renames

Block 24 - Create Workflow via n8n API

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions