Workflow Templates

Convert PDF Articles to Podcast Workflow Name: Convert PDF Articles to Podcast Author: Devjothi Dutta Category: Productivity, Content Creation, Automation Complexity: Medium Setup Time: 45-60 minutes 📖 Description Transform any PDF article, research paper, or document into a high-quality audio podcast automatically. This workflow extracts text from PDFs, converts it to natural-sounding speech using Google Cloud Text-to-Speech, stores the audio files in cloud storage, and generates an RSS feed compatible with all major podcast apps (Apple Podcasts, Spotify, Pocket Casts, etc.). Perfect for consuming long-form content while commuting, exercising, or multitasking. Turn your reading list into a personal podcast feed. 👥 Who's it for For Professionals: Convert industry reports and whitepapers to audio Listen to research papers during commutes Stay updated with long-form articles hands-free For Students: Turn textbooks and study materials into audio Create audio versions of lecture notes Study while exercising or commuting For Content Creators: Repurpose written content into audio format Create podcast episodes from blog posts Reach audio-focused audiences For Busy Readers: Convert saved articles to a personal podcast Listen to newsletters and essays on the go Build a private audio library ✨ Key Features 📄 PDF Text Extraction** - Automatically extracts text from any PDF file 🎙️ Natural Voice Synthesis** - High-quality WaveNet voices from Google Cloud TTS ☁️ Cloud Storage** - Files hosted on Cloudflare R2 (S3-compatible) with public URLs 📻 RSS Feed Generation** - Full iTunes-compatible podcast feed with metadata 📧 Email Notifications** - Instant alerts when new episodes are ready 🎨 Custom Branding** - Configurable podcast name, artwork, and descriptions ⚙️ Modular Configuration** - Easy-to-update centralized config node 🔄 Automated Workflow** - Set it and forget it - fully automated pipeline 🛠️ Requirements Required Services: n8n (self-hosted or cloud) - Workflow automation platform Google Cloud Platform - Text-to-Speech API access Free tier: 1 million characters/month (WaveNet voices) Paid: $16 per 1 million characters Cloudflare R2 - Object storage for audio files and RSS feed Free tier: 10GB storage, unlimited egress Email Service - SMTP or email service for notifications Required Community Nodes: Cloudflare R2 Storage** (n8n-nodes-cloudflare-r2-storage) Install via: Settings → Community Nodes → Install Search for: n8n-nodes-cloudflare-r2-storage Important: Install this BEFORE importing the workflow Optional: Custom domain for podcast feed URLs Podcast artwork (3000x3000px recommended) 📦 What's Included This workflow package includes: Complete n8n workflow JSON (ready to import) Comprehensive setup guide Architecture documentation Configuration templates Credentials setup instructions Testing and validation checklist RSS feed customization guide Troubleshooting documentation 🚀 Quick Start Install community node (required): Go to Settings → Community Nodes → Install Search for: n8n-nodes-cloudflare-r2-storage Click Install and wait for completion Import workflow into your n8n instance Configure credentials: Google Cloud TTS API key Cloudflare R2 credentials (Access Key ID + Secret) SMTP email credentials Update Workflow Config node with your settings: R2 bucket name and public URL Podcast name and description Artwork URL Email recipient Test with a sample PDF to verify setup Add RSS feed URL to your podcast app 📊 Workflow Stats Nodes:** 10 Complexity:** Medium Execution Time:** ~2-5 minutes per PDF (depends on length) Monthly Cost:** $0-20 (depending on usage and free tiers) Maintenance:** Minimal (set and forget) 🎨 Customization Options Change TTS voice (20+ English voices available) Adjust speech speed and pitch Customize RSS feed metadata Add custom intro/outro audio Configure file retention policies Set up webhook triggers for remote submission 🔧 How it Works User uploads PDF to n8n Text is extracted from PDF Text is sent to Google TTS API Audio file (.mp3) is generated Files uploaded to R2 storage: Original PDF Generated MP3 audio RSS feed is generated/updated with: Episode title (from PDF filename) Audio URL Duration and file size Publication date Rich HTML description RSS feed uploaded to R2 Email notification sent with episode details 💡 Pro Tips Voice Selection:** Test different WaveNet voices to find your preferred style Batch Processing:** Process multiple PDFs by running workflow multiple times Quality vs Cost:** WaveNet voices sound better but cost more than Standard voices Storage Management:** Set up R2 lifecycle rules to auto-delete old episodes Custom Domains:** Use Cloudflare for custom podcast feed URLs 🔗 Related Workflows PDF to Email Summary Document Translation to Audio Blog RSS to Podcast Multi-language Audio Generation 📧 Support & Feedback For questions, issues, or feature requests: GitHub: PDF-to-Podcast---N8N Repository n8n Community Forum: Tag @devdutta Email: devjothi@gmail.com 📄 License MIT License - Free to use, modify, and distribute ⭐ If you find this workflow useful, please share your feedback and star the workflow!

