Workflow Templates

Who’s it for This workflow is ideal for sysadmins, DevOps engineers, and IT teams who want to monitor server health automatically and receive instant email notifications if any server goes down. It’s perfect for anyone managing multiple servers or services without setting up a full-fledged monitoring tool. How it works / What it does The workflow periodically sends HTTP requests to your server endpoints to check availability and response times. If a server responds with an error code or times out, the workflow automatically sends an email alert with the server details, including the endpoint, status, and timestamp. Multiple servers can be monitored in parallel, ensuring that issues are detected and reported in real time. How to set up Import the workflow template into n8n. Replace the credentials with your credentials. Configure the Email node with your SMTP credentials stored securely in n8n Credentials. Set the Cron node interval to the frequency you want the checks to run (e.g., every 5 minutes). Requirements n8n instance (self-hosted or cloud) SMTP email credentials (Gmail, Outlook, or any SMTP server) Servers with endpoints accessible by n8n

This workflow automates the process of transcribing audio/video files into text using ElevenLabs Speech-to-Text, saving the transcripts to Google Docs, and generating AI-powered summaries and analysis, which are then emailed to a specified address. This ElevenLabs Speech-to-Text model excels in scenarios requiring accurate speech-to-text conversion: Transcription Services: Perfect for converting audio/video content to text Meeting Documentation: Ideal for capturing and documenting conversations Content Analysis: Well-suited for audio content processing and analysis Multilingual Recognition: Supports accurate transcription across 99 languages Files up to 3 GB in size and up to 10 hours in duration are supported. This API supports uploading both audio and video files for transcription. Key Advantages ✅ Automation of Repetitive Tasks: Eliminates manual transcription, note-taking, and reporting. ✅ High-Accuracy Transcription: Powered by ElevenLabs, supporting multiple languages and long files. ✅ Structured Insights: AI-powered analysis (Gemini) transforms raw transcripts into professional summaries with action items and key decisions. ✅ Seamless Integration: Works with Google Sheets, Google Docs, and Gmail for easy workflow adoption. ✅ Scalable & Reusable: Handles multiple recordings in batch and integrates smoothly into existing processes. ✅ Improved Productivity: Teams save time by receiving clear, well-structured meeting recaps without effort. How It Works The workflow operates in a linear sequence, processing one audio URL at a time from a Google Sheet. Trigger & Data Fetch: The process starts manually. It first reads from a specified Google Sheet to get a list of audio file URLs that haven't been processed yet (marked with "DONE"). Transcription: For each audio URL, it sends a request to the ElevenLabs Speech-to-Text API, passing the cloud storage URL of the audio file. Document Creation & Storage: Upon receiving the transcription text from ElevenLabs, the workflow: Creates a new Google Doc named after the transcription ID. Writes the full raw transcript text into this newly created document. Analysis & Summary: The raw transcript text is passed to Google Gemini AI. The AI analyzes the text based on a detailed, pre-defined system prompt that instructs it to extract key points, decisions, action items, and insights, formatting the output as a structured summary. Notification: The AI-generated analysis (converted from Markdown to HTML) is sent via Gmail as an email to a predefined address. Status Update: Finally, the workflow updates the original row in the Google Sheet, marking it as "DONE" (with an 'x') and recording the ID of the newly created Google Doc for future reference. This ensures the same audio file is not processed again on the next run. Set Up Steps To configure this workflow, you need to complete the following steps: Credentials Setup: ElevenLabs API: In the "Speech-to-Text" HTTP Request node, configure the HTTP Header Auth credentials. The header name should be xi-api-key and the value should be your valid ElevenLabs API key. Google Services: Ensure your Google Sheets, Google Docs, and Gmail nodes are connected to valid Google OAuth2 credentials with the necessary permissions to read, write, and send emails. Google Gemini AI: The "Transcript Analysis" node must be connected to valid Google Gemini (PaLM) API credentials. Google Sheet Configuration: Make a copy of the provided Google Sheet template. In the "Get audio urls" node, update the documentId parameter to match the ID of your new Google Sheet. Similarly, update the documentId in the "Update row" node. Populate your sheet with the URLs of the audio/video files you want to process in the 'AUDIO URL' column. Output Configuration: In the "Send email" node, change the sendTo parameter to the email address where you want to receive the analysis summaries. The "Create Doc" node specifies a folderId; change this to the ID of the specific Google Drive folder where you want the transcripts to be saved. Need help customizing? Contact me for consulting and support or add me on Linkedin.

