HumationHuman + Automation
Back to Catalog

Automate digital product delivery & sales tracking with Stripe, Email, Notion & Telegram

Shelly-Ann DavyShelly-Ann Davy
82 views
2/3/2026
AirtableInventory ManagementShopifyE-commerceData Sync
Official Page

Overview

This workflow automates the end-to-end delivery of digital products after a successful Stripe checkout. It eliminates manual fulfillment, keeps a structured sales log in Notion, and optionally notifies you in Telegram.

It’s designed for template sellers, coaches, course creators, and micro-SaaS owners who want to professionalize their delivery process without custom code.

Workflow Logic

Webhook Trigger (Stripe)

Listens for the checkout.session.completed event.

Path: /stripe-webhook

Method: POST

Response Mode: onReceived

HTTP Request – Get Checkout Session

Fetches full session details from Stripe API.

URL: https://api.stripe.com/v1/checkout/sessions/{{$json.body.data.object.id}}

Authentication: Header Auth (Authorization: Bearer YOUR_STRIPE_SECRET_KEY)

IF Node – Check Product

Evaluates line_items.data[0].description from Stripe response.

Routes flow depending on which product was purchased (e.g., Notion Template A vs Notion Template B).

Email Send Nodes

Sends product delivery emails with personalized greeting and download link.

To: {{$json.customer_details.email}}

Subject: Your Elegant Template is Ready ✨

Body text includes product-specific link.

Notion Node – Log Sale

Creates a page in your Sales Log database.

Properties:

Name → {{$json.customer_details.name}}

Email → {{$json.customer_details.email}}

Product → {{$json.line_items.data[0].description}}

Date → {{$now}}

Status → Delivered

Telegram Notify Node (Optional)

Sends you a private message:

💸 New Sale!
Product: {{ $json.line_items.data[0].description }}
Buyer: {{ $json.customer_details.name }}

Requires YOUR_TELEGRAM_CHAT_ID and bot token.

Node List

Webhook (Stripe)

HTTP Request (Stripe API)

IF (Check Product)

Email Send (Product Delivery)

Notion (Create Page)

Telegram (Send Message)

Setup Instructions

Stripe:

Create a webhook endpoint in your Stripe dashboard.

Subscribe to checkout.session.completed.

Add your secret key into the HTTP Request node (YOUR_STRIPE_SECRET_KEY).

Notion:

Create a Sales Log database.

Share with your Notion API integration.

Replace YOUR_NOTION_DATABASE_ID with the correct ID.

Email:

Configure SMTP credentials or Gmail OAuth in the Email Send node.

Update sender email (fromEmail).

Telegram (Optional):

Create a bot with BotFather.

Get your chat ID.

Add your token and YOUR_TELEGRAM_CHAT_ID in the node.

Why It’s Gallery-Ready

✅ Clear business use case (digital delivery, sales tracking).

✅ Proper variable usage ($json syntax, no hardcoded customer data).

✅ No exposed API keys (placeholders provided).

✅ Markdown-based documentation with H2 headings.

✅ Broad but specific: works for any digital seller (Notion, PDFs, Canva, courses).

Example Use Cases

Auto-deliver Notion templates or digital kits after Stripe checkout.

Log all sales in a Notion database for tracking/reporting.

Send instant Telegram notifications so you never miss a new customer.

Replace manual fulfillment with a professional automation pipeline.

✨ With this workflow, you’ll never have to manually email files again. Customers are delighted with instant delivery, your sales records stay organized, and you gain real-time visibility on every transaction.

n8n Automated Digital Product Delivery & Sales Tracking

This n8n workflow automates the process of digital product delivery and sales tracking by integrating Stripe, email, Notion, and Telegram. It acts as a backend system to manage customer notifications, internal tracking, and sales record-keeping upon a successful purchase.

What it does

This workflow is designed to streamline the post-purchase experience for digital products. Here's a step-by-step breakdown:

  1. Receives Stripe Webhook: The workflow is triggered by a webhook, presumably from Stripe, indicating a successful payment or a new sale.
  2. Conditional Processing: It includes an "If" node, suggesting that it might filter or branch based on certain conditions of the incoming data (e.g., product type, payment status).
  3. Sends Confirmation Email: Upon a successful transaction, it sends an email to the customer, likely containing the digital product, download links, or further instructions.
  4. Records Sale in Notion: It interacts with Notion, presumably to add a new entry to a database for sales tracking, customer management, or order fulfillment.
  5. Notifies via Telegram: It sends a notification to a Telegram chat, which could be used for internal team alerts about new sales, order details, or daily summaries.
  6. Makes HTTP Request: An HTTP Request node is included, which could be used for various purposes such as updating an external CRM, triggering another service, or logging data to a custom endpoint.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Stripe Account: Configured to send webhooks to the n8n webhook URL.
  • Email Sending Service: SMTP credentials configured in n8n for sending emails.
  • Notion Account: With a database set up to receive sales data, and an n8n Notion credential configured.
  • Telegram Account: A Telegram bot and chat ID for sending notifications, with an n8n Telegram credential configured.
  • HTTP Request Endpoint (Optional): If the HTTP Request node is used, an external API or service endpoint to send data to.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your Email (SMTP) credentials for the "Send Email" node.
    • Set up your Notion credentials for the "Notion" node, ensuring it has access to the relevant database.
    • Set up your Telegram credentials for the "Telegram" node, including your bot token and the target chat ID.
  3. Configure Webhook:
    • Activate the "Webhook" trigger node in n8n.
    • Copy the generated webhook URL.
    • Go to your Stripe account settings and configure a new webhook endpoint, pointing it to the n8n webhook URL. Ensure it listens for relevant events like checkout.session.completed or payment_intent.succeeded.
  4. Configure "If" Node: Adjust the conditions in the "If" node to match your specific business logic for filtering or routing sales data.
  5. Configure "Send Email" Node: Customize the email subject, body, and recipient based on the incoming Stripe data.
  6. Configure "Notion" Node: Map the incoming Stripe data fields to the properties of your Notion database.
  7. Configure "Telegram" Node: Customize the message content for Telegram notifications.
  8. Configure "HTTP Request" Node (Optional): If used, configure the URL, method, headers, and body for your external API call.
  9. Activate the Workflow: Once all configurations are complete, activate the workflow in n8n.

This workflow provides a robust foundation for automating your digital product delivery and sales tracking, reducing manual effort and ensuring timely communication and record-keeping.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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