This n8n template demonstrates how to automate the followup when your customer completes a checkout in Stripe by emailing a receipt, logging the transaction, and sending an internal notification. See the video. Who it's for This workflow is for small to medium sized organizations using Stripe for payment processing and looking for a simple way to automate communication and logging that needs to happen post-checkout. How it works The workflow is triggered when a Stripe checkout is completed and again when Stripe creates an invoice. Checkout and invoice details are logged to a Google Sheet. A Slack message is sent to a channel where RevOps receive notifications about new sales. Lastly, a personalized email is sent to the customer with a link for downloading their receipt. How to set up Edit the two Stripe trigger nodes to enter your credentials. Create a Google Sheet named Payments with two tabs: transactions and invoices and the columns as shown in this example. Edit the three Google Sheets nodes to enter your credentials. The Gmail node also needs the credentials of the account that you want emails to come from. Lastly, enter credentials into the Slack node for the user that you want to be shown as posting Stripe transaction notifications. The Slack node is configured to send notifications to the revops channel, but you can change that to be whatever channel you want to use. Use your Stripe sandbox to test the workflow. In your sandbox, create a payment link that you can use to create the checkouts that will trigger the workflow. Make sure that your payment link has the option checked to create a post-payment invoice PDF. This will trigger the Invoice Created node. Requirements Stripe Account Google Workspace Account (Sheets, Mail) Slack Account

Outlook Inbox Tamer: AI-Powered Categorization, Auto Replies & Team Alerts This workflow automatically classifies and routes incoming Outlook emails into smart categories using n8n + OpenAI GPT-4.1-mini. It helps professionals and teams stay organized by intelligently sorting and responding to high-priority messages, customer support emails, promotions, and finance-related messages — all without manual effort. 🧠 Who’s It For Professionals or teams overwhelmed by email volume. Customer support, operations, or finance teams needing real-time triage. Anyone who wants AI to help manage and prioritize their Outlook inbox. ⚙️ How It Works Microsoft Outlook Trigger monitors your inbox for new emails. OpenAI GPT-4.1-mini analyzes each email and classifies it as one of: High_Priority Customer_Support Promotions Finance/Billing Routing node moves emails to matching Outlook folders. AI-generated replies and Telegram notifications keep the right team informed instantly. (Optional) Use Google Sheets + Manual Trigger to test with sample data before going live. 🛠️ Requirements Outlook account connected via Microsoft Outlook OAuth2. OpenAI API key** (set up in n8n credentials). (Optional) Telegram bot token for team alerts. (Optional) Google Sheets for test emails. 🔧 How to Set Up Import the workflow into your n8n instance. Add credentials for: Microsoft Outlook OpenAI Telegram (optional) Deploy and activate the workflow. Start sending or receiving emails — watch them get auto-classified and organized! 🧩 How to Customize Update the system prompt in the Email_Classifier_Agent to add more categories (like HR, Legal, etc.). Change Telegram recipients for alerts. Extend the workflow to post classified data into Notion, Slack, or CRM. 📘 Example Use Case An AI agent monitors your Outlook inbox, classifies incoming emails in real time, moves them to their respective folders, creates response drafts, and alerts your team instantly through Telegram. 💬 Connect with the Creator 👋 Created by Sandeep Patharkar 💼 Connect on LinkedIn 🌐 Join my Skool community for n8n + AI automation tutorials, live Q&As, and exclusive workflow templates. Category: Email Automation / AI Productivity Difficulty: Intermediate Estimated Setup Time: ⏱️ 10–15 minutes