Description Automated workflow that generates a Sprint Report from Jira and delivers it by Gmail. The flow fetches sprint issues from Jira, validates and normalizes the data, calculates metrics (tickets, story points, blockers, completion rate), generates an HTML report, and sends it by email. Context This template helps teams keep stakeholders updated automatically of the current sprint. Instead of manually compiling Jira data, the report is generated and sent on schedule (e.g., every Friday at 17:00). It’s production-friendly, reusable, and works across Jira projects. Target Users Scrum Masters and Agile Coaches who need sprint reports for retrospectives. Product Owners who want a weekly overview of sprint progress. Project Managers tracking Jira delivery KPIs. Engineering teams wanting automated status reporting without extra overhead. Technical Requirements Jira Cloud project + API email + API token + permission to read issues. Gmail credential for notifications. Workflow Steps Trigger – Schedule (e.g., Friday at 17:00). Edit Fields – Configure Jira base URL, project key, email recipients. Get Many Issues – Fetch sprint issues with JQL (project = <KEY> AND sprint in openSprints()). Validation & Normalization – Clean/validate fields (status, assignee, priority, story points, sprint info). Metrics Calculation – Aggregate KPIs (done, in progress, blockers, story points, completion %). HTML Report Generation – Build a styled email-friendly HTML summary + detailed table. Send Gmail – Deliver report to stakeholders. Key Features Automated Sprint Reports: No manual copy-paste. Metrics overview: Tickets done vs total, blockers, story points. Detailed table: Issue key, summary, status, assignee, priority, SP. Email delivery: HTML report with Jira links sent to stakeholders. Fully customizable: Adjust fields, KPIs, and recipients easily. Expected Output 📊 HTML Sprint Report with KPIs and issue table. ✅ Email delivered to stakeholders via Gmail. 🔗 Jira links embedded for easy navigation. How it works ⏰ Trigger – Runs on schedule (e.g., every Friday at 17:00). 🧾 Fetch Issues – JQL filters sprint tickets. 📊 Metrics – Done vs total, SP progress, blockers. 💻 Generate HTML – Clean, styled table and summary. ✉️ Notify – Send Gmail with full sprint report to stakeholders. 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