Description This workflow automates the tracking and follow-up process for pending payments. It pulls lead payment data from Google Sheets, checks whether the status is “Open,” and then routes actions accordingly. For open payment cases, it creates a dedicated ClickUp task and sends an email confirmation to stakeholders. For non-open cases, it notifies the team via Slack. This ensures payment verifications are never missed, while keeping all updates transparent and centralized. What This Template Does (Step-by-Step) 📊 Fetch Lead Data from Google Sheets Retrieves lead records including: Lead Name Company Name Payment Verification Status Status (Open/Closed) ⚖️ Check if Status = Open ✅ TRUE (Open): Creates a ClickUp task and sends an email confirmation. ❌ FALSE (Not Open): Sends a Slack notification only. 🗂 Create ClickUp Task for Payment Verification: Adds a task with lead and company details for pending payment follow-up in the specified list. ✉️ Send Email Confirmation: Notifies the assigned watcher (via Gmail) with task details (name, ID, and link). 💬 Send Slack Notification: Alerts the Slack workspace if a lead’s status is not “Open,” providing visibility on non-actionable cases. Prerequisites Google Sheet with lead/payment data ClickUp account & API credentials Gmail API credentials Slack API credentials n8n instance (cloud or self-hosted) Step-by-Step Setup Connect Google Sheets → Fetch payment verification data. Apply Status Filter (If Node) → Route based on “Open” status. Open Status → Create ClickUp Task → Send Email confirmation. Not Open Status → Send Slack notification. Customization Ideas 🎯 Add additional filtering (e.g., only create tasks if payment verification = “Pending”). 📢 Send Slack alerts for all new leads, not just closed ones. 📚 Log completed payment verifications into Airtable or Notion for reporting. 💡 Include payment due dates or invoice numbers in ClickUp task details. Key Benefits ✅ Automates payment follow-up process ✅ Keeps stakeholders informed via email ✅ Provides real-time Slack alerts for non-actionable cases ✅ Centralizes pending payment tasks in ClickUp ✅ Reduces manual monitoring and ensures no pending case is missed Perfect For 👥 Finance teams handling multiple payment verifications 🏢 Companies wanting a transparent and automated payment tracking process 🎯 Teams already using ClickUp for task management 📊 Managers who need visibility into pending vs. closed payment statuses

Description This workflow sends an instant email alert when a task in a Google Sheet is marked as Urgent, and then sends a Telegram reminder notification after 2 hours if the task still hasn’t been updated. Then a Jira ticket is created so the task enters in the formal workflow and another Telegram message is sent with the details of the issue created. It helps teams avoid missed deadlines and ensures urgent tasks get attention — without requiring anyone to refresh or monitor the sheet manually. Context In shared task lists, urgent items can be overlooked if team members aren't actively checking the spreadsheet. This workflow solves that by: Sending an email as soon as a task becomes Urgent Waiting 2 hours Checking if the task is still open Sending a Telegram reminder only if action has not been taken Creating a Jira issue Sending a Telegram message with the details of the issue created This prevents both silence and spam, creating a smart and reliable alert system. Target Users Project Managers using Google Sheets Team leads managing shared task boards Remote teams needing lightweight coordination Anyone who wants escalation notifications without complex systems Technical Requirements Google Sheets credential Gmail credential Telegram Bot + Chat ID Google Sheet with a column named Priority Jira credential Workflow Steps Trigger: Google Sheets Trigger (on update in the “Priority” column) IF Node – Checks if Priority = Urgent Send Email – Sends alert email with task name, owner, status, deadline Mark Notified = Yes in the sheet Wait 2 hours IF Status is still not resolved Send Telegram reminder create an Issue on Jira based on the information provided Send Telegram message with the details of the ticket Key Features Real-time alerts on critical tasks Simple logic (no code required) Custom email body with dynamic fields Works on any Google Sheet with a “Priority” column Telegram notification ensures the task doesn’t get forgotten Expected Output Personalized email alert when a task is marked as "Urgent" Email includes task info: title, owner, deadline, status, next step Telegram message after 2 hours if the task is still open Automatic creation of a Jira issue with the higgest priority Telegram message to notify about the new Jira ticket How it works Trigger: Watches for “Priority” updates 🔍 Check: If Priority = Urgent AND Notified is empty 📧 Email: Sends a personalized alert ✏️ Sheet Update: Marks the task as already notified ⏳ Wait: 2-hour delay 🤖 Check Again: If Status hasn’t changed → send Telegram reminder, create Jira ticket and send the details. Tutorial video: Watch the Youtube Tutorial video About me : I'm Yassin, IT Project Manager, Agile & Data specialist. Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

How it Works This automated workflow transforms Zoom meeting emails into professional summaries and Google Docs. It monitors your Gmail for Zoom meeting notification emails, extracts meeting content using AI-powered analysis, and generates both email-safe HTML summaries and Google Docs-compatible text. The workflow intelligently parse meeting transcripts, creating structured summaries with attendee lists, key discussion points, action items, and next steps. It automatically creates Google Docs for record-keeping and sends formatted email summaries to meeting participants. Who is it For Perfect for project managers, team leads, executives, and meeting coordinators who regularly conduct Zoom meetings and need consistent, professional documentation. Ideal for organizations that require structured meeting records, action item tracking, and seamless integration between communication tools. Especially valuable for distributed teams, consulting firms, and corporate environments where meeting accountability and follow-up are critical. Benefits for Using this Workflow Time Savings**: Eliminates 30-60 minutes of manual meeting summary creation per meeting. Professional Consistency**: Ensures all meeting summaries follow the same structured format with headers, attendees, discussion points, and action items. Automated Documentation**: Creates searchable Google Docs archives and distributes summaries without manual intervention. Enhanced Accountability**: Clear action item tracking with assignees and deadlines improves follow-through. Multi-Format Output**: Provides both email-friendly HTML and plain text formats for maximum compatibility across different platforms and systems. Setup Requirements Prerequisites**: Active n8n instance, Gmail account, Google Docs access, OpenAI API key. Required Credentials**: Configure Gmail OAuth2 for both trigger and sending, Google Docs OAuth2 for document creation, OpenAI API for GPT-4 processing. Configuration Steps**: 1) Import workflow and activate Gmail trigger with filter for Zoom meeting emails, 2) Set up Google Drive folder permissions for document creation, 3) Configure OpenAI credentials and verify AI agent tools connection, 4) Test workflow with a sample Zoom email to ensure proper formatting and delivery. Optional Customization**: Modify Gmail search filters, adjust Google Docs folder location, customize email templates, or fine-tune AI prompt for specific meeting formats.