Secure your perfect Malaysian identity with the Khaisa Domain Sniper. This n8n workflow monitors specific .my domains using the free MYNIC RDAP API, instantly triggering Gmail and Discord alerts the moment a domain becomes available for registration, ensuring you never miss a high-value branding opportunity again. Why Use This Workflow? Time Savings: Eliminates the need for manual WHOIS lookups, saving roughly 2 hours of repetitive checking per week. Error Prevention: Automated 24/7 monitoring ensures you are notified within 30 minutes of a domain status change, preventing competitors from "sniping" your target. Scalability: Effortlessly monitor a list of 10, 50, or 100+ domains by simply adding rows to a Google Sheet. Ideal For Digital Agencies:** Monitor expiring client brand names or high-value industry keywords for SEO benefits. Startup Founders:** Secure the perfect .my or .com.my domain for a new venture as soon as it is released. Domain Investors:** Automate the "sniping" process for expired Malaysian domains to build a valuable portfolio. How It Works Trigger: A scheduled trigger initiates the process every 30 minutes. Data Collection: The workflow pulls a list of target domains from a Google Sheet where the status is marked as "no" (not available). Processing: A loop iterates through each domain, preparing individual requests. Intelligence Layer: The workflow queries the official MYNIC RDAP public API to check the real-time registration status. Output & Delivery: If the API confirms availability, the system sends a professionally styled HTML email via Gmail and a notification to a Discord channel. Storage & Logging: The Google Sheet is automatically updated to "yes" for available domains to prevent duplicate alerts. Setup Guide Prerequisites | Requirement | Type | Purpose | |-------------|------|---------| | n8n instance | Essential | Workflow execution platform | | Google Sheets | Essential | Central database for target domains | | Gmail Account | Essential | To send stylized HTML availability alerts | | Discord Bot | Optional | For instant push notifications to your team | | MYNIC RDAP | Public | No API key required for .my domain lookups | Installation Steps Import the JSON file to your n8n instance Configure credentials: Google Sheets: Connect your Google account and select your "Domain Target" spreadsheet. Gmail: Authenticate the Gmail node to allow the system to send alerts from your address. Discord: Add your Bot Token and Channel ID if you wish to receive Discord alerts. Prepare your Google Sheet: Create two columns: Domain and isAvailable. Add your target domains (e.g., brandname.my) and set isAvailable to no. Customize settings: Adjust the Schedule Trigger to your preferred frequency (e.g., every 15 or 30 minutes). Test execution: Run the workflow manually with one "available" test domain to confirm the email and Discord formatting. Technical Details Core Nodes | Node | Purpose | Key Configuration | |------|---------|-------------------| | RDAP: Check Status | Fetch API Data | Uses https://rdap.mynic.my/rdap/domain/{domain} | | Domain Available? | Logic Gate | Checks if response contains "is available for registration" | | Gmail Alert | Notification | Sends custom HTML template with "Register Now" button | | Update Sheet | Data Sync | Switches isAvailable to yes upon discovery | Workflow Logic The workflow uses a "Split in Batches" approach combined with a 10-second Wait Node. This is critical for performance as it prevents hitting MYNIC rate limits when checking long lists of domains, ensuring high reliability and preventing your IP from being temporarily blocked. Customization Options Basic Adjustments: Check Frequency:** Change the cron schedule from 30 minutes to 5 minutes for high-priority domains. Wait Duration:** Increase the 10-second wait if you are monitoring more than 100 domains in a single run. Advanced Enhancements: Auto-Registration:** Connect a registrar API (like OpenSRS or Hexonet) to automatically attempt registration. Multi-Extension:** Expand the logic to check .com, .net, or .io domains by adding conditional URL logic for different RDAP providers. Performance & Optimization | Metric | Expected Performance | Optimization Tips | |--------|---------------------|-------------------| | Execution time | ~12s per domain | Parallel processing can be enabled for small lists | | API calls | 1 per domain | Only processes domains marked as isAvailable = no | | Error handling | "Never Error" active | HTTP node is set to continue even if the API times out | Troubleshooting Common Issues: | Problem | Cause | Solution | |---------|-------|----------| | 429 Too Many Requests | Checking too fast | Increase the time in the Wait 10 Seconds node | | Gmail Authentication Error | Token expired | Re-connect your Google OAuth2 credentials | | Sheet not updating | Column name mismatch | Ensure headers in GSheets match the node mapping exactly | Use Case Examples Scenario 1: Brand Protection Challenge: A competitor currently owns a .my domain that matches your .com brand, and you are waiting for it to expire. Solution: This workflow monitors the domain 24/7 and alerts your legal team the moment it hits the "Available" status. Result: You secure your local brand identity without paying a premium to a domain broker. Scenario 2: Professional Domain Flipping Challenge: You have a list of 50 high-value keywords you want to acquire as they drop from the registry. Solution: Add the list to Google Sheets. The workflow checks them every 30 minutes and notifies your Discord "Sniper" channel. Result: You are always the first to know, allowing you to register prime digital real estate before others. Created by: Khaisa Studio Category: Productivity | Tags: Domain, Automation, Monitoring, MYNIC, RDAP Need custom workflows? Contact us Connect with the creator: Portfolio • Workflows • LinkedIn • Medium • Threads

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 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