This n8n workflow is designed to centralize the management and tracking of customer inquiries received through multiple channels (email and web forms). Who's it for? Customer support teams Marketing teams Sales teams Small to medium-sized businesses Individuals looking to streamline customer inquiry processes How it works / What it does This workflow is designed to automatically collect, process, route, and track customer inquiries from different sources. Multi-Channel Input: The workflow listens for inquiries from both incoming emails and web form submissions. Email Trigger: Monitors a specific inbox for sent emails. Webhook - Web Form: Listens for web form data submitted to a designated endpoint. Data Extraction and Parsing: Extract Email Content: Extracts HTML content from incoming emails to get a clean text message. Parse Email Data: Extracts relevant information from the email, such as customer name, email address, subject, message, received timestamp, source ("email"), and inquiry type (e.g., "urgent", "billing", "general") based on the subject line. Parse Webhook Data: Extracts customer name, email, subject, message, received timestamp, source ("webform"), and inquiry type from the web form data based on the provided type or a default of "general". Merge Inquiries: The parsed email and web form inquiry data are combined into a single stream for continued processing. Route by Inquiry Type: The workflow then routes the inquiries based on the extracted inquiryType. Urgent Inquiries: Inquiries marked as "urgent" are routed to a specific Slack channel for immediate alerts. General Inquiries: Inquiries marked as "general" are notified in another Slack channel. Billing Inquiries: Inquiries marked as "billing" are routed to the general inquiries channel, or can be customized for a separate channel if needed. Save to Google Sheets: All inquiry data is logged into a Google Sheet, which serves as a central repository, including details like customer name, email, subject, message, source, received timestamp, and inquiry type. Send Auto-Reply Email: Customers receive an automated email reply confirming that their inquiry has been successfully received. How to set up Google Sheets: Create a new spreadsheet in your Google Drive. Name the first sheet "Inquiries" and create the following header row: customerName, customerEmail, subject, message, source, receivedAt, inquiryType. In the 'Save to Google Sheets' node, configure the Spreadsheet ID and Sheet Name. Link your Google Sheets credentials. Email Trigger (IMAP): Set up the 'Email Trigger' node to connect to your IMAP email account. Test it to ensure it correctly listens for incoming emails before activating the workflow. Webhook - Web Form: Copy the Webhook URL from the 'Webhook - Web Form' node and configure your web form to submit data to it. Ensure your web form sends fields like name, email, subject, message, and type in JSON format. Slack: Configure your Slack credentials to connect to your Slack workspace. Update the relevant Slack Channel IDs in both the 'Notify Urgent - Slack' and 'Notify General - Slack' nodes for sending notifications for urgent and general inquiries. Gmail: Set up your Gmail credentials to connect to your Gmail account. Ensure the 'Send Auto-Reply Email' node is correctly linked to your sending Gmail account. Requirements An n8n instance A Google Sheets account An IMAP-enabled email account A Slack workspace A Gmail account A basic web form (to integrate with the Webhook node) How to customize the workflow Add more Inquiry Types: You can add more specific inquiry types (e.g., "technical support", "returns") by adding more rules in the **'Route by Inquiry Type' node. Additional Notification Channels**: To integrate other notification systems (e.g., Microsoft Teams, Discord, SMS) beyond Slack, create new routing outputs and add new notification nodes for the desired service. CRM Integration**: Instead of or in addition to saving data to Google Sheets, you can add new nodes to connect to CRM systems like Salesforce, HubSpot, or others. Prioritization and Escalation**: Implement more complex logic to trigger escalation processes or prioritization rules based on inquiry type or keywords. AI Sentiment Analysis**: Integrate an AI node to analyze the sentiment of inquiry messages and route or prioritize them accordingly. `

Create curated industry trend reports from Medium to Google Docs This workflow automates the process of market research by generating high-quality, curated digests of Medium articles for specific topics. It scrapes recent content, uses AI to filter out spam and duplicates, categorizes the stories into readable buckets, and compiles everything into a formatted Google Doc report. Target Audience Content marketers, market researchers, product managers, and investors looking to track industry trends without reading through noise. How it works Schedule: The workflow runs on a defined schedule (e.g., daily or weekly) via the Schedule Trigger. Define Source: A Set node defines the specific Medium tag URL to track (e.g., /tag/artificial-intelligence). Scrape Content: BrowserAct visits the target Medium page and scrapes the latest article titles, authors, and summaries. Analyze & Filter: An AI Agent (powered by Claude via OpenRouter) analyzes the raw feed. It removes duplicates, filters out spam/clickbait, and categorizes high-quality stories into buckets (e.g., "Must Reads," "Engineering," "Wealth"). Create Report: A Google Docs node creates a new document using the digest title generated by the AI. Build Document: The workflow loops through the analyzed items, appending headers and body text to the Google Doc section by section. Notify Team: A Slack node sends a message to your chosen channel confirming the report is ready. How to set up Configure Credentials: Connect your BrowserAct, Google Docs, Slack, and OpenRouter accounts in n8n. Prepare BrowserAct: Ensure the Automated Industry Trend Scraper & Outline Creator template is saved in your BrowserAct account. Set Target Topic: Open the Target Page node and replace the Target_Medium_Link with the Medium tag archive you wish to track (e.g., https://medium.com/tag/bitcoin/archive). Configure Notification: Open the Send a message node (Slack) and select the channel where you want to receive alerts. Activate: Turn the workflow on. Requirements BrowserAct* account with the *Automated Industry Trend Scraper & Outline Creator** template. Google Docs** account. Slack** account. OpenRouter** account (or any compatible LLM credentials). How to customize the workflow Adjust the AI Persona: Modify the system prompt in the Analyzer & Script writer node to change the categorization buckets (e.g., change "Engineering" to "Marketing Strategies"). Change the Output Destination: Replace the Google Docs nodes with Notion or Airtable nodes if you prefer a database format over a document. Add Email Delivery: Add a Gmail or Outlook node at the end to email the finished Google Doc link directly to stakeholders. Need Help? How to Find Your BrowserAct API Key & Workflow ID How to Connect n8n to BrowserAct How to Use & Customize BrowserAct Templates Workflow Guidance and Showcase Video Stop Writing Outlines! Use This AI Trend Scraper (BrowserAct + n8n + Gemini)

Who's it for Women and healthcare providers who want to automate menstrual cycle tracking with personalized AI-powered health insights delivered through multiple channels. What it does This workflow automates the complete cycle tracking process: Retrieves period and symptom data from Google Sheets every morning Analyzes patterns using OpenAI GPT to generate personalized health insights Sends daily notifications via Telegram on weekdays Creates Google Calendar reminders for upcoming cycle events Generates comprehensive weekly reports sent via email on weekends How it works Daily Trigger: Activates every morning at 8 AM Data Collection: Fetches period tracking and symptom logs from Google Sheets AI Analysis: GPT-4 analyzes your cycle data to provide personalized insights and predictions Smart Distribution: Weekday updates go to Telegram for quick access, weekend summaries are emailed Calendar Integration: Automatically creates events for predicted cycle phases Requirements Google account (for Sheets and Calendar) Telegram account and bot token OpenAI API key Gmail account for email reports Setup steps Configure the "Configuration Settings" node with your personal IDs Connect your Google Sheets with period and symptom data Set up Telegram bot and add your chat ID Add OpenAI credentials for AI analysis Connect Gmail for weekly reports Activate the workflow How to customize Adjust trigger time to your preferred schedule Modify AI prompts for different health focuses Add more notification channels (Slack, Discord, etc.) Customize report formatting and frequency Add additional data sources for more comprehensive tracking

Description Streamline IT and operations change management by automating approval routing, Jira issue creation, audit logging, and real-time Slack alerts. This workflow ensures faster reviews, traceable approvals, and transparent communication across systems. 🚀 What This Template Does Step 1: Triggers automatically every weekday at 3:00 AM to fetch new or updated change requests from Monday.com. ⏰ Step 2: Extracts key fields (request name, component, risk level, approvers, and description) for structured processing. 🧩 Step 3: Routes each request based on its current status — Pending, Approved, or Rejected. 🔀 Step 4: Sends Slack alerts for pending approvals with detailed context for quick action. 💬 Step 5: Creates Jira tickets for approved requests, ensuring smooth implementation tracking. 🎫 Step 6: Logs all approved requests to Google Sheets for compliance and audit purposes. 📊 Step 7: Sends confirmation emails to requesters with Jira ticket details via Gmail. 📧 Step 8: Automatically creates resubmission items in Monday.com for rejected requests. 🔁 Key Benefits ✅ Eliminates manual approval routing between tools ✅ Centralizes audit trails and implementation data ✅ Accelerates change management turnaround ✅ Provides real-time alerts to approvers and teams ✅ Ensures compliance with automated record-keeping Features Automated daily trigger (Mon–Fri, 3 AM) Monday.com integration for request intake Conditional branching by status (Pending, Approved, Rejected) Jira issue creation for approved requests Slack notifications for pending and approved updates Google Sheets logging for audit tracking Gmail email confirmations for requesters Automatic resubmission handling for rejected requests Requirements Monday.com API credentials with board access Jira API credentials with project permissions Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Gmail OAuth2 credentials for email automation Target Audience IT & DevOps teams managing structured change approvals Project management teams tracking implementation requests Organizations seeking automated risk-based change routing Managers needing centralized logs and instant Slack alerts Step-by-Step Setup Instructions Connect your Monday.com account and replace YOUR_BOARD_ID and groupId. Configure Jira credentials and set the target project for new tickets. Link your Google Sheets document and replace YOUR_SHEET_ID and YOUR_SHEET_GID. Add Slack credentials and update YOUR_CHANNEL_ID for notifications. Set up Gmail OAuth2 for sending confirmation emails. Adjust the cron expression (0 3 * * 1-5) if needed to match your timezone. Run the workflow manually once to test end-to-end connectivity. Enable for scheduled automation and enjoy a fully managed approval process.

Streamline Your Zoom Meetings with Secure, Automated Stripe Payments This comprehensive workflow automates the entire process of setting up a paid online event, from scheduling a Zoom meeting and creating a Stripe payment link to tracking participants and sending confirmation emails. How it Works This workflow has two primary, distinct branches: Event Creation and Participant Registration. Event Creation Flow (Triggered via Form): An administrator submits details (title, price, date/time) via a form. The workflow creates a new Zoom meeting with a unique password. It creates a Stripe Product and a Payment Link. A dedicated Google Sheet tab is created for tracking participants. An email is sent to the event organizer with all the details, including the Zoom link, payment link, and participant list URL. Participant Registration Flow (Triggered via Stripe Webhook): A webhook is triggered when a Stripe payment is completed (checkout.session.completed). The participant's details are added to the dedicated Google Sheet tab. A confirmation email is sent to the participant with the Zoom link and password. A notification email is sent to the event organizer about the new registration. Use Cases Webinar Sales**: Automate setup and registration for paid webinars. Consulting/Coaching Sessions**: Streamline the booking and payment process for group coaching calls. Online Classes**: Handle registration, payment, and access distribution for online courses or classes. Setup Instructions Credentials: Add credentials for: Zoom: For creating the meeting. Google: You need both Gmail and Google Sheets credentials. Stripe: For creating products and handling payment webhooks. Google Sheet: Create a new, blank Google Sheet to hold meeting and participant information. Config Node: Fill the Config node with: currency (e.g., EUR). sheet_url (the URL of the Google Sheet you created). teacher_email (the organizer/host's email). Workflow Logic The workflow splits into two logical parts handled by an if node: Part A: Event Creation (Triggered by Creation Form) Trigger: Creation Form (Form Trigger). Check: if is creation flow (If) evaluates to true. Zoom: Create Zoom meeting creates the session. Stripe Product: Create Stripe Product creates a product and price in Stripe. Stripe Link: Create payment link generates the public payment link, embedding Zoom and sheet metadata. Google Sheet: Create participant list creates a new sheet tab for the event. Email Host: Send email to teacher notifies the host of the successful setup. Part B: Participant Registration (Triggered by On payment) Trigger: On payment (Stripe Trigger - checkout.session.completed). Format: Format participant extracts customer details. Google Sheet: Add participant to list appends the new participant's info to the event's sheet. Email Participant: Send confirmation to participant sends the Zoom access details. Email Host: Notify teacher sends a registration alert. Node Descriptions | Node Name | Description | |-----------|-------------| | Creation Form | A form trigger used to input the event's required details (title, price, start date/time). | | On payment | A Stripe trigger that listens for the checkout.session.completed event, indicating a successful payment. | | Create Zoom meeting | Creates a new Zoom meeting, calculating the start time based on the form inputs. | | Create Stripe Product | Posts to the Stripe API to create a new product and price based on the form data. | | Create payment link | Creates a Stripe Payment Link, embedding Zoom meeting and Google Sheet ID metadata. | | Create participant list | Creates a new tab (named dynamically) in the configured Google Sheet for event tracking. | | Add participant to list | Appends a new row to the event's Google Sheet tab upon payment completion. | | Send email to teacher / Notify teacher | Sends emails to the host/organizer for creation confirmation and new participant registration, respectively. | | Send confirmation to participant | Sends the welcome email to the paying customer with the Zoom access details retrieved from the Stripe metadata. | Customization Tips Email Content**: You are encouraged to adapt the email contents in the Gmail nodes to fit your branding and tone. Currency**: Change the currency in the Config node. Zoom Password**: The password is set to a random 4-character string; you can modify the logic in the Create Zoom meeting node. Stripe Price**: The price is sent to Stripe in the smallest currency unit (e.g., cents, * 100). Suggested Sticky Notes for Workflow Setup**: "Add Your credentials [Zoom, Google, Stripe]. Note: For Google, you need to add Gmail and Google Sheet. Create a new Google Sheet. Keep this sheet blank for now. And fill the config node." Creation Form**: "Your journey to easy event management starts here. Click this node, copy the production URL, and keep it handy. It's your personal admin tool for quickly creating new meetings." Customize**: "Feel free to adapt email contents to your needs." Config**: "Setup your flow". Required Files 2DT5BW5tOdy87AUl_Streamline_Your_Zoom_Meetings_with_Secure,_Automated_Stripe_Payments.json: The n8n workflow export file. A new, blank Google Sheet (URL configured in the Config node). Testing Tips Test Creation**: Run the Creation Form to trigger the Part A flow. Verify that a Zoom meeting and Stripe Payment Link are created, a new Google Sheet tab appears, and the host receives the setup email. Test Registration**: Simulate a successful payment to the generated Stripe link to trigger the Part B flow. Verify that the participant is added to the Google Sheet, receives the confirmation email with Zoom details, and the host receives the notification. Suggested Tags & Categories #Stripe #Zoom #Payment #E-commerce #GoogleSheets #Gmail #Automation #Webinar