Who's it for This workflow is designed for venture capitalists, private equity professionals, investment analysts, and financial researchers who need to track private securities offerings and fundraising activities in real-time. It's particularly valuable for firms building deal flow pipelines, monitoring competitor fundraising, or conducting private market research. What it does This automation continuously monitors the SEC's EDGAR database for new Form D filings, which companies file when raising capital through private placements. Every 10 minutes during business hours (Monday-Friday, 6 AM - 9 PM), it checks for new filings, downloads the complete documents, and extracts critical information into a structured Google Sheets database. The workflow captures comprehensive details including company name and contact information, key executives and their roles, fund classification, target offering amount, current capital raised, total investor count, sale status, filing dates, and regulatory exemptions being utilized (such as Rule 506(b) or 3(c)(7)). How it works The workflow operates in five main stages: Stage 1 - Feed Monitoring: A scheduled trigger activates every 10 minutes during business hours, fetching the latest Form D filing feed from the SEC EDGAR system in XML format. Stage 2 - Initial Processing: The XML feed is parsed to extract basic filing metadata including CIK numbers, company names, form types, and document URLs. The system then filters out any previously processed filings using deduplication logic and adds only new filings to your Google Sheet tracking database. Stage 3 - Selective Processing: The workflow identifies unprocessed Form D and Form D/A (amendment) filings that need detailed extraction, filtering out other form types and already-processed entries. Stage 4 - Deep Data Extraction: For each unprocessed filing, the workflow downloads the complete Form D text document, parses the embedded XML structure, and systematically extracts four categories of information: issuer details (company name, address, CIK, jurisdiction, entity type, industry classification), key personnel (executives, directors, promoters with their specific roles), offering information (total offering amount, amount already sold, remaining amount, investor count, accredited investor status), and regulatory details (exemptions claimed, sale status, offering duration). Stage 5 - Database Update: All extracted data is consolidated into a summary format and used to update the corresponding row in your Google Sheet, marking the filing as "processed". A wait node introduces a brief delay between document retrievals to comply with SEC rate limiting policies. Requirements To use this workflow, you'll need: A Google Sheet configured with these specific columns: cikNumber, title, formType, filingLinkHtml, filingLinkTxt, updated, companyName, keyExecutive, executiveRole, fundType, targetAmount, amountRaised, investorCount, salesStatus, filingDate, exemptions, status, and comment Google Sheets OAuth2 credentials connected in n8n to enable read/write access Compliance with SEC EDGAR requirements: you must update the User-Agent headers in both HTTP Request nodes (replacing the placeholder email with your own valid email address as required by SEC's fair access policy) Setup instructions Step 1: Create or prepare your Google Sheet with the exact column structure listed in the requirements section. Note your Google Sheet ID from the browser URL. Step 2: In n8n, configure your Google Sheets OAuth2 credentials through the credentials panel. Test the connection to ensure it's working properly. Step 3: Open both Google Sheets nodes in the workflow ("Add New Filing to Tracking Sheet" and "Update Filing Status in Sheet"). Update the Document ID field with your Google Sheet ID. Step 4: Critical compliance step - Open both HTTP Request nodes ("Fetch SEC Form D Feed" and "Retrieve Form D Document"). In the headers section, replace nchoudhary110792@gmail.com with your actual email address. The SEC requires this for their access logs. Step 5: Test the workflow manually first by clicking "Execute Workflow" to ensure everything connects properly and data flows to your sheet correctly. Step 6: Once verified, activate the workflow using the toggle switch. It will now run automatically on the configured schedule. Customization options Adjust monitoring frequency: Modify the Schedule Trigger node's cron expression to run more or less frequently. The default */10 6-21 * * 1-5 runs every 10 minutes during business hours on weekdays. Filter by fund type or size: Add a Filter (IF) node after "Consolidate Filing Data" to only process filings that meet specific criteria (e.g., offerings above $10M, specific fund types like hedge funds or venture capital). Add real-time notifications: Connect a Slack, Discord, or Email node after "Update Filing Status in Sheet" to receive instant alerts when high-priority filings are detected (based on criteria you define). Enrich with external data: Add HTTP Request nodes to query APIs like Crunchbase, PitchBook, or LinkedIn to supplement SEC data with additional company intelligence, funding history, or executive backgrounds. CRM integration: Replace or supplement the Google Sheets nodes with connections to your CRM (Salesforce, HubSpot, Pipedrive) to automatically create deal records or update company profiles when relevant filings appear. Historical analysis: Add a Set node to calculate metrics like month-over-month filing volume, average raise sizes by industry, or track specific companies' filing patterns over time. Multi-sheet organization: Use Router nodes to send different filing types to separate sheets (e.g., venture capital funds vs. hedge funds vs. real estate offerings) for easier analysis.

📊 Google Sheets Leads → 🎲 Random Templates → ✉️ Personalized Emails → 📝 Status Tracking What this workflow does 📊 Reads leads list from Google Sheets (Name, Email, Send Status) 🔍 Filters out already-contacted leads (skips "SENT" status) 🎲 Randomly selects email template from template library ✏️ Personalizes subject and body with lead's name 📧 Sends emails one-by-one with delays between sends ✅ Updates Google Sheet with send status and timestamp 🔁 Loops through all unsent leads automatically Why it's useful ⚡ Automate cold outreach without manual copy-paste 🎯 Avoid duplicate sends—tracks who's been contacted 📝 Rotate email templates for A/B testing and variety 👤 Personalization makes emails feel human, not spammy ⏱️ Built-in delays prevent spam flags and rate limits 📊 Full audit trail of who received what and when How it works 📊 Google Sheets (Leads) → reads Name, Email, Send Status 🚦 IF Node → filters leads where Send Status ≠ "SENT" 🔄 Loop Over Items → processes leads one-by-one 📧 Google Sheets (Templates) → fetches Subject + Body templates 🎲 Code Node → picks random template 🔀 Merge → combines lead data with template ✏️ Edit Fields → replaces [Name] with actual lead name 📨 Send Email → delivers personalized message ⏳ Wait → adds delay between sends (avoids spam flags) ✅ Google Sheets (Update) → marks as "SENT" with timestamp What you'll need 📊 Google Sheet #1: Leads (columns: Name, Email, Send Status, Time) 📧 Google Sheet #2: Templates (columns: Subject, Body) 📬 SMTP credentials (SendGrid, Mailgun, etc.) 🔐 Google Sheets OAuth Setup steps 📊 Create "Leads" sheet with columns: Name | Email | Send Status | Time 📧 Create "Templates" sheet with columns: Subject | Body (use [Name] placeholder) 🔗 Connect Google Sheets OAuth credentials 📬 Add SMTP email credentials 🧭 Update both Google Sheets node IDs to point to your sheets ⚙️ Set "From Email" in Send Email node 🧪 Test with 2-3 test leads first Customization ideas ⏱️ Adjust Wait time (30s-5min) to control send rate 📊 Add click tracking with UTM parameters 🔔 Send Slack/Telegram notification when campaign completes 🎯 Add lead scoring—prioritize high-value leads first 📈 Log opens/replies to separate tracking sheet Who it's for 🧑‍💻 Freelancers doing cold outreach to agencies 📈 Sales teams running lead generation campaigns 🚀 Startups reaching out to potential customers 🎯 Marketers testing email copy variations 💼 Business developers nurturing prospect lists Quick Setup Guide Before You Start - What You Need: 📊 Google account for Sheets access 📧 SMTP email account (Gmail, custom domain, or email service) 📝 List of leads (names + emails) ✉️ Email templates ready (with [Name] placeholders) Want help customizing? 📧 anirpoke@gmail.com 🔗 LinkedIn

Categories CRM Automation, Revenue Operations, Sales Operations, Meeting Automation Build a Revenue Ops Meeting Pipeline with Pipedrive, Calendar, Slack This workflow creates a CRM-driven revenue operations meeting pipeline that automatically coordinates meetings once a deal reaches a specific stage in Pipedrive. When a deal moves into the Meeting Booking stage, the workflow waits for the SDR to complete the meeting details, creates the event in Google Calendar, sends a confirmation email to the client, and notifies the internal team in Slack. The result is a reliable, no-manual-work system that ensures meetings are scheduled, confirmed, and communicated without human follow-up. Benefits CRM as the Single Source of Truth** All automation is triggered directly from deal stage changes. Reduced No-Shows** Clients receive timely meeting confirmations with correct links and times. Zero Manual Coordination** No copying links, sending reminders, or checking calendars. Internal Visibility** Sales teams receive Slack reminders automatically. Time-Zone Safe Scheduling** Meeting times are calculated and normalized automatically. How It Works Deal Stage Trigger (Pipedrive) Listens for deal updates in Pipedrive Runs only when the deal enters the Meeting Booking stage Prevents execution on irrelevant pipeline changes Controlled Wait Logic Pauses execution to allow the SDR to: Add the meeting link Set date, time, and duration Ensures data completeness before scheduling Data Extraction & Enrichment Fetches full deal details Extracts: Client name and email Company name Meeting link Meeting date and time Calculates ISO start and end times with time-zone handling Calendar Event Creation (Google Calendar) Creates a calendar event automatically Adds the client as an attendee Inserts the meeting link as the event location Client Email Confirmation Sends a personalized confirmation email Includes meeting date, time, and context Reduces rescheduling and confusion Internal Slack Notification Sends a reminder to a selected Slack channel Notifies SDRs and sales managers of upcoming meetings Keeps teams aligned without CRM checking Required Setup Pipedrive Deal pipeline with a defined Meeting Booking stage Meeting details stored in deal activities Google Calendar OAuth access enabled Permission to create events Gmail OAuth access enabled Email sending permissions Slack OAuth access enabled Target channel selected Business Use Cases Sales Teams Eliminate missed meetings and manual reminders Reduce admin work for SDRs Revenue Operations Standardize meeting execution across pipelines Improve forecasting reliability Founders & Managers Increase meeting attendance without micromanagement Agencies & Consultants Deliver CRM-based RevOps automation to clients Difficulty Level Intermediate Estimated Build Time 45–60 minutes Monthly Operating Cost Pipedrive: Existing plan Google Calendar: Free Gmail: Free Slack: Free or paid workspace n8n: Self-hosted or cloud Typical range: $0–20/month Why This Workflow Works Deal stage changes represent real sales intent Waiting logic prevents broken automations Calendar-first execution ensures reliability Multi-channel notifications reduce human error Possible Extensions Add SMS or WhatsApp reminders Auto-cancel meetings on stage rollback Log meeting outcomes back to Pipedrive Trigger post-meeting follow-ups Add AI-generated meeting summaries

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)