Template Description 📝 Template Title Analyze Amazon product reviews with Gemini and save to Google Sheets 📄 Description This workflow automates the process of analyzing customer feedback on Amazon products. Instead of manually reading through hundreds of reviews, this template scrapes reviews (specifically targeting negative feedback), uses Google Gemini (AI) to analyze the root causes of dissatisfaction, and generates specific improvement suggestions. The results are automatically logged into a Google Sheet for easy tracking, and a Slack notification is sent to keep your team updated. This tool is essential for understanding "Voice of Customer" data efficiently without manual data entry. 🧍 Who is this for Product Managers** looking for product improvement ideas. E-commerce Sellers (Amazon FBA, D2C)** monitoring brand reputation. Market Researchers** analyzing competitor weaknesses. Customer Support Teams** identifying recurring issues. ⚙️ How it works Data Collection: The workflow triggers the Apify actor (junglee/amazon-reviews-scraper) to fetch reviews from a specified Amazon product URL. It is currently configured to filter for 1 and 2-star reviews to focus on complaints. AI Analysis: It loops through each review and sends the content to Google Gemini. The AI determines a sentiment score (1-5), categorizes the issue (Quality, Design, Shipping, etc.), summarizes the complaint, and proposes a concrete improvement plan. Formatting: A Code node parses the AI's response to ensure it is in a clean JSON format. Storage: The structured data is appended as a new row in a Google Sheet. Notification: A Slack message is sent to your specified channel to confirm the batch analysis is complete. 🛠️ Requirements n8n** (Self-hosted or Cloud) Apify Account:** You need to rent the junglee/amazon-reviews-scraper actor. Google Cloud Account:** For accessing the Gemini (PaLM) API and Google Sheets API. Slack Account:** For receiving notifications. 🚀 How to set up Apify Config: Enter your Apify API token in the credentials. In the "Run an Actor" node, update the startUrls to the Amazon product page you want to analyze. Google Sheets: Create a new Google Sheet with the following header columns: sentiment_score, category, summary, improvement. Copy the Spreadsheet ID into the Google Sheets node. AI Prompt: The "Message a model" node contains the prompt. It is currently set to output results in Japanese. If you need English output, simply translate the prompt text inside this node. Slack: Select the channel where you want to receive notifications in the Slack node.