Browse 13,012 Workflows

By Fahmi Fahreza

Quick overview Sign up for Decodo HERE for Discount Automatically fetches page content, generates a compact SEO audit (score, issues, fixes), and writes both a per-URL summary and a normalized “All Issues” table to Google Sheets—great for weekly monitoring and prioritization. How it works Weekly trigger loads the Google Sheet of URLs. Split in Batches processes each URL. Decodo fetches page content (markdown + status). Gemini produces a strict JSON audit via the AI Chain + Output Parser. Code nodes flatten data for two tabs. Google Sheets nodes append Summary and All Issues rows. Split in Batches continues to the next URL. Setup Add credentials for Google Sheets, Decodo, and Gemini. Set sheet_id and Sheet GIDs in the Set node. Ensure input sheet has a URL column. Configure your Google Sheets tabs with proper headers matching each field being appended (e.g., URL, Decodo Score, Priority, etc.). Adjust schedule as needed. Activate the workflow. Additional info Published by Fahmi Fahreza, Indonesia’s first official n8n Brand Ambassador and founder of WithMi Automation, built from real client implementations, not tutorials. → Let us build it for you: withmiautomation.com → Learn to build it yourself: academy.withmiautomation.com → Bring Fahmi to your team (training, workshop, talkshow): fahmiiireza.com. An n8n automation workflow template by Fahmi Fahreza.

By Asfandyar Malik

Automatically track new freelance job postings from any platform using Apify Actors, process the results, and get real-time WhatsApp alerts for new opportunities. This workflow saves jobs to Google Sheets for record-keeping and sends instant notifications so you never miss a client lead. Who’s it for Freelancers, agencies, and business developers who want to monitor platforms like Upwork, Fiverr, or Freelancer for new jobs — without checking manually. How it works The workflow starts when a chat message or trigger event is received. It runs an Apify Actor to scrape job listings from your target platform. The dataset results are fetched via Apify’s API. A JavaScript Code node processes and filters the results for relevant jobs. The data is saved to Google Sheets for tracking and reporting. A formatted job summary is created and sent as a WhatsApp message directly to your phone. How to set up Create or use an Apify Actor for scraping job listings from your chosen site. Connect your Apify API token in n8n under credentials. Link your Google Sheets account and specify the sheet for storing job data. Add your WhatsApp Cloud API or Twilio WhatsApp credentials. Test the workflow by sending a trigger message — new jobs will be fetched, stored, and sent to WhatsApp. Requirements Apify account with API access Google Sheets integration WhatsApp Cloud API or Twilio account n8n Cloud or self-hosted instance How to customize 🧩 Add filters: Include keyword or budget filters in the JavaScript node. 🔄 Schedule runs: Replace the chat trigger with a Cron node for hourly or daily tracking. 📊 Change destination: Save results to Notion, Airtable, or Slack instead of Google Sheets. 🗣️ Multi-channel alerts: Send updates to Discord, Telegram, or Email as well. Stay ahead of freelance opportunities — this n8n workflow finds jobs, logs them, and alerts you instantly via WhatsApp. An n8n automation workflow template by Asfandyar Malik.

By Asfandyar Malik

Automatically create, evaluate, and optimize professional biographies with the Bio-Graphy Agent. This workflow uses a multi-agent system powered by GPT-5 to write, review, and enhance bios — then saves the final version directly to Google Docs. Who’s it for For professionals, creators, and marketers who want high-quality biographies for their profiles, portfolios, or LinkedIn — without spending hours writing or editing. How it works The user sends a chat message with details like name, age, and location. The Biography Agent generates a complete biography using the GPT-5 Chat Model. The Evaluator Agent reviews the bio and provides structured feedback. The Optimizer Agent refines tone, structure, and clarity based on that feedback. The final biography is saved automatically to Google Docs for easy access or publishing. How to set up Connect your Google account in n8n to enable document saving. Add your OpenAI (GPT-5 or compatible) credentials to the agent nodes. Customize prompts in the Biography, Evaluator, and Optimizer agents for your preferred writing style. Test the workflow by sending a chat message with basic personal details. Your completed bio will be generated, improved, and saved to your connected Google Docs. Requirements n8n Cloud or Self-hosted instance Google Docs integration OpenAI (GPT-compatible) credentials How to customize 🎯 Add personality: Adjust the prompts to make bios sound more friendly, formal, or humorous. 🌐 Change output: Send the result to Notion, Airtable, or Gmail instead of Google Docs. 🪄 Add another agent: Include a Grammar or Tone Correction agent for extra polish. 🧩 Extend use: Adapt it for “About Us” pages, resumes, or brand storytelling. Use this workflow to instantly generate professional, polished bios — powered by GPT-5 and automated through n8n. An n8n automation workflow template by Asfandyar Malik.

By Daniel Shashko

How it Works This workflow automates competitive price intelligence using Bright Data's enterprise web scraping API. On a scheduled basis (default: daily at 9 AM), the system loops through configured competitor product URLs, triggers Bright Data's web scraper to extract real-time pricing data from each site, and intelligently compares competitor prices against your current pricing. The workflow handles the full scraping lifecycle: it sends scraping requests to Bright Data, waits for completion, fetches the scraped product data, and parses prices from various formats and website structures. All pricing data is automatically logged to Google Sheets for historical tracking and trend analysis. When a competitor's price drops below yours by more than the configured threshold (e.g., 10% cheaper), the system immediately sends detailed alerts via Slack and email to your pricing team with actionable intelligence. At the end of each monitoring run, the workflow generates a comprehensive daily summary report that aggregates all competitor data, calculates average price differences, identifies the lowest and highest competitors, and provides a complete competitive landscape view. This eliminates hours of manual competitor research and enables data-driven pricing decisions in real-time. Who is this for? E-commerce businesses and online retailers needing automated competitive price monitoring Product managers and pricing strategists requiring real-time competitive intelligence Revenue operations teams managing dynamic pricing strategies across multiple products Marketplaces competing in price-sensitive categories where margins matter Any business that needs to track competitor pricing without manual daily checks Setup Steps Setup time: Approx. 30-40 minutes (Bright Data configuration, credential setup, competitor URL configuration) Requirements: Bright Data account with Web Scraper API access Bright Data API token (from dashboard) Google account with a spreadsheet for price tracking Slack workspace with pricing channels SMTP email provider for alerts Sign up for Bright Data and create a web scraping dataset (use e-commerce template for product data) Obtain your Bright Data API token and dataset ID from the dashboard Configure these nodes: Schedule Daily Check: Set monitoring frequency using cron expression (default: 9 AM daily) Load Competitor URLs: Add competitor product URLs array, configure your current price, set alert threshold percentage Loop Through Competitors: Automatically handles multiple URLs (no configuration needed) Scrape with Bright Data: Add Bright Data. An n8n automation workflow template by Daniel Shashko.

By Yehor EGMS

🎙️ n8n Workflow: Voice Message Transcription with Access Control This n8n workflow enables automated transcription of voice messages in Telegram groups with built-in access control and intelligent fallback mechanisms. It's designed for teams that need to convert audio messages to text while maintaining security and handling various audio formats. 📌 Section 1: Trigger & Access Control ⚡ Receive Message (Telegram Trigger) Purpose: Captures incoming messages from users in your Telegram group. How it works: When a user sends a message (voice, audio, or text), the workflow is triggered and the sender's information is captured. Benefit: Serves as the entry point for the entire transcription pipeline. 🔐 Sender Verification Purpose: Validates whether the sender has permission to use the transcription service. Logic: Check sender against authorized users list If authorized → Proceed to next step If not authorized → Send "Access denied" message and stop workflow Benefit: Prevents unauthorized users from consuming AI credits and accessing the service. 📌 Section 2: Message Type Detection 🎵 Audio/Voice Recognition Purpose: Identifies the type of incoming message and audio format. Why it's needed: Telegram handles different audio types with different statuses: Voice notes (voice messages) Audio files (standard audio attachments) Text messages (no audio content) Process: Check if message contains audio/voice content If no audio file detected → Send "No audio file found" message If audio detected → Assign file ID and proceed to format detection 🧩 File Type Determination (IF Node) Purpose: Identifies the specific audio format for proper processing. Supported formats: OGG (Telegram voice messages) MPEG/MP3 MP4/M4A Other audio formats Logic: If format recognized → Proceed to transcription If format not recognized → Send "File format not recognized" message Benefit: Ensures compatibility with transcription services by validating file types upfront. 📌 Section 3: Primary Transcription (OpenAI) 📥 File Download Purpose: Downloads the audio file from Telegram for processing. 🤖 OpenAI Transcription Purpose: Transcribes audio to text using OpenAI's Whisper API. Why OpenAI: High-quality transcription with cost-effective pricing. Process: Send downloaded file to OpenAI transcription API Simultaneously send notification: "Transcription started" If successful → Assign transcribed text to variable and proceed If error occurs → Trigger fallback mechanism Benefit: Fast, accurate transcription with multi-language support. 📌 Section 4: Fallback Transcription (Gemini) 🛟 Gemini Backup Transcription Purpose: Provides a safety net if OpenAI transcription fails. Process: Receives file only if OpenAI node returns an error Downloads and processes the same audio file Sends to Google Gemini for transcription Assigns transcribed text to the same text variable Benefit: Ensures high reliability—if one service fails, the other takes over automatically. 📌 Section 5: Message Length Handling 📏 Text Length Check (IF Node) Purpose: Determines if the transcribed text exceeds Telegram's character limit. Logic: If text ≤ 4000 characters → Send directly to Telegram If text > 4000 characters → Split into chunks Why: Telegram has a 4,000-character limit per message. ✂️ Text Splitting (Code Node) Purpose: Breaks long transcriptions into 4,000-character segments. Process: Receives text longer than 4,000 characters Splits text into chunks of ≤4,000 characters Maintains readability by avoiding mid-word breaks Outputs array of text chunks 📌 Section 6: Response Delivery 💬 Send Transcription (Telegram Node) Purpose: Delivers the transcribed text back to the Telegram group. Behavior: Short messages:** Sent as a single message Long messages:** Sent as multiple sequential messages Benefit: Users receive complete transcriptions regardless of length, ensuring no content is lost. 📊 Workflow Overview Table | Section | Node Name | Purpose | |---------|-----------|---------| | 1. Trigger | Receive Message | Captures incoming Telegram messages | | 2. Access Control | Sender Verification | Validates user permissions | | 3. Detection | Audio/Voice Recognition | Identifies message type and audio format | | 4. Validation | File Type Check | Verifies supported audio formats | | 5. Download | File Download | Retrieves audio file from Telegram | | 6. Primary AI | OpenAI Transcription | Main transcription service | | 7. Fallback AI | Gemini Transcription | Backup transcription service | | 8. Processing | Text Length Check | Determines if splitting is needed | | 9. Splitting | Code Node | Breaks long text into chunks | | 10. Response | Send to Telegram | Delivers transcribed text | 🎯 Key Benefits 🔐 Secure access control: Only authorized users can trigger transcriptions 💰 Cost management: Prevents unauthorized credit consumption 🎵 Multi-format support: Handles various Telegram audio types 🛡️ High reliability: Dual-AI fallback ensures transcription success 📱 Telegram-optimized: Automatically handles message length limits 🌍 Multi-language: Both AI services support numerous languages ⚡ Real-time notifications: Users receive status updates during processing 🔄 Automatic chunking: Long transcriptions are intelligently split 🧠 Smart routing: Files are processed through the optimal path 📊 Complete delivery: No content loss regardless of transcription length 🚀 Use Cases Team meetings:** Transcribe voice notes from team discussions Client communications:** Convert client voice messages to searchable text Documentation:** Create text records of verbal communications Accessibility:** Make audio content accessible to all team members Multi-language teams:** Leverage AI transcription for various languages. An n8n automation workflow template by Yehor EGMS.

By Yehor EGMS

🔐 n8n Workflow: Access Control for Internal Chats or Chatbots This n8n workflow helps you restrict access to your internal chats or chatbots so that only authorized team members can interact with them. It's perfect for setups using Telegram, Slack, or other corporate messengers, where you need to prevent unauthorized users from triggering internal automations. 📌 Section 1: Trigger & Input ⚡ Receive Message (Telegram Trigger) Purpose: Captures every incoming message from a user interacting with your Telegram bot (or another messenger). How it works: When a user sends a message, it instantly triggers the workflow and passes their username or ID as input data. Benefit: Acts as the entry point for verifying whether a user is allowed to proceed. 📌 Section 2: Access Table Lookup 📋 User Access Table (Data Node / Spreadsheet / DB Query) Purpose: Stores all your team members and their current access status. Structure Example: | Username | Access Status | |----------|---------------| | user1 | granted | | user2 | denied | | user3 | granted | Benefit: Centralized access control — you can easily update user permissions without editing the workflow. 📌 Section 3: Permission Check 🧩 Check Access (IF Node) Purpose: Compares the incoming user's name or ID against the access table. Logic: If status = granted → Allow message to continue If status = denied → Stop workflow execution Benefit: Ensures only approved users can interact with your automations or receive responses. 📌 Section 4: Response Handling 💬 Send Reply (Telegram Node) Purpose: Sends a message back to the user depending on their access level. Paths: ✅ Granted: Sends the normal bot response or triggers the main process. ❌ Denied: Sends no reply (or an optional "Access denied" message). Benefit: Prevents unauthorized access while maintaining a seamless experience for approved users. 📊 Workflow Overview Table | Section | Node Name | Purpose | |---------|-----------|---------| | 1. Trigger | Receive Message | Captures incoming messages | | 2. Access Table | User Access Table | Stores usernames + permissions | | 3. Check | Check Access | Verifies if user has permission | | 4. Response | Send Reply | Sends or blocks response based on status | 🎯 Key Benefits 🔐 Secure access control: Only trusted users can trigger your internal automations. ⚙️ Dynamic management: Easily update user permissions from a table or database. 🧠 Lightweight setup: Just three nodes create a fully functional access gate. 🚀 Scalable foundation: Extend it with role-based access or activity logging later. An n8n automation workflow template by Yehor EGMS.

By Jitesh Dugar

University Admission Confirmation & Welcome Kit A robust n8n workflow template that automates the university admission process for colleges, universities, and educational programs. This workflow validates student emails, generates professional PDF admission letters, sends personalized welcome emails, and handles errors efficiently — all in under 15 seconds per submission. Perfect for streamlining student onboarding with professional communication. Overview This workflow automates the process of handling new admission submissions by: Verifying student emails in real-time Generating university-branded admission confirmation PDFs Sending personalized welcome emails Logging invalid entries and preventing spam Key Features Email Verification & Fraud Prevention Real-time email validation using VerifiEmail API Checks RFC compliance, MX records, disposable emails, and spoofed addresses Rejects invalid emails before processing Prevents fake registrations and ensures deliverability Automated PDF Generation Creates branded, print-ready admission letters using PDFMunk Includes student details, program information, and verification badge Professional design with gradient headers and university branding Dynamic data integration for personalized documents Smart Email Notifications Student Welcome Email:** Personalized confirmation with PDF attachment Invalid Email Alerts:** Notifies admissions team of failed validations Responsive Design:** Mobile-friendly, clear next steps Intelligent Routing Conditional logic based on validation results Valid emails → generate PDF + send email Invalid emails → log and stop workflow Saves API usage and execution time Error Handling Comprehensive error detection for validation and API failures Detailed logging for invalid addresses Stops on failure to avoid unnecessary processing Sends admin alerts with actionable info Perfect For Universities & Colleges (Undergraduate & Postgraduate Admissions) Online Education Platforms (MOOCs, Certifications) Training & Vocational Programs Study Abroad Agencies Scholarship & Fellowship Applications Continuing Education Departments Workflow Statistics | Metric | Detail | |---------|--------| | Total Nodes | 15 | | Complexity | ⭐⭐ Medium | | Processing Time | 8–15 seconds per submission | | Setup Time | 10–15 minutes | | Code Required | ❌ No code (No-code solution) | | Maintenance | Minimal (Set & forget) | Requirements Required Services & APIs | Service | Purpose | Signup | |----------|----------|--------| | VerifiEmail API | Email validation | verifi.email | | PDFMunk API | PDF generation | pdfmunk.com | | Gmail | Email notifications | Google Cloud Console | Optional Integrations Google Forms or Typeform (data source) Google Sheets (admission tracking) Slack (team notifications) CRM (Salesforce, HubSpot, etc.) What Gets Created PDF Admission Letter Generated using PDFMunk API Includes: University-branded header & gradient design Email verification badge Student details (Name, Course, Application ID) Admission date & program info Professional footer & signature Email Notifications 1. Student Welcome Email Personalized greeting + attached PDF Next steps checklist (enrollment, orientation, etc.) Mobile-responsive design 2. Invalid Email Alert (Admin) Sent to admissions@youruniversity.edu Includes failure reasons, student name, and application ID Actionable follow-up steps Quick Start Guide 1️⃣ Import Template Copy workflow JSON In n8n → Workflows → Import from Clipboard Paste and import 2️⃣ Configure Credentials (10 minutes) A. VerifiEmail API Sign up → get API key → add under VerifiEmail account B. PDFMunk API Sign up → get API key → add under HtmlcsstopdfApi account C. Gmail OAuth2 Create project in Google Cloud Console Enable Gmail API → OAuth 2.0 credentials Add under Gmail account in n8n 3️⃣ Update Email Addresses Welcome Email Node:** admissions@youruniversity.edu Invalid Alert Node:** admissions team email Update branding details in email + PDF templates 4️⃣ Test the Workflow curl -X POST https://your-n8n.com/webhook/admission-form \ -H "Content-Type: application/json" \ -d '{ "name": "John Doe", "email": "john.doe@example.com", "course": "B.Tech Computer Science", "college_name": "TechNova University", "application_id": "TN-2025-0451", "admission_date": "2025-10-12" }' 5️⃣ Activate Workflow Toggle ON in n8n (top-right corner). 🧠 Detailed Setup Instructions Step 1: VerifiEmail Configuration Sign up → get API key Add in VerifiEmail Node credentials Test with sample email Step 2: PDFMunk Setup Sign up → get API key Add in HTML to PDF Node Test with sample execution Step 3: Gmail Configuration Enable Gmail API Add OAuth 2.0 credentials Authenticate with Gmail account Test sending an email Step 4: Webhook Setup Copy webhook URL from “Webhook - Admission Form” node Connect your form platform (Google Form, Typeform, etc.) Ensure JSON payload includes: name, email, course, college_name, application_id, admission_date Step 5: Test & Validate ✅ Valid email: Check PDF generation + welcome email ❌ Invalid email: Confirm admin alert sent ⚠️ Missing data: Review error logs 🔄 Workflow Diagram Start ↓ Webhook Trigger ↓ Email Verification (VerifiEmail API) ↓ Conditional Check (Valid?) ↙️ ↘️ TRUE FALSE ↓ ↓ Generate PDF Log Error ↓ ↓ Send Welcome Email End ↓ Done ✅ Processing Flow Details | Stage | Time | | ----------------------- | ----------- | | Webhook → Data capture | ~0s | | Email Verification | ~2–3s | | PDF Generation | ~4–6s | | Email Delivery | ~2–3s | | Total (Valid Email) | 8–15s ⚡ | | Invalid Email Path | 3–5s 🚀 | Customization Options Easy Customizations Email Templates:** Update HTML & university branding PDF Template:** Modify HTML (colors, fonts, fields) Error Messages:** Customize admin alerts Advanced Customizations Add Tracking:** Google Sheets or CRM Multi-Language Support:** Generate localized PDFs Extra Notifications:** Slack or SMS for staff CRM Integration:** Auto-push student data to Salesforce Troubleshooting | Issue | Cause | Solution | | -------------------- | ----------------------------- | ----------------------------- | | Email marked invalid | API key or quota issue | Check VerifiEmail dashboard | | PDF not generated | HTML error or expired API key | Validate HTML + check PDFMunk | | Email not sent | OAuth expired | Re-auth Gmail credential | | Webhook inactive | URL incorrect or workflow off | Activate + test via curl | Performance & Scalability | Metric | Current Capacity | | ---------------------- | --------------------------------- | | Concurrent Submissions | 10–20 | | Daily Volume | 500–1000 | | PDF Size | 100–500 KB | | Storage | Temporary (email attachment only) | Scaling Up Upgrade API tiers for high-volume admissions Add queue system or DB logging Validate large payloads & compress data Security & Privacy All API calls via HTTPS OAuth2 for Gmail authentication No student data stored post-execution Encrypted verification process Compliance GDPR compliant (minimal retention) Secure credential storage in n8n Full audit via execution logs License This template is provided as-is for commercial and personal use under the MIT License. An n8n automation workflow template by Jitesh Dugar.

By Jitesh Dugar

Startup Pitch Deck Submission Validator & Auto-Processor Overview A comprehensive n8n workflow template that completely automates the startup pitch deck submission process for accelerators, incubators, VC firms, and startup competitions. This workflow validates founder emails, stores pitch decks securely, generates professional PDF summaries, and sends notifications to both your team and the founders—all in under 30 seconds per submission. Key Features Email Verification & Spam Protection Real-time email validation** using VerifiEmail API Checks for RFC compliance, MX records, disposable emails, and spoofed addresses Automatically rejects invalid submissions before file storage Prevents spam, fake entries, and temporary email addresses Automated File Management Downloads pitch deck PDFs from provided URLs Uploads to organized Google Drive folders with automatic naming Creates two permanent archives: Original pitch decks in /PitchDecks/ Generated summaries in /Submission Summaries/ Maintains clean folder structure with timestamp-based filenames Professional PDF Reports Generates beautiful, branded PDF summary reports Includes company info, founder details, email verification status Professional gradient design with interactive elements Links to Google Drive documents for easy access Smart Email Notifications Admin Team Notification**: Comprehensive email with all details and clickable document links Founder Confirmation**: Professional thank-you email with next steps and timeline Invalid Submission Alerts**: Immediate notification for failed verifications with detailed reasons Intelligent Routing Conditional logic based on email validation results Valid submissions proceed through full workflow Invalid submissions trigger admin alerts and stop processing No wasted resources on fake submissions Error Handling Comprehensive error detection at every step Admin alerts for failed email verifications Graceful handling of file download failures Detailed logging for troubleshooting Perfect For Startup Accelerators** (Y Combinator, Techstars, 500 Startups style programs) Incubators & Innovation Hubs** Venture Capital Firms** (deal flow management) Pitch Competitions** (local, national, international events) Investment Rounds** (seed, Series A applications) Government Innovation Programs** Corporate Accelerators** University Entrepreneurship Programs** Workflow Statistics Total Nodes**: 11 Complexity**: ⭐⭐⭐ Medium Processing Time**: 15-30 seconds per submission Setup Time**: 15-20 minutes Code Required**: None (no-code solution) Maintenance**: Minimal (set and forget) Requirements Required Services & APIs VerifiEmail API Purpose: Email verification Sign up: https://verifi.email Google Drive Purpose: File storage Setup: Enable Drive API in Google Cloud Console Gmail Purpose: Email notifications Setup: Enable Gmail API in Google Cloud Console HTML to PDF API (pdfmunk.com) Purpose: PDF generation Sign up: https://pdfmunk.com Optional Integrations Typeform** - For frontend submission forms Google Forms** - Alternative form solution Webflow** - For custom landing pages Airtable** - For additional database logging Slack** - For team notifications What Gets Created Folder Structure in Google Drive My Drive/ ├── PitchDecks/ │ ├── TechVenture_JohnDoe_PitchDeck.pdf │ ├── AIStartup_JaneSmith_PitchDeck.pdf │ └── GreenTech_MikeJones_PitchDeck.pdf │ └── Submission Summaries/ ├── TechVenture_Summary_20251012_143025.pdf ├── AIStartup_Summary_20251012_145532.pdf └── GreenTech_Summary_20251012_151147.pdf Email Notifications Admin Team Email (to: accelerator@yourdomain.com) All startup details Founder information with verified email badge Clickable buttons to view pitch deck and summary Email verification breakdown (RFC, MX, disposable check) Google Drive folder structure overview Document IDs for reference Founder Confirmation (to: founder's email) Personalized thank you message Submission confirmation checklist Detailed submission summary table Clear next steps with timeline (5-7 day review) PDF summary attached for records Contact information for questions Invalid Email Alert (to: admin@yourdomain.com) Failed submission details Email verification failure reasons Timestamp for tracking Option for manual review Quick Start Guide 1. Import Template Download the JSON file In n8n: Workflows → Import from File Select: startup-pitch-deck-validator-template.json 2. Configure Credentials (15 minutes) A. VerifiEmail API Sign up at https://verifi.email Get API key from dashboard In n8n: Credentials → VerifiEmail API → Paste key B. Google Drive OAuth2 Go to https://console.cloud.google.com Create project → Enable Drive API Create OAuth 2.0 credentials In n8n: Credentials → Google Drive OAuth2 → Follow flow C. Gmail OAuth2 Same Google Cloud project Enable Gmail API In n8n: Credentials → Gmail OAuth2 → Authorize D. HTML to PDF API Sign up at https://pdfmunk.com Get API key In n8n: Credentials → HTML to PDF API → Paste key 3. Create Google Drive Folders Create these folders in your Google Drive: /PitchDecks/ (for original pitch decks) /Submission Summaries/ (for generated reports) Then select them in the workflow nodes. 4. Update Email Addresses Replace placeholder emails in these nodes: Notify Accelerator Team**: Change accelerator@yourdomain.com Alert Admin - Invalid Email**: Change admin@yourdomain.com Founder confirmation template**: Update support@youraccelerator.com 5. Test the Workflow Send a test webhook: curl -X POST https://your-n8n.com/webhook/startup-submission -H "Content-Type: application/json" -d '{ "name": "Jane Smith", "email": "jane@example.com", "startup_name": "TechVenture AI", "website": "https://techventure.io", "industry": "Artificial Intelligence", "pitch_deck_file_url": "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf" }' 6. Activate Workflow Click the toggle in top-right corner to activate! Detailed Setup Instructions Step 1: VerifiEmail Configuration Visit https://verifi.email and create account Navigate to API section in dashboard Copy your API key In n8n workflow, click "Verifi Email" node Create new credential → Paste API key Test credential to ensure it works Step 2: Google Cloud Project Setup Create Google Cloud Project Go to https://console.cloud.google.com Click "New Project" Name it: "n8n Startup Workflow" Click "Create" Enable Required APIs Go to "APIs & Services" → "Library" Search and enable: "Google Drive API" Search and enable: "Gmail API" Create OAuth Credentials Go to "APIs & Services" → "Credentials" Click "Create Credentials" → "OAuth 2.0 Client ID" Application type: "Web application" Add authorized redirect URI from n8n Download credentials JSON Configure in n8n In workflow, click any Google Drive node Create new credential → Google Drive OAuth2 Upload credentials JSON or paste values Complete OAuth flow and authorize Repeat for Gmail nodes using same project Step 3: Folder Setup Open Google Drive in browser Create folder: "PitchDecks" (note the folder ID from URL) Create folder: "Submission Summaries" In workflow, select these folders in the respective nodes: "Upload Pitch Deck to Drive" → PitchDecks folder "Save Summary PDF to Drive" → Submission Summaries folder Step 4: PDF API Setup Sign up at https://pdfmunk.com Get API key from account dashboard In "HTML to PDF" node, create new credential Paste API key Test with sample execution Step 5: Email Customization In "Notify Accelerator Team" node: Line 7: Change recipient email Update company name in footer (optional) In "Send Founder Confirmation" node: Line 69-70: Update support email Line 72: Update company name and year In "Alert Admin - Invalid Email" node: Line 3: Change recipient email Step 6: Test & Validate Test with Valid Email: Use your own email address Valid pitch deck URL Verify you receive confirmation email Check Google Drive for files Test with Invalid Email: Use temporary email service Verify admin receives alert Confirm no files are stored Test Error Handling: Use invalid file URL Check error messages Verify graceful failure Workflow DiagramStart → Webhook Trigger ↓ Email Verification (VerifiEmail API) ↓ Conditional Check (Valid?) ↙️ ↘️ TRUE FALSE ↓ ↓ Download PDF Alert Admin ↓ (end) Upload to Drive ↓ Generate Summary PDF ↓ Download Summary ↓ Save to Drive ↓ Notify Admin Team ↓ Confirm to Founder ↓ Done! ✅ Processing Flow Details For Valid Submissions (TRUE Branch): Webhook receives data → ~0s Email verification → ~2-3s Download pitch deck → ~3-5s Upload to Google Drive → ~2-3s Generate PDF summary → ~5-8s Download PDF → ~1-2s Save PDF to Drive → ~2-3s Send admin notification → ~2-3s Send founder confirmation → ~2-3s Total: 15-30 seconds For Invalid Submissions (FALSE Branch): Webhook receives data → ~0s Email verification → ~2-3s Send admin alert → ~2-3s Total: 4-6 seconds (saves resources!) Customization Options Easy Customizations Email Templates Modify HTML in Gmail nodes Add your logo Change colors and branding Adjust text and messaging PDF Template Edit HTML in "HTML to PDF" node Add custom styling Include additional fields Add company logo/branding Folder Structure Create subfolders by industry Add year-based organization Implement custom naming conventions Notification Preferences Add Slack notifications Set up SMS alerts Create calendar events Log to Airtable/database Advanced Customizations Add Duplicate Detection Check if email already submitted Prevent multiple submissions Create whitelist/blacklist Implement Scoring System Add rating fields to PDF Create evaluation criteria Automate preliminary screening Multi-Stage Workflow Add approval process Create interview scheduling Implement status updates Analytics & Reporting Track submission metrics Generate monthly reports Monitor email verification rates Analyze industry trends Troubleshooting Common Issues & Solutions 1. Email Verification Fails Problem**: All emails marked as invalid Solution**: Check VerifiEmail API key and quota 2. Google Drive Upload Error Problem**: "Insufficient permissions" error Solution**: Re-authorize OAuth, ensure Drive API enabled Check**: Folder exists and is accessible 3. PDF Generation Fails Problem**: PDF not generated or broken Solution**: Check HTML to PDF API key and quota Verify**: HTML template syntax is valid 4. Emails Not Sending Problem**: Gmail node fails Solution**: Re-authorize Gmail OAuth, check API quota Check**: Email addresses are valid format 5. File Download Fails Problem**: "Cannot fetch file from URL" Solution**: Verify URL is publicly accessible Check**: File exists and is not behind authentication 6. Webhook Not Triggering Problem**: No workflow execution Solution**: Check webhook URL is correct Verify**: Workflow is activated (toggle ON) Performance & Scalability Current Capacity Concurrent Submissions**: Up to 10-20 simultaneously Daily Volume**: ~500-1000 submissions (depends on API quotas) File Size Limit**: Up to 100MB per pitch deck Storage**: Unlimited (within Google Drive quota) Scaling Considerations For High Volume (1000+ submissions/day): Upgrade to paid API tiers Use queue system for processing Add database for tracking Implement rate limiting For Large Files (>100MB): Use direct file upload to Drive Skip PDF generation for large files Add file size validation Security & Privacy Data Protection Email verification via secure API Encrypted file transfer (HTTPS) OAuth2 authentication for Google services No data stored in n8n beyond execution logs Compliance GDPR compliant (data minimization) No sensitive data retention Secure credential storage Audit trail via execution logs Community Support n8n Forum: https://community.n8n.io Discord: https://discord.gg/n8n GitHub Issues: https://github.com/n8n-io/n8n 📄 License This template is provided as-is for commercial and personal use. An n8n automation workflow template by Jitesh Dugar.

By Jitesh Dugar

Personalized Promo Code Cards for Verified Users Overview This workflow automatically generates beautiful, personalized promotional cards with QR codes and sends them via email to verified users. Perfect for e-commerce stores, marketing campaigns, and customer engagement initiatives. Key Features Email Verification**: Validates email addresses using Verifi Email API to prevent fraud and ensure deliverability Dynamic Promo Cards**: Generates stunning, personalized promotional cards with custom discount codes and QR codes Automated Email Delivery**: Sends professionally designed HTML emails with embedded promo card images Real-time Logging**: Tracks all promo distributions in Google Sheets for monitoring and analytics Error Handling**: Includes error path for invalid emails with admin notifications Fully Customizable**: Easy to customize card design, email template, and discount values Workflow Process Webhook Trigger: Receives user data (name, email, promo_code, discount_value, discount_type) Data Processing: Formats and validates incoming data with default values Email Verification: Checks email validity using Verifi Email API Validation Gateway: Routes valid emails to generation or invalid to error path Card Generation: Creates personalized promo card image using HTML/CSS to Image API Email Delivery: Sends beautifully designed email with promo card via Gmail Logging: Records successful distributions in Google Sheets Error Notification: Sends admin alerts for failed attempts What's Included Beautiful Promo Card Design Gradient purple background (#667eea to #764ba2) Personalized greeting with customer name Prominent discount display in circular badge QR code for easy checkout redemption Validity date clearly shown Professional, mobile-responsive design Professional Email Template Engaging gradient header matching promo card Highlighted promo code section with dashed border Three feature icons (Easy to Use, Exclusive Deal, Limited Time) Call-to-action button Embedded promo card image Clean footer with expiry and contact info Required Integrations & APIs 1. Verifi Email API Purpose**: Email verification and validation Get API Key**: https://verifi.email Setup**: Sign up → Generate API key → Add to workflow credentials 2. HTML/CSS to Image API Purpose**: Convert HTML promo card to PNG image Get API Key**: https://htmlcsstoimg.com Setup**: Create account → Copy API key → Configure in workflow 3. Gmail API (OAuth2) Purpose**: Send personalized promo emails Get Credentials**: https://console.cloud.google.com/ Setup Steps**: Create new project Enable Gmail API Create OAuth 2.0 Client ID Add credentials to n8n 4. Google Sheets API Purpose**: Log promo distributions for tracking Get Credentials**: https://console.cloud.google.com/ Setup Steps**: Enable Google Sheets API Create Service Account (or use OAuth2) Share your Google Sheet with the service account email Add credentials to n8n Quick Start Guide Step 1: Import the Workflow Copy the workflow JSON Go to n8n dashboard Click "Import from File" or "Import from URL" Paste the workflow Step 2: Configure Credentials Set up the following credentials in n8n: Verifi Email API credentials HTML/CSS to Image API credentials Gmail OAuth2 credentials Google Sheets credentials Step 3: Create Google Sheet Create a new Google Sheet Add headers: Timestamp, Name, Email, Promo Code, Discount Value, Status Share with your service account (if using service account auth) Copy the Sheet ID and update in the workflow Step 4: Customize Settings QR Code URL**: Update the checkout URL in the promo card HTML (line with YOURSTORE.com) Admin Email**: Change admin notification email in the "Error Path" node Validity Date**: Update expiry date in both promo card and email template Colors/Design**: Customize gradient colors and styling as needed Step 5: Test the Workflow Activate the workflow Copy the webhook URL Send a POST request with test data: { "name": "John Doe", "email": "john@example.com", "promo_code": "SAVE20", "discount_value": "20%", "discount_type": "percentage" } Input Parameters Send a POST request to the webhook with the following JSON body: { "name": "Customer Name", // Optional: defaults to "Valued Customer" "email": "customer@example.com", // Required: customer email address "promo_code": "SUMMER25", // Optional: defaults to "WELCOME10" "discount_value": "25%", // Optional: defaults to "10%" "discount_type": "percentage" // Optional: defaults to "percentage" } Use Cases E-commerce Welcome offers for new customers Abandoned cart recovery with discount codes Birthday/anniversary promotions Loyalty rewards for repeat customers Marketing Campaigns Seasonal sale promotions Referral program rewards Social media contest prizes Email list incentives Customer Engagement Re-engagement campaigns VIP member benefits Event registration perks Survey completion rewards Customization Options Promo Card Design Modify colors and gradients in the HTML/CSS Change logo/emoji in the header Adjust card dimensions and layout Customize QR code size and styling Update validity date format Email Template Change email subject line Modify header text and styling Add company branding/logo Customize CTA button text and link Update footer information Business Logic Add conditional discounts based on user tier Implement time-based validity Add product-specific promo codes Include multiple discount tiers Add custom validation rules Monitoring & Analytics The workflow automatically logs: Timestamp of each promo distribution Customer name and email Promo code assigned Discount value Distribution status (Success/Failed) Use this data to: Track campaign performance Monitor redemption rates Identify popular discount amounts Analyze email delivery success Debug failed attempts Troubleshooting Common Issues Email not sending: Verify Gmail API credentials are correct Check OAuth2 token hasn't expired Ensure Gmail account has proper permissions Image not generating: Confirm HTML/CSS to Image API key is valid Check API usage limits haven't been exceeded Verify HTML syntax is correct Email validation failing: Ensure Verifi Email API credentials are active Check API rate limits Verify email format in incoming data Google Sheets not updating: Confirm Sheet ID is correct Check service account has edit permissions Verify sheet name matches configuration Pro Tips Test with Invalid Emails: Try sending to invalid emails to verify error handling works Monitor API Limits: Keep track of API usage to avoid hitting rate limits A/B Test Designs: Create multiple card variations to see which performs better Personalize Further: Add more custom fields like user tier, purchase history, etc. Schedule Reports: Create a companion workflow to send daily/weekly promo distribution reports Performance Metrics Processing Time**: 30-60 seconds per request Success Rate**: 95%+ for valid email addresses Scalability**: Handles hundreds of requests per hour Error Recovery**: Automatic admin notifications for failures Security & Privacy Email validation prevents spam and fraud No sensitive data stored in workflow All API credentials encrypted in n8n Google Sheets logging can be disabled if needed Compliant with email marketing best practices Best Practices Email Deliverability: Always validate emails before sending Rate Limiting: Implement delays for bulk sends to avoid spam filters Personalization: Use customer names and relevant discount amounts Clear CTAs: Make it easy for customers to redeem their codes Tracking: Monitor distribution and redemption metrics Testing: Always test with real emails before launching campaigns 📄 License This workflow template is provided as-is for use in your n8n instance. Feel free to customize and adapt to your specific needs. Why Use This Workflow? ✅ Saves Time: Automates entire promo distribution process ✅ Reduces Errors: Email validation prevents bounce rates ✅ Professional Output: Beautiful, branded promo cards ✅ Easy Tracking: Real-time logging in Google Sheets ✅ Scalable: Handles high volume campaigns ✅ Customizable: Easy to adapt to your brand ✅ Cost-Effective: Uses affordable or free tier APIs Perfect for marketers, e-commerce managers, and anyone looking to automate personalized promotional campaigns!. An n8n automation workflow template by Jitesh Dugar.

By Oneclick AI Squad

Enhance your hiring pipeline by automating interview management post-screening. This workflow runs every 5 minutes to scan upcoming Google Calendar events, filter relevant interviews, send timely email reminders to candidates and internal teams, and handle result submissions via webhook — updating statuses in Google Sheets and notifying via Gmail based on pass/fail outcomes. Ensure no interviews slip through the cracks with proactive reminders and instant feedback loops. What This Template Does Step 1: Triggers every 5 minutes to proactively check for upcoming interviews. Step 2: Fetches all Google Calendar Events and identifies interview-related ones. Step 3: Filters Upcoming Interviews based on event details (e.g., candidate name, role). Step 4: Sends Reminder Emails to candidates and interviewers via Gmail for preparation. Step 5: Receives Webhook Submission of interview results (pass/fail) post-event. Step 6: Updates Google Sheet with result data, including feedback and updated status. Step 7: Branches on result:   → Passed: Sends congratulatory Email to Candidate and advances status.   → Failed: Sends polite Failure Notification and closes the loop. Key Benefits ✅ Reduces no-shows with automated reminders ✅ Centralizes interview tracking in Google Sheets ✅ Instant Gmail notifications for pass/fail decisions ✅ Minimizes manual status updates ✅ Improves candidate experience with timely communication ✅ Ensures audit-ready logs of all interactions Features Cron-triggered checks every 5 minutes Google Calendar integration for event fetching Smart filtering for interview-specific events Gmail-powered reminder and notification emails Webhook for secure result submissions Conditional branching on pass/fail Real-time Google Sheets append/update Comprehensive sheet structure for tracking Requirements GOOGLE_SHEET_ID**: Your Google Sheet ID (structured as below) Credentials Needed:** Google Calendar OAuth2 Gmail API Key Customize:** • Event filter criteria (e.g., keywords like "Interview") • Reminder timing (e.g., 24 hours before) • Email templates for reminders and results • Webhook endpoint for result submission Google Sheet Structure: Create a sheet with columns: Candidate Email Interview Link Status Result Meet Link Feedback Updated At Target Audience Recruiters juggling multiple interview schedules 🗓️ HR teams focused on candidate engagement 💬 Hiring managers needing quick result turnarounds ⚡ Growing companies scaling interview volumes 📈 Remote teams relying on calendar and email sync 🌐 Step-by-Step Setup Instructions Set up Google Sheet  → Create sheet with the specified columns: Candidate Email, Interview Link, Status, Result, Meet Link, Feedback, and Updated At.  → Replace YOUR_SHEET_ID in the workflow with your actual Sheet ID. Configure Calendar Integration  → Connect Google Calendar OAuth2 and select the relevant calendar (e.g., hiring@company.com). Define Event Filters  → In the "Filter Upcoming Interviews" node, set keywords (e.g., "Candidate Interview") to match event titles/descriptions. Customize Reminders  → Edit the "Send Reminder to Candidate" template (e.g., include interview link and prep tips).  → Set reminder offset (e.g., 1 day before event). Set Up Webhook for Results  → Generate and expose the webhook URL for your interview form/tool to submit pass/fail data. Connect Gmail  → Enable Gmail OAuth2.  → Define sender email and customize pass/fail templates. Test the Flow  → Create a test calendar event for an upcoming interview.  → Wait 5 minutes or trigger manually → Verify reminder email.  → Submit test webhook result → Check sheet update and notification email. Go Live  → Enable the 5-minute cron trigger.  → Monitor sheet for real entries on Thursday, October 23, 2025, or your next interview day. An n8n automation workflow template by Oneclick AI Squad.

By Oneclick AI Squad

Streamline your hiring process with intelligent AI-powered candidate screening and automated interview scheduling. This workflow receives applications via webhook, evaluates candidates using OpenAI's GPT model, scores them against job requirements, stores data in Google Sheets, and automatically schedules interviews for high-scoring candidates — all while sending personalized email notifications and updating statuses in real time. Reduce manual screening time and ensure only top candidates move forward. 🤖📧 What This Template Does Step 1: Triggers on new application submission via Webhook (e.g., from job portal or form). Step 2: Stores applicant data (resume, contact, role) into Google Sheets for centralized tracking. Step 3: Uses OpenAI GPT to evaluate candidate fit based on resume, skills, and job requirements. Step 4: Applies Scoring Logic:   • Score ≥ 70 → Qualified for interview   • Score < 70 → Not a fit Step 5: Branches based on score:   → High Score Path:    • Sends Interview Invitation Email    • Creates Google Calendar Event    • Updates Sheet: Status → “Interview Scheduled”   → Low Score Path:    • Sends Polite Rejection Email    • Updates Sheet: Status → “Rejected” Step 6: Final metrics logged and webhook response confirms completion. Key Benefits ✅ Eliminates manual resume screening ✅ AI evaluates candidates consistently and objectively ✅ Automates interview scheduling with calendar integration ✅ Real-time status updates in Google Sheets ✅ Personalized email communication at every stage ✅ Full audit trail of decisions and actions Features Webhook-triggered application intake Google Sheets as applicant tracking system (ATS) OpenAI GPT-powered candidate evaluation Dynamic scoring threshold (customizable) Conditional branching (High/Low Score) Gmail integration for email notifications Google Calendar auto-event creation Real-time status updates via sheet write-back Final webhook response for system confirmation Requirements GOOGLE_SHEET_ID**: Your Google Sheet ID Credentials Needed:** Google Sheets OAuth2 Gmail API Key OpenAI API Key Google Calendar OAuth2 Customize:** • Job requirements & AI prompt • Score threshold (currently 70) • Email templates • Interview scheduling time slots Target Audience HR teams managing high-volume applications 👥 Recruiters seeking faster shortlisting ⏱️ Startups automating early-stage hiring 🚀 Tech companies with technical screening needs 💻 Remote-first organizations using digital workflows 🌍 Step-by-Step Setup Instructions Set up Google Sheet  → Create a sheet with columns: Name, Email, Resume Link, Role, Status, Score, Timestamp  → Replace YOUR_SHEET_ID in the workflow with your actual Sheet ID. Configure Webhook  → Connect your job application form (e.g., Typeform, LinkedIn, custom portal) to trigger this workflow. Add OpenAI API Key  → Insert your OpenAI key and customize the evaluation prompt under “AI Evaluation” node. Set Scoring Threshold  → Adjust the “IF – Check Score Threshold” node (default: ≥70 = pass). Connect Gmail & Calendar  → Enable Gmail OAuth2 and Google Calendar OAuth2.  → Define interviewer email and default interview duration. Customize Emails  → Edit “Interview Invitation” and “Rejection Notice” templates with your branding. Test the Flow  → Submit a test application via webhook.  → Verify: Sheet update → AI score → Email → Calendar event → Status change. Go Live  → Enable automation. Monitor first few runs in Google Sheets. Workflow Complete! Now sit back as AI screens, scores, schedules, and communicates — all without lifting a finger. Metrics to Track: Applications received Average AI score Interview rate Time to process. An n8n automation workflow template by Oneclick AI Squad.

By Intuz

Quick overview This workflow lets users upload PDFs or ask questions in Telegram, indexes PDF content in Pinecone using Google Gemini embeddings, and answers follow-up questions with a Google Gemini chat model using retrieval-augmented generation formatted for Telegram HTML. How it works Triggers when a new Telegram message is received by your bot. Checks whether the message includes a document; if it does, it downloads the file from Telegram and forces the binary metadata to application/pdf. Splits the PDF text into overlapping chunks, generates embeddings with Google Gemini, and inserts the vectors into a Pinecone index. Sends a Telegram confirmation message indicating how many PDF pages were saved to Pinecone. If the message is a text question, retrieves relevant context from the Pinecone index and uses the Google Gemini chat model to generate an answer constrained to that context. Sends the generated answer back to Telegram using HTML parse mode formatting. Setup Create a Telegram bot with BotFather and add Telegram credentials in n8n for the Telegram Trigger and Telegram nodes. Add a Google Gemini (PaLM) API credential for both the embeddings and chat model nodes. Set up a Pinecone account, create (or select) an index named telegram, and add your Pinecone credentials in n8n. Activate the workflow and start a chat with your Telegram bot to upload a PDF for indexing and then send text questions to query it. Requirements n8n Instance & Required Nodes: An active n8n account (Cloud or self-hosted). Telegram Account: A Telegram bot created via the BotFather, along with its API token. Google Gemini AI Account: A Google Cloud account with the Vertex AI API enabled and an associated API Key. Pinecone Account: A Pinecone account with an API key. Additional info Connect with us: Website: https://www.intuz.com/n8n-workflow-automation-templates/ Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz For Custom Workflow Automation Get Started: https://n8n.partnerlinks.io/intuz. An n8n automation workflow template by Intuz.

By gotoHuman

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality. An n8n automation workflow template by gotoHuman.

By Habeeb Mohammed

Who's it for This workflow is perfect for individuals who want to maintain detailed financial records without the overhead of complex budgeting apps. If you prefer natural language over data entry forms and want an AI assistant to handle the bookkeeping, this template is for you. It's especially useful for: People who want to track cash and online transactions separately Anyone who lends money to friends/family and needs debt tracking Users comfortable with Slack as their primary interface Those who prefer conversational interactions over manual spreadsheet updates What it does This AI-powered finance tracker transforms your Slack workspace into a personal finance command center. Simply mention your bot with transactions in plain English (e.g., "₹500 cash food, borrowed ₹1000 from John"), and the AI agent will: Parse transactions using natural language understanding via Google Gemini Calculate balance changes for cash and online accounts Show a preview of changes before saving anything Update Google Sheets only after you approve Track debts (who owes you, who you owe, repayments) Send daily reminders at 11 PM with current balances and active debts The workflow maintains conversational context using PostgreSQL memory, so you can say things like "yesterday's transactions" or "that payment to Sarah" and it understands the context. How it works Scheduled Daily Check-in (11 PM) Fetches current balances from Google Sheets Retrieves all active debts Formats and sends a Slack message with balance summary Prompts you to share the day's transactions AI Agent Transaction Processing When you mention the bot in Slack: Phase 1: Parse & Analyze Extracts amount, payment type (cash/online), category (food, travel, etc.) Identifies transaction type (expense, income, borrowed, lent, repaid) Stores conversation context in PostgreSQL memory Phase 2: Calculate & Preview Reads current balances from Google Sheets Calculates new balances based on transactions Shows formatted preview with projected changes Waits for your approval ("yes"/"no") Phase 3: Update Database (only after approval) Logs transactions with unique IDs and timestamps Updates debt records with person names and status Recalculates and stores new balances Handles debt lifecycle (Active → Settled) Phase 4: Confirmation Sends success message with updated balances Shows active debts summary Includes logging timestamp Requirements Essential Services: n8n instance (self-hosted or cloud) Slack workspace with admin access Google account Google Gemini API key PostgreSQL database Recommended: Claude AI model (mentioned in workflow notes as better alternative to Gemini) How to set up 1. Google Sheets Setup Create a new Google Sheet with three tabs named exactly: Balances Tab: | Date | Cash_Balance | Online_Balance | Total_Balance | |------|--------------|----------------|---------------| Transactions Tab: | Transaction_ID | Date | Time | Amount | Payment_Type | Category | Transaction_Type | Person_Name | Description | Added_At | |----------------|------|------|--------|--------------|----------|------------------|-------------|-------------|----------| Debts Tab: | Person_Name | Amount | Type | Date_created | Status | Notes | |-------------|--------|------|--------------|--------|-------| Add header rows and one initial balance row in the Balances tab with today's date and starting amounts. 2. Slack App Setup Go to api.slack.com/apps and create a new app Under OAuth & Permissions, add these Bot Token Scopes: app_mentions:read chat:write channels:read Install the app to your workspace Copy the Bot User OAuth Token Create a dedicated channel (e.g., #personal-finance-tracker) Invite your bot to the channel 3. Google Gemini API Visit ai.google.dev Create an API key Save it for n8n credentials setup 4. PostgreSQL Database Set up a PostgreSQL database (you can use Supabase free tier): Create a new project Note down connection details (host, port, database name, user, password) The workflow will auto-create the required table 5. n8n Workflow Configuration Import the workflow and configure: A. Credentials Google Sheets OAuth2**: Connect your Google account Slack API**: Add your Bot User OAuth Token Google Gemini API**: Add your API key PostgreSQL**: Add database connection details B. Update Node Parameters All Google Sheets nodes: Select your finance spreadsheet Slack nodes: Select your finance channel Schedule Trigger: Adjust time if you prefer a different check-in hour (default: 11 PM) Postgres Chat Memory: Change sessionKey to something unique (e.g., finance_tracker_your_name) Keep tableName as n8n_chat_history_finance or rename consistently C. Slack Trigger Setup Activate the "Bot Mention trigger" node Copy the webhook URL from n8n In Slack App settings, go to Event Subscriptions Enable events and paste the webhook URL Subscribe to bot event: app_mention Save changes 6. Test the Workflow Activate both workflow branches (scheduled and agent) In your Slack channel, mention the bot: @YourBot ₹100 cash snacks Bot should respond with a preview Reply "yes" to approve Verify Google Sheets are updated How to customize Change Transaction Categories Edit the AI Agent's system message to add/remove categories. Current categories: travel, food, entertainment, utilities, shopping, health, education, other Modify Daily Check-in Time Change the Schedule Trigger's triggerAtHour value (0-23 in 24-hour format). Add Currency Support Replace ₹ with your currency symbol in: Format Daily Message code node AI Agent system prompt examples Switch AI Models The workflow uses Google Gemini, but notes recommend Claude. To switch: Replace "Google Gemini Chat Model" node Add Claude credentials Connect to AI Agent node Customize Debt Types Modify AI Agent's system prompt to change debt handling logic: Currently: I_Owe and They_Owe_Me You can add more types or change naming Add More Payment Methods Current: cash, online To add more (e.g., credit card): Update AI Agent prompt Modify Balances sheet structure Update balance calculation logic Change Approval Keywords Edit AI Agent's Phase 2 approval logic to recognize different approval phrases. Add Spending Analytics Extend the daily check-in to calculate: Weekly/monthly spending summaries Category-wise breakdowns Use additional Code nodes to process transaction history Important Notes ⚠️ Never trigger with normal messages - Only use app mentions (@botname) to avoid infinite loops where the bot replies to its own messages. 💡 Context Awareness - The bot remembers conversation history, so you can reference "yesterday", "last week", or previous transactions naturally. 🔒 Data Privacy - All your financial data stays in your Google Sheets and PostgreSQL database. The AI only processes transaction text temporarily. 📊 Backup Regularly - Export your Google Sheets periodically as backup. Pro Tips: Start with small test transactions to ensure everything works Use consistent person names for debt tracking The bot understands various formats: "₹500 cash food" = "paid 500 rupees in cash for food" You can batch transactions in one message: "₹100 travel, ₹200 food, ₹50 snacks". An n8n automation workflow template by Habeeb Mohammed.

By Javier Rieiro

Description Automates daily CVE-driven scanning against bug bounty scopes. It fetches bug-bounty domains, pulls newly published Project Discovery templates, converts them to Nuclei rules, runs targeted scans, and emails findings. Objective Help security researchers and bug bounty hunters discover exploitable instances quickly by automatically running the latest public templates from Project Discovery against a consolidated bug-bounty scope. Reduce manual steps and maintain continuous reconnaissance. How it works The workflow accepts or fetches a domain list that covers HackerOne, Bugcrowd, Intigriti, and YesWeHack. It downloads the latest public templates from Project Discovery. For each new template published since the last run it: creates a file, uploads it to a remote host, and converts it to a Nuclei-compatible YAML. It uploads a consolidated domains wordlist to the remote host. It executes Nuclei with the new templates against the domains list using configured flags (concurrency, rate limits, severity tags). It collects and deduplicates Nuclei output. If results exist, it sends the findings via Gmail. Requirements • SSH access (root or equivalent) to a VPS or host. • Nuclei installed on the remote host. • Gmail OAuth2 credentials for sending notifications. • Recommended: VPS with enough CPU and network capacity for concurrent scanning when scope is large. An n8n automation workflow template by Javier Rieiro.

By Automate With Marc

## Podcast on Autopilot — Generate Podcast Ideas, Scripts & Audio Automatically with Eleven Labs, GPT-5 and Claude Sonnet 4.0 Bring your solo podcast to life — on full autopilot. This workflow uses GPT-5 and Claude Sonnet to turn a single topic input into a complete podcast episode intro and ready-to-send audio file. How it works Start a chat trigger – enter a seed idea or topic (e.g., “habits,” “failure,” “technology and purpose”). Podcast Idea Agent (GPT-5) instantly crafts a thought-provoking, Rogan- or Bartlett-style episode concept with a clear angle and takeaway. Podcast Script Agent (Claude 4.0 Sonnet) expands that idea into a natural, engaging 60-second opening monologue ready for recording. Text-to-Speech via ElevenLabs automatically converts the script into a high-quality voice track. Email automation sends the finished MP3 directly to your inbox. Perfect for • Solo creators who want to ideate, script and voice short podcasts effortlessly • Content teams prototyping daily or weekly audio snippets • Anyone testing AI-driven storytelling pipelines Customization tips • Swap ElevenLabs with your preferred TTS service by editing the HTTP Request node. • Adjust prompt styles for tone or audience in the Idea and Script Agents. • Modify the Gmail (or other mail service) node to send audio to any destination (Drive, Slack, Notion, etc.). • For reuse at scale, add variables for episode number, guest name, or theme category — just clone and update the trigger node. Watch step-by-step tutorial (how to build it yourself) https://www.youtube.com/watch?v=Dan3_W1JoqU Requirements & disclaimer • Requires API keys for OpenAI + Anthropic + ElevenLabs (or your chosen TTS). • You’re responsible for managing costs incurred through AI or TTS usage. • Avoid sharing sensitive or private data as input into prompt flows. • Designed with modularity so you can turn off or swap/deep-link any stage (idea → script → voice → email) without breaking the chain. An n8n automation workflow template by Automate With Marc.

By Adrian Kendall

Key Features Implements a simple round-robin distribution mechanism using a Data Table to track the last route used. Supports multiple downstream workflows or resources, balancing workload across them sequentially. Uses Switch and Code nodes for flexible routing logic. Designed for easy customization — replace placeholder “Route” nodes with sub-workflow calls or API triggers. Works with any trigger type, and includes merge logic to preserve input data. Nodes in Use | Node Name | Type | Purpose | |-------------------------------------------------|---------------|--------------------------------------------------------------------------| | When clicking ‘Execute workflow’ | Manual Trigger | Test entry point for manual execution. | | Calculate the next route to use | Data Table | Retrieves the last used route number. | | Code in JavaScript | Code | Increments the route counter (0–3 cycle). | | Update last_used in the datatable | Data Table | Updates the “Last_Used” field to track next route. | | Round Robin Router | Switch | Routes workflow execution to the correct path based on Last_Used value. | | Route 1 / Route 2 / Route 3 | NoOp | Placeholder routes — replace with your own workflows. | | Merge trigger data to pass to subworkflow if needed | Merge | Combines trigger data with routing data for sub-workflows. | | Sticky Notes | Annotations | Explain workflow logic and intended replacements. | How It Works The workflow starts when triggered manually (or by another workflow). The Data Table node fetches the current value of Last_Used, which identifies which route was last used. The Code node increments that value, resetting to 0 after 3, creating a round-robin cycle. The Data Table update node stores the new Last_Used value. The Switch node reads Last_Used and routes execution to the correct downstream branch. Each route can represent a duplicated workflow, resource, or API endpoint. Optionally, the Merge node reattaches trigger data before sending it to sub-workflows. Step-by-Step Trigger the workflow manually or via webhook/cron/etc. Retrieve current route index using the Data Table node. Increment route counter with the JavaScript Code node: If Last_Used = 3, it resets to 0. Otherwise, increments by 1. Update Data Table with the new Last_Used value. Route execution using the Switch node based on that value. Send data to corresponding subworkflow (Route 1, Route 2, Route 3). Replace the NoOp nodes with your target workflow or HTTP call nodes for real routing. Use Cases Distribute load across multiple API endpoints to prevent throttling. Run identical sub-workflows on different worker instances for parallel processing. Simulate load balancing during testing of N8N workflows. Sequentially alternate between external systems or servers handling similar tasks. Act as a proof-of-concept for balancing strategies before scaling up. An n8n automation workflow template by Adrian Kendall.

By Dahiana

Description Who's it for: Content creators, marketers, and businesses who publish on both YouTube and blog platforms. What it does: Monitors your YouTube channel for new videos and automatically creates SEO-optimized blog posts using AI, then publishes to WordPress or Webflow. How it works: RSS Feed Trigger polls YouTube videos (every X amount of time) Extracts video metadata (title, description, thumbnail) YouTube node extracts full description for extra context Uses OpenAI (you can choose any model) to generate 600-800 word blog post Publishes to WordPress AND/OR Webflow with error handling Sends notifications to Telegram if publishing fails Requirements: YouTube channel ID (avoid tutorial channels for better results) OpenAI API key (or similar) WordPress OR Webflow credentials Telegram bot (optional, for error notifications) Setup steps: Replace YOUR_CHANNEL_ID in RSS Feed Trigger Add OpenAI credentials in AI generation node Configure WordPress and/or Webflow credentials Add Telegram bot for error notifications (optional). If you choose to set up Telegram, you need to input your channel ID. Test with manual execution first Customization: Modify AI prompt for different content styles Adjust polling frequency (30-60 minutes recommended) Add more CMS platforms Add content verification (is content larger than 600 characters? if not, improve). An n8n automation workflow template by Dahiana.

By Convosoft

Generate Secure User Authentication with One Webhook Streamline user onboarding and security for your applications using this n8n workflow. This template handles signup, login, and password resets through a single endpoint, making it ideal for developers building MVPs or scaling apps without a full authentication backend. Who Is This For? This workflow is designed for: Developers, indie hackers, and teams building web, mobile, or API-driven applications. Those who need a quick and secure authentication layer. Anyone tired of writing custom auth code or managing third-party services like Auth0 for simple needs. This template integrates seamlessly into your n8n setup. What Problem Does This Workflow Solve? Building authentication from scratch is time-consuming and complex: User Management: Managing registration, credential verification, and password recovery can take weeks of development time. Security: Ensuring secure password hashing, case-insensitive email matching, and robust error handling adds significant complexity. Integration: Creating consistent APIs for apps (e.g., React Native, Next.js, Flutter) is challenging. This workflow provides a battle-tested, webhook-based authentication system that is: Database-agnostic (works with PostgreSQL/Supabase). Extensible—deploy once and integrate across all your apps. What This Workflow Does The workflow handles authentication tasks through a single webhook endpoint, offering the following functionality: Webhook Entry: Listens for POST requests at /webhook/auth. Processes a simple JSON payload, routing actions via a "path" parameter (signup, signin, forgot). Signup: Inserts new users into your database. Uses bcrypt-hashed passwords (via pgcrypto). Returns user details in the response. Login: Queries for case-insensitive email matches. Verifies passwords securely. Returns user information on successful login. Forgot Password: Generates a random 8-character password. Updates the password hash in the database. Returns the new password (suitable for email delivery). Routing & Validation: Uses n8n Switch and IF nodes to securely handle paths and credentials. Standardized Responses: Outputs clean JSON with status, message, and data for easy frontend parsing. Error Handling: Gracefully manages invalid inputs, duplicate entries, or database errors. No more boilerplate—get authentication up and running in minutes! Setup Instructions Follow these steps to set up the workflow: Connect Your Accounts: Use PostgreSQL or Supabase for user storage (free tiers are sufficient). Enable the following PostgreSQL extensions: uuid-ossp and pgcrypto. Create the Users Table: sqlCREATE TABLE users ( id uuid PRIMARY KEY DEFAULT uuid_generate_v4(), full_name text NOT NULL, email text UNIQUE NOT NULL, password_hash text NOT NULL, created_at timestamptz DEFAULT now() ); Configure Credentials : Add PostgreSQL credentials to the n8n nodes ("Signup", "Login", "Reset Password"). Import the JSON workflow into n8n. Activate the workflow. Test the Workflow: Use Postman or curl to send requests to the auto-generated webhook URL. How to Customize This Workflow Extend the workflow to fit your specific needs with these modifications: Add JWT Sessions: Insert a node after successful login to generate and sign JWT tokens (e.g., using the Crypto node). Email Integration: Add a SendGrid or Mailgun node to the "Forgot Password" flow to automatically send new credentials. Rate Limiting: Include an HTTP Request node to check usage quotas before processing requests. Multi-Database Support: Replace PostgreSQL with MySQL or MongoDB by updating the query nodes. Frontend Enhancements: Extend JSON responses to include user avatars or roles by joining additional tables in SQL queries. Triggers: Add a Schedule node for batch user imports. Include a webhook for external authentication calls. An n8n automation workflow template by Convosoft.

By Abhiman Sundararajan

Short description Transcribe Telegram voice/audio messages to text using Groq’s OpenAI-compatible Whisper endpoint. Replies are delivered either as a Telegram message or as a downloadable .txt file, plug-and-play for n8n with minimal setup. Who’s it for / Uses Educators, podcasters, interviewers, and support teams who need quick voice → text conversions. Automating meeting notes, voice feedback, voicemail transcription, or speech logging. Useful when you want transcripts pushed to chat or saved as files for archiving. How it works (overview) Telegram Trigger — workflow starts on incoming message. Switch (Audio/Voice) — detects voice or audio. If neither, replies “Wrong file type” and stops. Telegram Download — downloads the audio using the file_id, outputs file path/binary. Set Node (credentials + options) — stores Groq_API and Telegram_access_token (required) and transcript_output_format (message or file). HTTP Request → Groq (Whisper) — uploads audio (multipart/form-data) to Groq’s transcription endpoint and receives text. Reply Switch — routes to either: Message branch: send transcribed text as a Telegram message. File branch: convert transcript to .txt and send as a document. Requirements n8n instance (cloud or self-hosted) with internet access Telegram bot token (create via BotFather) Groq API key (create at https://console.groq.com/keys) Basic n8n nodes: Telegram Trigger, Switch, Telegram Download, Set, HTTP Request, Convert to File, Telegram Send Message/Document Important setup & notes Mandatory:* Add Groq_API and Telegram_access_token in the *Set** node (or use n8n Credentials). The workflow will fail without them. Do not hardcode** keys in HTTP node fields that will be exported/shared. Use Set fields or n8n Credentials. Include sticky notes explaining each node (yellow note with full description recommended). Sticky notes should show setup steps and required fields. Before publishing: remove personal IDs and secrets, test with sample voice messages, and verify Groq response schema to map the transcript field correctly. Security & best practices Use n8n Credentials or environment variables in production. Rotate API keys if they become exposed. Keep the Set node private when sharing templates; instruct users to replace keys with their own. An n8n automation workflow template by Abhiman Sundararajan.

By Piotr Sikora

Who’s it for This workflow is perfect for content managers, SEO specialists, and website owners who want to easily analyze their WordPress content structure. It automatically fetches posts, categories, and tags from a WordPress site and exports them into a Google Sheet for further review or optimization. What it does This automation connects to the WordPress REST API, collects data about posts, categories, and tags, and maps the category and tag names directly into each post. It then appends all this enriched data to a Google Sheet — providing a quick, clean way to audit your site’s content and taxonomy structure. How it works Form trigger: Start the workflow by submitting a form with your website URL and the number of posts to analyze. Fetch WordPress data: The workflow sends three API requests to collect posts, categories, and tags. Merge data: It combines all the data into one stream using the Merge node. Code transformation: A Code node replaces category and tag IDs with their actual names. Google Sheets export: Posts are appended to a Google Sheet with the following columns: URL Title Categories Tags Completion form: Once the list is created, you’ll get a confirmation message and a link to your sheet. If the WordPress API isn’t available, the workflow automatically displays an error message to help you troubleshoot. Requirements A WordPress site with the REST API enabled (/wp-json/wp/v2/). A Google account connected to n8n with access to Google Sheets. A Google Sheet containing the columns: URL, Title, Categories, Tags. How to set up Import this workflow into n8n. Connect your Google Sheets account under credentials. Make sure your WordPress site’s API is accessible publicly. Adjust the Post limit (per_page) in the form node if needed. Run the workflow and check your Google Sheet for results. How to customize Add additional WordPress endpoints (e.g., authors, comments) by duplicating and modifying HTTP Request nodes. Replace Google Sheets with another integration (like Airtable or Notion). Extend the Code node to include SEO metadata such as meta descriptions or featured images. An n8n automation workflow template by Piotr Sikora.

By Jameson Kanakulya

Overview This automated workflow intelligently qualifies interior design leads, generates personalized client emails, and manages follow-up through a human-approval process. Built with n8n, Claude AI, Telegram approval, and Notion database integration. ⚠️ Hosting Options This template works with both n8n Cloud and self-hosted instances. Most nodes are native to n8n, making it cloud-compatible out of the box. What This Template Does Automated Lead Management Pipeline: Captures client intake form submissions from website or n8n forms AI-powered classification into HOT/WARM/COLD categories based on budget, project scope, and commitment indicators Generates personalized outreach emails tailored to each lead type Human approval workflow via Telegram for quality control Email revision capability for rejected drafts Automated client email delivery via Gmail Centralized lead tracking in Notion database Key Features ✅ Intelligent Lead Scoring: Analyzes 12+ data points including budget (AED), space count, project type, timeline, and style preferences ✅ Personalized Communication: AI-generated emails reference specific client details, demonstrating genuine understanding ✅ Quality Control: Human-in-the-loop approval via Telegram prevents errors before client contact ✅ Smart Routing: Different workflows for qualified leads (meeting invitations) vs. unqualified leads (respectful alternatives) ✅ Revision Loop: Rejected emails automatically route to revision agent for improvements ✅ Database Integration: All leads stored in Notion for pipeline tracking and analytics Use Cases Interior design firms managing high-volume lead intake Architecture practices with complex qualification criteria Home renovation companies prioritizing project value Any service business requiring budget-based lead scoring Sales teams needing approval workflows before client contact Prerequisites Required Accounts & API Keys: Anthropic Claude API - For AI classification and email generation Telegram Bot Token - For approval notifications Gmail Account - For sending client emails (or any SMTP provider) Notion Account - For lead database storage n8n Account - Cloud or self-hosted instance Technical Requirements: Basic understanding of n8n workflows Ability to create Telegram bots via BotFather Gmail app password or OAuth setup Notion database with appropriate properties Setup Instructions Step 1: Clone and Import Template Copy this template to your n8n instance (cloud or self-hosted) All nodes will appear as inactive - this is normal Step 2: Configure Form Trigger Open the Client Intake Form Trigger node Choose your trigger type: For n8n forms: Configure form fields matching the template structure For webhook: Copy webhook URL and integrate with your website form Required form fields: First Name, Second Name, Email, Contact Number Project Address, Project Type, Spaces Included Budget Range, Completion Date, Style Preferences Involvement Level, Previous Experience, Inspiration Links Step 3: Set Up Claude AI Credentials Obtain API key from https://console.anthropic.com In n8n: Create new credential → Anthropic → Paste API key Apply credential to these nodes: AI Lead Scoring Engine Personalized Client Outreach Email Generator Email Revision Agent Step 4: Configure Telegram Approval Bot Create bot via Telegram's @BotFather Copy bot token Get your Telegram Chat ID (use @userinfobot) In n8n: Create Telegram credential with bot token Configure Human-in-the-Loop Email Approval node: Add your Chat ID Customize approval message format if desired Step 5: Set Up Gmail Sending Enable 2-factor authentication on Gmail account Generate app password: Google Account → Security → App Passwords In n8n: Create Gmail credential using app password Configure Client Email Delivery node with sender details Step 6: Connect Notion Database Create Notion integration at https://www.notion.so/my-integrations Copy integration token Create database with these properties: Client Name (Title), Email (Email), Contact Number (Phone) Project Address (Text), Project Type (Multi-select) Spaces Included (Text), Budget (Select), Timeline (Date) Classification (Select: HOT/WARM/COLD), Confidence (Select) Estimated Value (Number), Status (Select) Share database with your integration In n8n: Add Notion credential → Paste token Configure Notion Lead Database Manager with database ID Step 7: Customize Classification Rules (Optional) Open AI Lead Scoring Engine node Review classification criteria in the prompt: HOT: 500k+ AED, full renovations, 2+ spaces WARM: 100k+ AED, 2+ spaces COLD: <100k AED OR single space Adjust thresholds to match your business requirements Modify currency if not using AED Step 8: Personalize Email Templates Open Personalized Client Outreach Email Generator node Customize: Company name and branding Signature placeholders ([Your Name], [Title], etc.) Tone and style preferences Alternative designer recommendations for COLD leads Step 9: Test the Workflow Activate the workflow Submit a test form with sample data Monitor each node execution in n8n Check Telegram for approval message Verify email delivery and Notion database entry Step 10: Set Up Error Handling (Recommended) Add error workflow trigger Configure notifications for failed executions Set up retry logic for API failures Workflow Node Breakdown 1. Client Intake Form Trigger Captures lead data from website forms or n8n native forms with all project details. 2. AI Lead Scoring Engine Analyzes intake data using structured logic: budget validation, space counting, and multi-factor evaluation. Returns HOT/WARM/COLD classification with confidence scores. 3. Lead Classification Router Routes leads into three priority workflows based on AI classification, optimizing resource allocation. 4. Sales Team Email Notifier Sends instant alerts to sales representatives with complete lead details and AI reasoning for internal tracking. 5. Personalized Client Outreach Email Generator AI-powered composer creating tailored responses demonstrating genuine understanding of client vision, adapted by lead type. 6. Latest Email Version Controller Captures most recent email output ensuring only final approved version proceeds to delivery. 7. Human-in-the-Loop Email Approval Telegram-based review checkpoint sending generated emails to team member for quality control before client delivery. 8. Approval Decision Router Evaluates reviewer's response, routing approved emails to client delivery or rejected emails to revision agent. 9. Email Revision Agent AI-powered editor refining rejected emails based on feedback while maintaining personalization and brand voice. 10. Client Email Delivery Sends final approved personalized emails demonstrating understanding of project vision with clear next steps. 11. Notion Lead Database Manager Records all potential clients with complete intake data, classification results, and tracking information for pipeline management. Customization Tips Adjust Classification Thresholds: Modify budget ranges and space requirements in the AI Lead Scoring Engine prompt to match your market and service level. Multi-Language Support: Update all AI agent prompts with instructions for your target language. Claude supports 100+ languages. Additional Routing: Add branches for special cases like urgent projects, VIP clients, or specific geographic regions. CRM Integration: Replace Notion with HubSpot, Salesforce, or Airtable using respective n8n nodes. SMS Notifications: Add Twilio node for immediate HOT lead alerts to mobile devices. Troubleshooting Issue: Telegram approval not received Verify bot token is correct Confirm chat ID matches your Telegram account Check bot is not blocked Issue: Claude API errors Verify API key validity and credits Check prompt length isn't exceeding token limits Review rate limits on your Anthropic plan Issue: Gmail not sending Confirm app password (not regular password) is used Check "Less secure app access" if using older method Verify daily sending limits not exceeded Issue: Notion database not updating Confirm integration has access to database Verify property names match exactly (case-sensitive) Check property types align with data being sent Template Metrics Execution Time**: ~30-45 seconds per lead (including AI processing) API Calls**: 2-3 Claude requests per lead (classification + email generation, +1 if revision) Cost Estimate**: ~$0.05-0.15 per lead processed (based on Claude API pricing) Support & Community n8n Community Forum**: https://community.n8n.io Template Issues**: Report bugs or suggest improvements via n8n template feedback Claude Documentation**: https://docs.anthropic.com Notion API Docs**: https://developers.notion.com License This template is provided as-is under MIT license. Modify and adapt freely for your business needs. Version: 1.0 Last Updated: October 2025 Compatibility: n8n v1.0+ (Cloud & Self-Hosted), Claude API v2024-10+. An n8n automation workflow template by Jameson Kanakulya.

By Connor Provines

AI-Powered Product-Qualified Lead (PQL) Scoring & Sales Routing One-Line Description Automatically score product usage signals from Amplitude cohorts and route hot leads to sales with enriched context. Detailed Description What it does: This workflow transforms behavioral data into sales-ready leads by instantly detecting when users hit your PQL threshold, enriching their profile with company intelligence, and using AI to score their conversion potential. Hot leads are routed directly to sales with personalized conversation starters, while warm and cold leads enter appropriate nurture sequences. Who it's for: Product-led growth (PLG) teams** bridging the gap between product adoption and sales conversion Sales development teams** needing real-time alerts on high-intent users with actionable context Revenue operations professionals** optimizing lead handoff processes between product and sales Key Features: Real-time PQL detection** - Triggers instantly when users enter Amplitude behavior cohorts, eliminating manual lead review Multi-source enrichment** - Combines product usage data with company intelligence from People Data Labs and AI-powered research AI-driven scoring** - Evaluates usage intensity, ICP fit, intent signals, and timing to produce 0-10 lead scores with breakdown reasoning Smart routing logic** - Automatically categorizes leads as hot (8-10), warm (5-7), or cold (0-4) for appropriate follow-up workflows Sales enablement context** - Provides conversation starters, key insights, red flags, and handoff recommendations tailored to each lead Customizable criteria** - References external Google Doc for PQL rules, allowing non-technical teams to update scoring logic How it works: Trigger: Amplitude fires webhook when user enters predefined PQL cohort based on product usage patterns Enrichment: Pulls company data from People Data Labs and conducts AI research on company stage, tech sophistication, and budget indicators AI Scoring: Agent evaluates combined usage + enrichment data against ICP criteria stored in Google Docs, producing structured scoring output Routing: High-scoring leads (hot) generate formatted Slack alerts for immediate sales outreach; warm/cold leads could trigger email sequences (not shown in this template) Setup Requirements Prerequisites: Amplitude account** with cohort webhook capability (Growth plan or higher) People Data Labs API key** for company/person enrichment (paid credits required) Perplexity API** for AI-powered company research Anthropic Claude API** for PQL scoring logic Google Gemini API** for Slack message formatting Slack workspace** with OAuth app configured for posting messages Google Docs** containing your PQL criteria and ICP definition (publicly readable or authenticated access) Estimated Setup Time: 45-60 minutes including API credential configuration, Amplitude cohort definition, and PQL criteria document creation Installation Notes Amplitude cohort setup**: Define your PQL cohort using behavioral criteria (e.g., "Users who viewed 5+ pages AND invited team members in last 7 days"). Configure webhook to fire on cohort entry. PQL criteria document**: Create a Google Doc outlining your scoring components (usage intensity factors, ICP requirements, intent signals). Update the Google Docs Tool node with your document URL. Free email filtering**: The workflow includes logic to flag free email domains (Gmail, Yahoo, etc.) which you may want to route differently Testing tip**: Use Amplitude's "Test Webhook" feature to send sample payloads before going live Customization Options Replace People Data Labs** with Clearbit, Apollo, or other enrichment providers by swapping the HTTP Request node Add CRM integration** to automatically create opportunities or update lead scores in Salesforce/HubSpot Extend routing paths** by adding branches for warm/cold leads (e.g., trigger email sequences via Customer.io, Braze) Adjust scoring weights** by modifying the AI agent prompt or criteria document without touching workflow logic Multi-channel alerts** by duplicating output nodes to send to email, SMS, or CRM tasks in addition to Slack Category Sales Tags amplitude pql product-qualified-leads sales-automation lead-scoring enrichment people-data-labs slack-notifications ai-scoring revenue-operations Use Case Examples SaaS PLG companies**: Automatically escalate free trial users who hit usage milestones (API calls, integrations connected, team invites sent) to sales for upgrade conversations Developer tools**: Identify enterprise-ready accounts based on team size growth, deployment patterns, and GitHub integration usage, routing to enterprise sales team B2B marketplaces**: Surface buyers showing high-intent behavior (multiple searches, saved items, pricing page views) to account executives with company context for proactive outreach. An n8n automation workflow template by Connor Provines.

By higashiyama

Personalized Learning Content Aggregator with AI Filtering Who’s it for This workflow is for learners, educators, and professionals who want to automatically collect and filter the most relevant educational articles, tutorials, and resources based on specific keywords. How it works Fetches content from RSS feeds and Reddit based on user-defined keywords. AI analyzes and filters the articles to keep only relevant, educational, and non-promotional posts. Saves curated results into a Google Sheet for easy review. How to set up Connect your Google Sheets and AI (OpenAI or LangChain) credentials. Add your RSS feed URLs and keywords to Google Sheets. Adjust schedule timing in the trigger node (default: 8 AM & 6 PM daily). Run the workflow and check the results in your Google Sheet. Requirements Google Sheets account for storage. RSS feed URLs and keyword list. AI node (OpenAI / Gemini / Claude) for filtering logic. How to customize Change or add new content sources (e.g., YouTube, Medium, Dev.to). Adjust AI prompt criteria to match your learning goals. Save results to other platforms (e.g., Notion, Slack, or Airtable). Note: This workflow uses no personal identifiers or API keys directly in nodes. All credentials are safely stored in n8n’s credential manager. An n8n automation workflow template by higashiyama.

By Renan Miller

How it works This workflow automatically extracts specific data from received emails and saves it into a Google Sheets document for easy tracking and analysis. It connects to a Gmail account, searches for emails received within a defined date range from a specific sender, opens links inside those emails, extracts data from the linked pages (such as case ID, patient name, birth date, complaint, and location), processes and cleans the information using custom JavaScript logic, and finally saves the structured results into a Google Sheet. Setup steps Connect Gmail using OAuth2 credentials. Adjust the date filters and sender email in the “Search Emails” node. Customize the CSS selectors in the HTML extraction nodes to match the desired elements from your email or linked page. Open the Code node and modify the logic if you need to calculate or transform additional fields. Link your Google Sheets account and specify the spreadsheet and sheet name where the results will be appended. An n8n automation workflow template by Renan Miller.

By Daniel Nkencho

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators**: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators**: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization**: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming**: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent**: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403)**: Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely**: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters**: Tweak agent prompt to enforce fuller structures like V1V2[C]; verify output length in executions. An n8n automation workflow template by Daniel Nkencho.

By OwenLee

📚In the social and behavioral sciences (e.g., psychology, sociology, economics, management), researchers and students often need to normalize academic paper metadata and extract variables before any literature review or meta-analysis. 🧩This workflow automates the busywork. Using an LLM, it processes CSV/XLSX/XLS files (exported from WoS, Scopus, EndNote, Zotero, or your own spreadsheets) into normalized metadata and extracted variables, and writes a neat table to Google Sheets. 🔗 Example Google Sheet: click me 👥 Who is this for? 🎓 Undergraduate and graduate students or researchers in soft-science fields (psychology, sociology, economics, business) ⏱️ People who don’t have time to read full papers and need quick overviews 📊 Anyone who wants to automate academic paper metadata normalization and variable extraction to speed up a literature review ⚙️ How it works 📤 Upload an academic paper file (CSV/XLSX/XLS) in chat. 📑 The workflow creates a Google Sheets spreadsheet with two tabs: Checkpoint and FinalResult. 🔎 A structured-output LLM normalizes core metadata (title, abstract, authors, publication date, source) from the uploaded file and writes it to Checkpoint; 📧 a Gmail notification is sent when finished. 🧪 A second structured-output LLM uses the metadata above to extract variables (Independent Variable, Dependent Variable) and writes them to FinalResult; 📧 you’ll get a second Gmail notification when done. 🛠️ How to set up 🔑 Credentials Google Sheets OAuth2** (read/write) Gmail OAuth2** (send notifications) Google Gemini (or any LLM you prefer)** 🚀 Quick start Connect Google Sheets, Gmail, and Gemini (or your LLM) credentials. Open File Upload Trigger → upload your CSV/XLSX/XLS file and type a name in chat (used as the Google Sheets spreadsheet title). Watch your inbox for status emails and open the Google Sheets spreadsheet to review Checkpoint and FinalResult. 🎛 Customization 🗂️ Journal lists: Edit the Journal Rank Classifier code node to add/remove titles. The default list is for business/management journals—swap it for a list from your own field. 🔔 Notifications: Replace Gmail with Slack, Teams, or any channel you prefer. 🧠 LLM outputs: Need different metadata or extracted data? Edit the LLM’s system prompt and Structured Output Parser. 📝 Note 📝 Make sure your file includes abstracts. If the academic paper data you upload doesn’t contain an abstract, the extracted results will be far less useful. 🧩 CSV yields no items? Encoding mismatches can break the workflow. If this happens, convert the CSV to .xls or .xlsx and try again. 📩 Help Contact: owenlzyxg@gmail.com. An n8n automation workflow template by OwenLee.

By Fahmi Fahreza

Quick overview This workflow automatically fetches balances from multiple financial institutions (RBC, Amex, Wise, PayPal) using Plaid, maps them to QuickBooks account names, and loads structured records into Google BigQuery for analytics. How it works The Schedule Trigger runs weekly. Four Plaid API calls fetch balances from RBC, Amex, Wise, and PayPal. Each response splits out individual accounts and maps them to QuickBooks names. All accounts are merged into one dataset. The workflow structures the account data, generates UUIDs, and formats SQL inserts. BigQuery node uploads the finalized records. Setup Add your Plaid and Google BigQuery credentials in the n8n Credential Manager before making any changes to the workflow. Open the configuration node and replace all hardcoded client IDs and secrets with the corresponding credential variables you just created. Test each credential connection individually to confirm Plaid and BigQuery are both authenticating and responding correctly. Open the Schedule Trigger node and set the frequency to match your preferred reporting cadence before activating the workflow. Additional info Published by Fahmi Fahreza, Indonesia’s first official n8n Brand Ambassador and founder of WithMi Automation, built from real client implementations, not tutorials. → Let us build it for you: withmiautomation.com → Learn to build it yourself: academy.withmiautomation.com → Bring Fahmi to your team (training, workshop, talkshow): fahmiiireza.com. An n8n automation workflow template by Fahmi Fahreza.

By Abdul Matheen

AI Doctor’s Appointment Scheduler – Process Flow User Interaction via Telegram: The user sends a text or voice message through Telegram requesting a doctor’s appointment. Input Processing: The AI agent receives and interprets the user’s message to identify the doctor’s name, preferred date, and time. Doctor Information Retrieval: The agent accesses the doctor’s details stored in Google Sheets (or an Excel file). Schedule Verification: It checks the doctor’s availability for the requested date and time using the doctor’s schedule ledger or database. Availability Response: If the doctor is already booked, the agent informs the user and suggests alternative available slots. If the doctor is available, the agent proceeds to confirm the appointment details with the user. Appointment Confirmation & Booking: Once the user confirms, the agent records the appointment details in the Excel sheet (or Google Sheet). Confirmation Notification: The agent sends a confirmation message to the user through Telegram, summarizing the appointment details (doctor name, date, and time). An n8n automation workflow template by Abdul Matheen.

By Zain Khan

AI-Powered Customer Feedback: Triage and Insight-Driven Chat This n8n workflow creates a two-phase system for handling customer feedback received via a Jotform submission. The first agent quickly triages the issue, and the second agent engages in a persistent, conversational exchange over email to collect the information necessary for a resolution. Phase 1: Triage and Initial Action (AI Agent) This phase is triggered by a new submission on the Jotform. The goal is to immediately categorize the feedback and take the appropriate initial action. Jotform Trigger: The workflow starts instantly when a user submits your designated feedback form. AI Agent (Triage): This agent (powered by Google Gemini) is tasked with two primary jobs: Sentiment Analysis and Response Drafting: It reads the feedback (q6_typeA6) and the user's name (q3_name.first). If Positive: It uses the Send a message in Gmail tool to send a concise, appreciative thank you note. If Negative: It uses the Send a message in Gmail tool to send an initial, empathetic response acknowledging the issue and stating that a team member will follow up with questions. It also uses the Create an issue in Jira Software tool to log the bug or issue immediately. Data Structuring: It uses the Structured Output Parser to extract key data points, most importantly the threadId of the initial email, which is crucial for the follow-up conversation agent. Phase 2: Conversational Insight Gathering (AI Agent (Chat)) This phase takes over for all negative feedback, engaging the customer in a back-and-forth exchange to collect essential details required for the development or support team. Gmail Trigger: This node is set to poll for new, unread emails (which are expected to be replies from the customer). Simple Memory: This node is vital for the conversational aspect. It is configured to use the unique email threadId as its session key, allowing the AI Agent to remember the entire history of the conversation (previous questions asked and details provided) across multiple emails. AI Agent (Chat): This is the 2nd agent and the core of the conversational process. Role: It acts as a dedicated feedback assistant. Goal: Its instruction is to reply and ask for specific, missing information needed for the ticket, such as: what device they were using, if they know the steps to reproduce the issue, and to confirm that the team will send a free coupon for credits as a thank you for their help. Tool: It uses the Reply to a message in Gmail tool to continue the conversation directly within the original email thread. Resolution: The agent is trained to look for confirmation that all necessary information has been provided. Once it determines the issue details are complete, it will send a final thank you email and automatically use the Jira tool to summarize and update the existing Jira issue with the new insights, closing the loop on the data collection process. Requirements To implement and run this automated customer feedback workflow, the following accounts and credentials are required: 1. Automation Platform n8n Instance:** A running instance of n8n (Cloud or self-hosted) to host and execute the workflow. Sign up for n8n using: https://n8n.partnerlinks.io/pe6gzwqi3rqw 2. Service Credentials You must set up and connect the following credentials within your n8n instance: Google Gemini API Key:* Required to power both *AI Agent** nodes for sentiment analysis and conversational follow-up. Gmail OAuth2/API Key:** Required for: The Send a message in Gmail tool (for initial replies). The Gmail Trigger (to detect new replies). The Reply to a message in Gmail tool (for the ongoing conversation). Jotform API Key:* Required for the *Jotform Trigger** node to instantly receive and process new form submissions. Sign up for Jotform using: https://www.jotform.com/?partner=zainurrehman Jira Software Credentials:* Required for the *Create an issue in Jira Software* tool (for the first agent) and the *Jira Tool** (for the second agent to update the ticket). 3. External Configurations Jotform Setup:** A live Jotform must be configured with specific fields to capture the user's name, email, and the feedback text. Jira Setup:* You need a designated *Jira Project* and a defined *Issue Type** for the workflow to create and update tickets. An n8n automation workflow template by Zain Khan.

By Bhuvanesh R

Instant, automated scheduling. This AI Scheduling Agent manages real-time appointments, availability checks, and rescheduling across Google Calendar and Sheets, eliminating human hold times. 🎯 Problem Statement Traditional call center or online booking systems often lack the flexibility to handle complex, multi-step customer requests like rescheduling, checking dynamic availability across multiple time slots, or handling context-aware conversational booking. This leads to friction, missed bookings, and high administrative overhead for service companies like HVAC providers. ✨ Solution This workflow deploys a sophisticated AI Scheduling Agent that acts as a virtual receptionist. It uses the Language Model's (LLM) "tool-use" capability to intelligently execute complex, sequential business logic (e.g., check availability before booking, find existing events before rescheduling) and manages the entire lifecycle of a service appointment, from initial inquiry to final confirmation. ⚙️ How It Works (Multi-Step Execution) Trigger: A customer request (e.g., from an external voice or text platform) hits the Webhook Trigger with intent details (e.g., tool\_request: 'reschedule\_appointment'). Agent Logic: The Receptionist Agent uses a strict system prompt and its internal tools to formulate an execution plan. It maintains conversational state via the simple-memory node. Tool Execution (Example: Reschedule): The Agent executes a predefined sequence of private tools: find\_old\_event: Locates the existing booking ID using the customer's email. check\_calendar: Verifies the proposed new time is available (2-hour window). reschedule\_appointment: Updates the calendar event. log\_lead: Updates the central Google Sheet. Synchronous Response: The Agent sends a confirmation or follow-up question via the respond\_to\_webhook node. Asynchronous Confirmation: The log\_lead action triggers a secondary workflow that composes a professional email via a second LLM (Anthropic) and sends it to the customer via Gmail, followed by an internal alert via Google Chat. 🛠️ Setup Steps Credentials: AI/LLM: Configure credentials for the Language Model used (OpenAI or Gemini) for the core Agent. Google Services: Set up OAuth2 credentials for Google Calendar (for booking/checking), Google Sheets (for logging), and Gmail (for customer confirmation). Google Calendar: Specify the technician's calendar ID (bhuvaneshx13@gmail.com in the template) in all Calendar nodes. Google Sheets: Create a new Google Sheet to serve as the Lead Log and update the Document ID and Sheet Name in the log\_lead and log\_lead\_trigger nodes. Tool Configuration: Review and customize the Agent's system prompt in the Receptionist node to align time zone rules (currently Asia/Kolkata - IST) and business hours (9:00 AM to 6:00 PM) with your operations. ✅ Benefits Increased Efficiency: Fully automates complex scheduling and rescheduling, freeing up human staff. Contextual Service: AI handles multi-turn conversations and adheres to strict business rules (e.g., 2-hour slots, maximum tool usage). Data Integrity: Ensures all bookings are immediately logged to Google Sheets, maintaining a centralized record (CRM). Professional Flow: Provides immediate confirmation to the customer via email and instant notification to the internal team via chat. 🚀 Other Use Cases The underlying multi-step, tool-execution pattern is highly versatile and can be adapted for any service industry requiring complex, rules-based scheduling: Real Estate:** Scheduling property viewings (Check agent availability → Book viewing → Send directions). HVAC Services:** Managing maintenance and repair visits (Diagnose issue type → Match with qualified technician → Check part availability → Schedule visit → Send service confirmation). Medical/Dental:** Booking patient appointments (Check insurance eligibility → Check doctor availability → Book → Send pre-visit forms). Legal Services:** Intake for consultations (Collect client issue → Check specialist availability → Book → Send retainer agreement). Automotive Repair:** Scheduling service bays (Check bay and mechanic availability → Book → Update internal service board). An n8n automation workflow template by Bhuvanesh R.

By Christian Lutz

How it works This workflow automates the delivery of personalized, AI-generated reports or roadmaps for new leads. When someone submits their information through a form, the workflow: Captures and stores the lead data. Uses an AI model to generate a customized report or roadmap. Formats the output into a professional, email-ready HTML document. Sends the report automatically to the lead via email. Optionally sends internal notifications (e.g., via chat or email) for tracking and follow-up. The process eliminates manual work and ensures every lead receives instant, high-quality output tailored to their input. Setup steps Webhook – Connect your form or website to the webhook endpoint to receive lead data. Data Table – Create or link a table to store incoming leads and track delivery status. AI Configuration – Add your OpenAI (or compatible) API credentials and customize prompts for your desired output. Email Setup – Configure SMTP credentials and define sender/recipient addresses for report delivery. Notifications – Optionally connect a chat or messaging service (e.g., Telegram) for internal alerts. Activation – Test the workflow, confirm the data flow and email delivery, then activate it for live use. This workflow transforms manual lead engagement into a fully automated, AI-driven experience that delivers instant, personalized value to every new contact. An n8n automation workflow template by Christian Lutz.

By Artem Makarov

About this template This template is to demonstrate how to trace the observations per execution ID in Langfuse via ingestion API. Good to know Endpoint: https://cloud.langfuse.com/api/public/ingestion Auth is a Generic Credential Type with a Basic Auth: username = you_public_key, password = your_secret_key. How it works Trigger**: the workflow is executed by another workflow after an AI run finishes (input parameter execution_id). Remove duplicates** Ensures we only process each execution_id once (optional but recommended). Wait to get execution data** Delay (60-80 secs) so totals and per-step metrics are available. Get execution** Fetches workflow metadata and token totals. Code: structure execution data** Normalizes your run into an array of perModelRuns with model, tokens, latency, and text previews. Split Out* → *Loop Over Items** Iterates each run step. Code: prepare JSON for Langfuse** Builds a batch with: trace-create (stable id trace-<executionId>, grouped into session-<workflowId>) generation-create (model, input/output, usage, timings from latency) HTTP Request to Langfuse** Posts the batch. Optional short Wait between sends. Requirements Langfuse Cloud project and API keys n8n instance with the HTTP node Customizing Add span-create and set parentObservationId on the generation to nest under spans. Add scores or feedback later via score-create. Replace sessionId strategy (per workflow, per user, etc.). If some steps don’t produce tokens, compute and set usage yourself before sending. An n8n automation workflow template by Artem Makarov.

By Lukman

This n8n workflow lets you delegate inbox management to an AI agent. It automatically replies to emails when a suitable response is found in your knowledge base. If no match is found, the message is forwarded to a human for review. This ensures all replies follow company guidelines and prevent misinformation or misrepresentation. Use Case Ideal for businesses that receive frequent inquiries about products or services and want to automate responses, freeing up time to focus on core operations. How It Works Polls your inbox for new incoming emails Cleans HTML to reduce token usage and filters spam Categorizes emails for better organization Retrieves conversation history from Supabase (if available) to give the AI proper context Uses the AI agent to query your FAQ database for relevant answers Replies automatically if a suitable answer is found Sends a placeholder email and forwards to a human if no accurate answer exists Ingests all processed emails into Supabase to retain conversation history and improve future AI accuracy Customization You can connect any email provider or LLM model. The workflow can also be expanded to let the AI schedule meetings, answer availability questions, or handle other inbox tasks. If you'd like help tailoring this workflow to your business, feel free to reach out: Upwork Profile. An n8n automation workflow template by Lukman.

By Drew Fabrikant

🎥 AI-Powered Inbound Video Agent: Auto-Respond to Leads with Personalized Videos Description: This workflow automates the first-touch response for inbound leads by creating and delivering a hyper-personalized video and follow-up email, all in seconds, using a powerful stack: n8n, Scout, HeyGen API, and OpenAI. How It Works (The Lead Journey): 📥 Form Trigger: Captures initial user inputs (name, email, address). 🔎 Data Enrichment (Scout): Instantly looks up lead details like property type, homeownership status, and household income. ✍️ Script Agent (GPT-5/LangChain): An AI agent writes a professional, 15-second outreach script, tailoring the message with three discussion paths based on the enriched Scout data. 🎬 Video Generation (HeyGen): Triggers an avatar video using the custom script. 📧 Delivery Logic: Waits for the video to complete, retrieves the final URL/thumbnail, and passes it to the next step. 🔗 Email Writer (GPT-4): Generates an HTML outreach email, embedding the video thumbnail and including a direct booking link (Calendly). 🚀 Send Email (Gmail Node): Sends the complete, personalized message to the inbound lead automatically. Key Integrations: Scout: Lead Data Enrichment HeyGen: AI Avatar Video Generation OpenAI (GPT-4/LangChain): Scriptwriting and Email Copy Gmail: Automated Email Delivery Setup Note: Ensure you have configured n8n credentials for HeyGen (httpHeaderAuth), Scout (HTTP Request header), OpenAI, and Gmail (OAuth2). An n8n automation workflow template by Drew Fabrikant.

By Connor Provines

One-Line Description Automatically detects missed Zoom demos booked via Calendly and triggers AI-powered follow-up sequences. Detailed Description What it does: When a prospect books a demo through Calendly but fails to join the Zoom meeting, this workflow automatically detects the no-show, generates personalized recovery messages using AI, updates your database, and notifies your sales team—all within minutes of the meeting ending. It bridges Calendly, Zoom, and your follow-up channels to ensure no lead falls through the cracks. Who it's for: Sales teams** running high-volume demo calendars who lose 20-40% of booked meetings to no-shows Customer success managers** conducting onboarding calls where attendance tracking matters SDRs and BDRs** who need immediate alerts when prospects miss scheduled meetings Revenue operations teams** seeking to improve demo-to-opportunity conversion rates through faster follow-up Key Features: Real-time no-show detection** - Automatically checks Zoom participant lists against expected attendees within seconds of meeting end AI-generated recovery messaging** - Creates contextual, empathetic follow-up emails and LinkedIn messages tailored to each no-show scenario Instant team notifications** - Sends formatted Slack alerts with attendee details and suggested next actions so reps can manually follow up if needed Attendance tracking database** - Maintains a searchable record of all bookings and attendance status for reporting and analysis Multi-channel follow-up orchestration** - Coordinates email, Slack notifications, and optional CRM updates from a single automation Selective event filtering** - Processes only specific Calendly event types so you control which meetings trigger the workflow How it works: Booking capture: Calendly webhook fires when a demo is scheduled, extracting Zoom meeting details and attendee information Meeting monitoring: When the Zoom meeting ends, a second webhook triggers attendance verification by pulling the participant list from Zoom's API No-show identification: Workflow cross-references the expected attendee email with actual Zoom participants to confirm whether they attended Automated response: For confirmed no-shows, AI generates personalized recovery messages while the system updates your database and notifies your team via Slack Optional integrations: Simultaneously updates CRM deal stages or triggers additional follow-up sequences based on your configuration Setup Requirements Prerequisites: Calendly account** (any paid plan) with webhook access and Personal Access Token Zoom account** (Pro or higher) with Server-to-Server OAuth app credentials for API access OpenAI API key** for AI-generated follow-up message creation Slack workspace** with OAuth permissions to post messages (optional but recommended) n8n Data Table** created with columns: meeting_id, email, status (built-in n8n feature, no external database needed) Email sending service** configured in n8n (SMTP, Gmail, SendGrid, etc.) if enabling automated email sending CRM API access** (HubSpot, Salesforce, Pipedrive, etc.) if enabling deal updates (optional) Note: Zoom API has rate limits (varies by plan); this workflow makes 1-2 API calls per meeting end event. Estimated Setup Time: 45-60 minutes including Zoom app creation, Calendly webhook configuration, and Data Table setup Installation Notes Critical setup steps: Zoom webhook validation**: You must complete Zoom's webhook endpoint validation process before receiving real events. The workflow includes a dedicated validation path—run it once after creating your Zoom app. Calendly webhook creation**: Use the "Manual Setup Trigger" path in the workflow to programmatically create your Calendly webhook subscription. This only needs to run once. Event type filtering**: Replace the placeholder YOUR_CALENDLY_EVENT_TYPE_URI with your specific demo event type URI from Calendly to avoid processing all meeting types. Test with a real meeting**: Book a test demo, join briefly with a different email than the booking email, then leave. The workflow should detect the "no-show" for the booking email. Common pitfalls to avoid: Forgetting to enable the disabled "Send Recovery Email" node after testing (it's disabled by default to prevent accidental sends during setup) Not configuring Zoom Server-to-Server OAuth correctly (requires Account ID, Client ID, and Client Secret—not JWT credentials) Using a personal Calendly account instead of an organization account (webhooks require organization-level access) Overlooking the Data Table creation step—the workflow will fail without this internal database Testing recommendations: Start with Slack notifications only (leave email sending disabled) to verify the workflow logic Use your own email as a test booking to safely generate AI messages without sending to real prospects Check the Data Table after each test to confirm booking records are being created and updated correctly Customization Options Easy modifications: Swap email for SMS**: Replace the email node with Twilio SMS to send text message follow-ups instead Add delays**: Insert "Wait" nodes to schedule follow-ups hours or days later rather than immediately Change AI tone**: Modify the OpenAI prompt to match your brand voice (casual, formal, humorous, etc.) Multi-step sequences**: Duplicate the AI and email nodes to create a 3-touch follow-up cadence over several days Different CRM platforms**: The HubSpot node can be swapped for Salesforce, Pipedrive, or any CRM n8n supports Extension possibilities: Add Google Sheets logging for executive dashboard reporting on no-show rates Integrate with Calendly's rescheduling API to automatically send rebooking links Connect to Loom or Vidyard APIs to attach pre-recorded demo videos in follow-up emails Create a "second chance" discount workflow that offers incentives for rescheduling Build a predictive model by exporting no-show data to analyze patterns (time of day, lead source, etc.) Category Sales Tags calendly zoom no-show-recovery demo-automation lead-follow-up sales-automation meeting-tracking ai-messaging slack-notification openai Use Case Examples SaaS sales team**: A B2B software company runs 40+ demos per week. When prospects no-show, this workflow immediately notifies the assigned rep in Slack with a pre-written LinkedIn message, sends an empathetic recovery email offering a Loom recording alternative, and flags the deal in HubSpot for manual outreach within 2 hours. Agency onboarding**: A marketing agency conducts discovery calls with new clients. If a client misses their scheduled kickoff meeting, the workflow logs the no-show, updates the client status in their CRM, and sends a friendly rescheduling email with three alternative time slots—all before the account manager even notices. Customer success**: A customer onboarding team tracks training session attendance. When users don't join their scheduled implementation calls, the workflow automatically sends a resource-rich email with documentation links, notifies the CSM team channel, and schedules a follow-up task in their project management tool. An n8n automation workflow template by Connor Provines.

By Atta

Stop drowning in job applications. This workflow transforms your hiring process from a manual, time-consuming data-entry task into an automated, intelligent screening system. When a candidate applies via your Jotform, this workflow automatically: Downloads their PDF resume (even from private links). Extracts the text from the resume and reads their cover letter. Compares the application to the Notion job description using Gemini AI. Generates an "AI Fit Score" (0-100) and a concise summary. Filters out low-scoring applicants. Creates a new, fully detailed candidate page in your Notion database, linked to the correct job. Instantly alerts your hiring team on Slack with the candidate's score and summary. Sends an automated confirmation email to the candidate. Features Triggers on New Jotform Submissions: Kicks off the moment a candidate clicks "Apply Now." Handles Private Files: Securely downloads private resume files from Jotform using your API key. PDF Text Extraction: Automatically reads the text from any uploaded PDF resume. Deep AI Analysis: Uses Gemini AI to compare the candidate's resume and cover letter against the specific job description from Notion. Relational Database Linking: Automatically links the new candidate to the correct "Open Position" page in Notion. Automated Quality Filtering: An IF node stops low-scoring candidates from cluttering your database. Multi-Channel Communication: Provides instant feedback to your team (Slack) and the candidate (Email). Nodes Used 🟣 Jotform Trigger (Jotform Trigger) ✉️ Gmail (Send Confirmation Email) ⬇️ HTTP Request (Download Resume PDF) 📄 Extract From File (Read Resume Text) 🔍 Notion (Find Job in Notion) 🖇️ Merge (Combine Data) 🧠 AI Agent (AI Candidate Analysis) ❓ IF (Score > 40?) ➕ Notion (Create Candidate in Notion) 📣 Slack (Alert Hiring Team) 🚫 No Operation, do nothing (Ignore (Score < 40)) How to use this template This template requires manual setup due to Jotform's unique Question IDs (QIDs). Please follow these steps carefully. ⚠️ CRITICAL WARNING ON JOTFORM QIDs To get the file URL, this template requires you to turn "Resolve Data" OFF in the Jotform Trigger. This means the workflow uses Question IDs (e.g., q7_positionApplying, q8_typeA8) instead of human-readable labels. Your QIDs will be different from the ones in this template. You must run the trigger once, find your QIDs, and replace them in the downstream nodes. 1. Set up Jotform and Notion (See "More Information" section below) Before you start, create your Jotform form and your two Notion databases ("Open Positions" and "Candidates") as described at the end of this document. 2. Configure the Jotform Trigger Node Credentials: Connect your Jotform account. Form: Select your "Job Application" form. IMPORTANT: In the node Parameters, find the "Resolve Data" option and turn it OFF. Test: Run a test by submitting your form. Look at the output and write down your unique QIDs for each field (e.g., q3_fullName, q7_positionApplying, q8_typeA8, uploadYour). 3. Configure the Download Resume PDF (HTTP Request) Node Credentials: This node needs your Jotform API Key. Authentication: Query Auth Credential: Create new Header Auth credentials. Name: Jotform API Key (Query) Parameter Name: apiKey Parameter Value: [Paste your Jotform API Key here] URL: Replace uploadYour in the expression {{ $('Jotform Trigger').item.json.uploadYour[0] }} with the QID for your file upload field. 4. Configure the Find Job in Notion Node (See the "Required Notion Setup" section at the end of this document for detailed instructions on how to build this database) Credentials: Connect your Notion credentials. Database ID: Select your "Open Positions" database. Filter Value: Replace q7_positionApplying in the expression {{ $('Jotform Trigger').item.json.q7_positionApplying }} with the QID for your "Position" dropdown. 5. Configure the AI Candidate Analysis Node Credentials: Connect your Google AI (Gemini) credentials. Prompt: In the prompt, find the line for "Candidate's Cover Letter". Replace q8_typeA8 in the expression {{ $('Jotform Trigger').item.json.q8_typeA8 }} with the QID for your cover letter field. 6. Configure the IF (Score > 40?) Node No credentials needed. You can change the "Value 2" from 40 to any score you want to use as your quality filter. 7. Configure the Create Candidate in Notion Node (See the "Required Notion Setup" section at the end of this document for detailed instructions on how to build this database) This is the most important step. Connect your Notion credentials and select your "Candidates" database. You must go through every single property and replace my QIDs with your QIDs from the Jotform trigger. Candidate Name: {{ $('Jotform Trigger').item.json.q3_fullName.first }} ... (Replace q3_fullName) Email: {{ $('Jotform Trigger').item.json.q4_email }} (Replace q4_email) Phone: {{ $('Jotform Trigger').item.json.q5_phoneNumber?.full ? ... (Replace q5_phoneNumber) Position (Relation): This expression, {{ $('Find Job in Notion').item.json.id }}, is correct. AI Summary, Score, Skills: These expressions are also correct. Resume (File): In the URL field, replace uploadYour with your file QID. 8. Configure Communication Nodes Send Confirmation Email (Gmail): Connect your email credentials and customize the email body. Alert Hiring Team (Slack): Connect your Slack credentials and select your desired channel (e.g., #hiring). 9. Activate your Workflow\! Once all steps are configured and QIDs are replaced, save and activate your workflow. How to Adapt the Template Log Rejected Candidates: Connect the false (No) output of the IF (Score > 40?) node to a Google Sheets node to keep a log of all candidates who didn't meet the score threshold. Change the AI Prompt: Edit the prompt in the AI Candidate Analysis node to ask for different insights, such as "List 3 potential red flags" or "Estimate years of experience." Use a Different AI: Replace the Google AI node with an OpenAI or Claude node. Change Notifications: Swap the Slack node for Discord, Microsoft Teams, or a simple email notification. More Information About Jotform Jotform is a powerful and easy-to-use online form builder perfect for creating professional job application forms. Its flexibility with file uploads and webhooks makes it an ideal trigger for this n8n automation. If you don't have an account, you can get started using the link above. Required Jotform Fields Your Jotform must have these fields for the template to work: Full Name Email Phone Number (Can be optional) File Upload (Label: Upload Your Resume) Crucial: Set the file type option to pdf only. Dropdown (Label: Position Applying For) Crucial: The options (e.g., "Marketing Manager") must exactly match the page titles in your "Open Positions" Notion database. Long Text (Label: Summary / Cover Letter) Required Notion Setup This workflow requires two separate databases in Notion that are linked together. Both databases must be shared with your n8n integration. Database 1: "Open Positions" This database holds your job descriptions. The AI reads from this database to understand the job requirements. Create a new Table database in Notion named Open Positions. Create the following properties: Name (Title): This is the job title. It must exactly match the options in your Jotform dropdown (e.g., "Marketing Manager"). Job Description (Text): A text field where you will paste the full job description for the role. Database 2: "Candidates" This database will store every new applicant and their AI-generated score. Create a new Table database in Notion named Candidates. Create the following properties to store the data: Candidate Name (Title): This will be filled with the applicant's name from the form. Email (Email): Stores the candidate's email. Phone (Phone): Stores the candidate's phone number. Resume (File): Stores the link to the resume PDF. AI Summary (Text): Stores the 2-sentence summary from the AI. AI Fit Score (Number): Stores the 0-1S00 score from the AI. Key Skills (Multi-select): Stores the skills array generated by the AI. Position (Relation): This is the final, crucial property. Type: Select Relation. Database: In the menu, search for and select your "Open Positions" database. IMPORTANT: A toggle labeled "Show on 'Open Positions'" will appear. You must turn this toggle ON. This creates a two-way relation, which is required for n8n to see and use this property. An n8n automation workflow template by Atta.

By KlickTipp

Community Node Disclaimer This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only. Who’s it for Marketing teams, agencies, and content creators who want to turn Instagram post comments into automated conversations — capturing leads, sending personalized DMs, and enriching contacts in KlickTipp without manual work. How it works This workflow automates engagement between Instagram users and your marketing funnel. It listens for new Instagram comments, validates the Meta webhook, and sends personalized DMs with form links. The workflow then stores and syncs user data for tagging and enrichment in KlickTipp. When a new comment appears, it: Validates the webhook setup via the Meta hub.challenge Captures the commenter’s username and ID Sends a personalized DM with a form link for lead capture Stores the data in Google Sheets for tracking Updates or tags the contact in KlickTipp The result: every Instagram comment turns into a structured, tagged lead for your marketing automation. How to set up Connect accounts for Meta (Instagram), Google Sheets, and KlickTipp. Set up your Meta App webhook for Instagram comments, using your workflow’s webhook URL and verify token (e.g., KlickTipp). Create a Google Sheet as a matching table with the columns: Instagram username Instagram ID Authenticate KlickTipp with API credentials and ensure your subscriber fields are configured. Test by commenting on a connected Instagram post to trigger the workflow. 💡 Pro Tip: Customize the DM to include your brand’s tone and lead form link for higher engagement. Requirements Meta (Instagram) Business Account Facebook Graph API with pages_messaging permission Google Sheets OAuth connection KlickTipp account with API access How to customize Replace the default form link with your own JotForm or landing page URL. Adjust DM content to fit your tone and campaign messaging. Add logic to send different DMs based on comment keywords. Integrate with KlickTipp tags for automatic segmentation. Expand the workflow to handle repeat commenters or trigger follow-ups. An n8n automation workflow template by KlickTipp.

By Jay Emp0

Ebook to Audiobook Converter ▶️ Watch Full Demo Video What It Does Turn any PDF ebook into a professional audiobook automatically. Upload a PDF, get an MP3 audiobook in your Google Drive. Perfect for listening to books, research papers, or documents on the go. Example: Input PDF → Output Audiobook Key Features Upload PDF via web form → Get MP3 audiobook in Google Drive Natural-sounding AI voices (MiniMax Speech-02-HD) Automatic text extraction, chunking, and audio merging Customizable voice, speed, and emotion settings Processes long books in batches with smart rate limiting Perfect For Students**: Turn textbooks into study audiobooks Professionals**: Listen to reports and documents while commuting Content Creators**: Repurpose written content as audio Accessibility**: Make content accessible to visually impaired users Requirements | Component | Details | |-----------|---------| | n8n | Self-hosted ONLY (cannot run on n8n Cloud) | | FFmpeg | Must be installed in your n8n environment | | Replicate API | For MiniMax TTS (Sign up here) | | Google Drive | OAuth2 credentials + "Audiobook" folder | ⚠️ Important: This workflow does NOT work on n8n Cloud because FFmpeg installation is required. Quick Setup 1. Install FFmpeg Docker users: docker exec -it <n8n-container-name> /bin/bash apt-get update && apt-get install -y ffmpeg Native installation: sudo apt-get install ffmpeg # Linux brew install ffmpeg # macOS 2. Get API Keys Replicate**: Sign up at replicate.com and copy your API token Google Drive**: Set up OAuth2 in n8n and create an "Audiobook" folder in Drive 3. Import & Configure Import n8n.json into your n8n instance Replace the Replicate API token in the "MINIMAX TTS" node Configure Google Drive credentials and select your "Audiobook" folder Activate the workflow Cost Estimate | Component | Cost | |-----------|------| | MiniMax TTS API | $0.15 per 1000 characters ($3-5 for average book) | | Google Drive Storage | Free (up to 15GB) | | Processing Time | ~1-2 minutes per 10 pages | How It Works PDF Upload → Extract Text → Split into Chunks → Convert to Speech (batches of 5) → Merge Audio Files (FFmpeg) → Upload to Google Drive The workflow uses four main modules: Extraction: PDF text extraction and intelligent chunking Conversion: MiniMax TTS processes text in batches Merging: FFmpeg combines all audio files seamlessly Upload: Final audiobook saved to Google Drive Voice Settings (Customizable) { "voice_id": "Friendly_Person", "emotion": "happy", "speed": 1, "pitch": 0 } Available emotions: happy, neutral, sad, angry, excited Limitations ⚠️ Self-hosted n8n ONLY (not compatible with n8n Cloud) PDF files only (not EPUB, MOBI, or scanned images) Large books (500+ pages) take longer to process Requires FFmpeg installation (see setup above) Troubleshooting FFmpeg not found? Docker: Run docker exec -it <container> /bin/bash then apt-get install ffmpeg Native: Run sudo apt-get install ffmpeg (Linux) or brew install ffmpeg (macOS) Rate limit errors? Increase wait time in the "WAITS FOR 5 SECONDS" node to 10-15 seconds Google Drive upload fails? Make sure you created the "Audiobook" folder in your Google Drive Reconfigure OAuth2 credentials in n8n Created by emp0 | More workflows: n8n Gallery. An n8n automation workflow template by Jay Emp0.

By LeeWei

Overview of the n8n Workflow This n8n workflow automates the daily monitoring of trends across X (Twitter), newsletters, and websites. It runs on a schedule, fetches data from configured sources in Google Sheets, processes it using AI agents for extraction and analysis (including browser automation and web search), and appends relevant updates to a Google Sheets database. The workflow handles data aggregation, filtering for recency, and deduplication, ensuring users receive concise, actionable insights on topics like AI news or market opportunities. How it Works • The workflow triggers daily, pulling configuration from Google Sheets (e.g., X accounts, newsletters, websites). • It scrapes recent X posts, fetches newsletter emails via Gmail, and browses websites using an AI agent to extract updates. • All data is aggregated, analyzed by an AI agent (with optional web research for context), and filtered for relevance. • Extracted data points (name, description, source, date) are saved to Google Sheets for easy review. Set Up Steps Setup takes about 15-30 minutes, focused on credentials and API keys. Detailed node guidance is in the workflow's sticky notes—clone it, add credentials, and test. The workflow is plug-and-play once imported; only edit prompts or sources as needed. ⚙️ AI Trend Listener: Monitor Updates 24/7 Automate daily scanning of X (Twitter), newsletters, and websites for trends, saving key updates to Google Sheets. 🧑‍💻 Author: LeeWei 🚀 Steps to Connect: Google Sheets Setup Duplicate the template sheet. Add OAuth2 credentials in n8n for read/write access to the sheet. Populate the X, Newsletters, and Websites tabs with your sources (e.g., usernames, email filters, URLs). Apify Integration (for X Scraping) Sign up at apify.com and generate an API token. Paste the token into the HTTP Request node's credentials (header auth: Authorization Bearer). Test with a sample X account to fetch recent posts. Gmail Setup (for Newsletters) Create OAuth2 credentials in n8n with scopes for reading emails (gmail.readonly). Connect to the Gmail nodes; ensure your newsletters are in the inbox. 💡 Filter for specific senders in the Newsletters sheet tab. Airtop Browser Automation Register at airtop.ai, generate an API key, and create a profile. Paste the key into the Airtop nodes' credentials. The browser agent handles website navigation—test with a sample URL. OpenAI API Key Generate a key at platform.openai.com. Paste it into the OpenAI (or equivalent chat model) nodes. Use for AI agents analyzing data; select a model like GPT-4 for best results. Perplexity AI (for Web Research) Sign up at perplexity.ai/api and get an API key. Paste it into the Perplexity AI tool node. Enables context gathering during analysis—use sparingly for cost. Plug and Play Instructions Clone the workflow JSON directly into n8n—all nodes (schedules, agents, aggregators, HTTP requests) are pre-wired and ready. No re-setup needed beyond the steps above. Key editable fields (found in sticky notes): Your Instructions Node: Browser Prompt** Customize the website extraction (default: "Search all the latest AI news from this page and its child pages"). Example: Change to "Find new real estate listings" for market-specific monitoring. Your Instructions Node: Analysis Prompt** Adjust the AI filtering criteria (default: Focuses on AI developments). Example: Add rules for crypto signals or finance news exclusion/inclusion. Google Sheets Nodes (Get X Accounts, Get Newsletters, Get Websites)** Update the sheet IDs or tabs if using a custom duplicate; add more sources directly in the sheet. Schedule Trigger Node** Change the daily time (default: 6 AM) or frequency for more frequent runs. Filter Node (for Tweets)** Tweak the 24-hour recency check if monitoring longer periods. Test with the default AI focus: Run manually and check the Data Points sheet for updates. Potential Customizations Add More Sources**: Expand Google Sheets tabs for new categories (e.g., Reddit via HTTP) and add aggregation branches. Switch AI Models**: Replace OpenAI with another provider in the chat model nodes. Enhance Output**: Add notifications (e.g., Slack node) after saving to Sheets. Scale Monitoring**: Increase Apify maxItems or add loops for larger datasets. Considerations and Improvements Rate Limits**: Apify and Perplexity have usage caps; monitor for heavy queries. Airtop starts with free credits (10,000). Data Volume**: Handles moderate sources; for high-volume, batch process or filter stricter. Privacy**: Data passes through third-party APIs—avoid sensitive topics. Enhancements**: Integrate email notifications for urgent trends or add deduplication logic for cross-source overlaps. This workflow keeps you ahead in fast-moving fields like AI or markets, delivering daily insights without manual checking. Questions? Test it in n8n!. An n8n automation workflow template by LeeWei.

By explorium

Explorium Agent for Slack AI-powered Slack bot for business intelligence queries using Explorium API through MCP. Prerequisites Slack workspace with admin access Anthropic API key (You can replace with other LLM Chat) Explorium API Key 1. Create Slack App Create App Go to api.slack.com/apps Click Create New App → From scratch Give it name (e.g., "Explorium Agent") and select workspace Bot Permissions (OAuth & Permissions) Add these Bot Token Scopes: app_mentions:read channels:history channels:read chat:write emoji:read groups:history groups:read im:history im:read mpim:history mpim:read reactions:read users:read Enable Events Event Subscriptions → Enable Add Request URL (from n8n Slack Trigger node) Subscribe to bot events: app_mention message.channels message.groups message.im message.mpim reaction_added Install App Install App → Install to Workspace Copy Bot User OAuth Token (xoxb-...) 2. Configure n8n Import & Setup Import this JSON template Slack Trigger node: Add Slack credential with Bot Token Copy webhook URL Paste in Slack Event Subscriptions Request URL Anthropic Chat Model node: Add Anthropic API credential Model: claude-haiku-4-5-20251001 (You can replace it with other chat models) MCP Client node: Endpoint: https://mcp.explorium.ai/mcp Header Auth: Add Explorium API key Usage Examples @ExploriumAgent find tech companies in SF with 50-200 employees @ExploriumAgent show Microsoft's technology stack @ExploriumAgent get CMO contacts at healthcare companies `. An n8n automation workflow template by explorium.

By edisantosa

This n8n workflow ensures data freshness in the RAG system by handling modifications to existing files. It complements the "Document Ingestion" workflow by triggering whenever a file in the monitored Google Drive folder is updated. This "delete-then-re-insert" process ensures the RAG agent always has access to the most current version of your documents. Key Features & Workflow: Update Trigger: The workflow activates using the File Updated trigger for the same Google Drive folder ("DOCUMENTS"). Duplicate Run Prevention: An If node cleverly filters out immediate "update" events that are triggered by the "Upload Doc" workflow's Word-to-Google-Doc conversion, preventing unecessary duplicate runs. Delete Old Entries: Once a genuine update is detected, the workflow's first action is to find and delete all existing vector chunks associated with that file_id from the Supabase "documents" table. Smart Versioning: It then retrieves the old version number from the deleted metadata and uses an OpenAI node (Set Version) to intelligently increment it (e.g., "v1" becomes "v2"). Re-Ingestion Pipeline: The updated file is then processed through the exact same logic as the "Upload Doc" workflow: It is routed by a Switch node based on its MIME type (PDF, Google Doc, Excel, etc.). Text is extracted, chunked, and embedded. The Enhanced Default Data Loader enriches these new chunks with metadata, including the new, incremented version number. Insert New Entries: Finally, the newly processed and versioned chunks are inserted back into the Supabase Vector Store. An n8n automation workflow template by edisantosa.

By edisantosa

This n8n workflow is the data ingestion pipeline for the "RAG System V2" chatbot. It automatically monitors a specific Google Drive folder for new files, processes them based on their type, and inserts their content into a Supabase vector database to make it searchable for the RAG agent. Key Features & Workflow: Google Drive Trigger: The workflow starts automatically when a new file is created in a designated folder (named "DOCUMENTS" in this template). Smart File Handling: A Switch node routes the file based on its MIME type (e.g., PDF, Excel, Google Doc, Word Doc) for correct processing. Multi-Format Extraction: PDF: Text is extracted directly using the Extract PDF Text node. Google Docs: Files are downloaded and converted to plain text (text/plain) and processed by the Extract from Text File node. Excel: Data is extracted, aggregated, and concatenated into a single text block for embedding. Word (.doc/.docx): Word files are automatically converted into Google Docs format using an HTTP Request. This newly created Google Doc will then trigger the entire workflow again, ensuring it's processed correctly. Chunking & Metadata Enrichment: The extracted text is split into manageable chunks using the Recursive Character Text Splitter (set to 2000-character chunks). The Enhanced Default Data Loader then enriches these chunks with crucial metadata from the original file, such as file_name, creator, and created_at. Vectorization & Storage: Finally, the workflow uses OpenAI Embeddings to create vector representations of the text chunks and inserts them into the Supabase Vector Store. An n8n automation workflow template by edisantosa.

By Praneel S

⚠️ Disclaimer: This workflow uses WhatsApp, Google Calendar, and Gmail nodes that must be configured manually. Who’s it for This workflow is built for professionals, teams, and automation enthusiasts who want to manage their Google Calendar and Gmail directly from WhatsApp, powered by an AI assistant using OpenAI GPT or Google Gemini. It enables users to chat naturally through WhatsApp to schedule meetings, send emails, and check events — all without opening Gmail or Google Calendar. How it works The WhatsApp Trigger node captures incoming messages from users. The AI Agent (powered by Gemini or GPT) interprets user queries and determines the best tool to use. The Simple Memory node keeps context between messages using the user’s phone number. The Google Calendar nodes handle: Listing, creating, and updating events. Checking your availability before scheduling. The Gmail nodes handle: Sending emails. Reading and summarizing recent messages. The Date & Time node converts natural language like “next Monday at 3 PM” into proper ISO time format. The assistant responds via Send WhatsApp Response, sending clear confirmations and replies. Features Manage Gmail and Calendar entirely via WhatsApp. AI-powered understanding of natural language commands. Integrated with Google Meet for automatic conferencing links. Short-term memory for context retention. Fully modular – swap Gemini with OpenAI GPT or any LLM. Setup Steps Configure WhatsApp Cloud API via Meta for Developers. Set up Google Calendar and Gmail OAuth2 credentials. Add your Google API keys and calendar email. Connect your OpenAI or Gemini model credentials. Activate and test the workflow with messages like: “Schedule a meeting tomorrow at 5 PM.” “Check my latest emails.” “Send an email to alex@example.com about our project.” Requirements n8n instance (self-hosted or cloud) WhatsApp Business API (Meta Developer Account) Google Workspace or Gmail account OpenAI API key or Google Gemini API key Properly configured webhooks for WhatsApp Trigger Example Prompts “What’s on my calendar this week?” “Email John to confirm our meeting.” “When am I free tomorrow afternoon?” Customization Replace Gemini with OpenAI GPT in the AI Agent node. Adjust memory length for longer or shorter conversations. Add Slack or Teams notification nodes. Modify the prompt personality or response tone. Credits Created by Praneel For detailed setup help, visit praneel.tech/contact. An n8n automation workflow template by Praneel S.

By Matty Reed

Ingest meeting webhooks, process transcript, classify the meeting, generate structured notes with AI Agent, file the transcript to Google Drive, write rich pages to Notion, and create assigned tasks. Includes optional polling path if webhooks aren’t available. Who is this for? Teams that record calls and want instant, structured notes in Notion, with transcripts archived in Google Drive and action items auto-created—without manual copy/paste. What problem does it solve? Manual note taking is slow and inconsistent. This flow listens for a meeting webhook, flattens the transcript, classifies the call, runs a tailored notetaker prompt, and writes a clean Notion page plus tasks—hands-free and standardized. How it works | # | Node | Purpose | |---|------|---------| | 1 | New Meeting Webhook | Receives meeting payload with transcript segments and metadata. (Webhook Node) | | 2 | Flatten Transcript (Code) | Joins segments to speaker: text lines and extracts title, meetingId, url. | | 3 | Set Title + Transcript + URL | Normalizes fields for downstream nodes. | | 4 | Categorize Meeting | Uses OpenAI to return { "meetingType": "DiscoveryCall" | "MiscMeeting" }. (OpenAI) | | 5 | Switch | Routes to the correct notetaker branch based on meetingType. | | 6a | Discovery Call Notetaker | Anthropic model + structured parser to extract sales-specific fields. (Anthropic Docs) | | 6b | Misc Meeting Notetaker | General meeting notetaker with strict JSON schema. | | 7a | Add Discovery Meeting Notes to Notion | Writes a formatted page with overview, goals, pains, risks, and action items. | | 7b | Add Meeting Notes to Notion | Writes a simpler page for non-discovery meetings. | | 8 | Set Notion Page ID | Captures created page ID and the action-items array. | | 9 | Create File (Google Drive) | Saves raw transcript text and returns the file ID. (Drive API) | | 10 | Link Transcript in Notion | Updates the Notion page with a viewable Drive link. | | 11 | Split out Tasks | Expands the action-items array to one item per execution. | | 12 | If Assigned to Me | Filters tasks where assignee = "Matty Reed". | | 13 | Add Tasks (Notion) | Creates tasks in your Notion Tasks DB, links to the meeting page. (Notion API) | | * | (Optional polling path) | If webhooks aren’t available: Schedule Trigger → Get Meetings from Notion → List Meetings (HTTP Request) → Get New Meetings (Code) → Get Transcript (HTTP) → Transcript Ready? → Wait → Flatten. Disabled by default. | Setup steps Import the JSON flow into n8n Confirm nodes marked disabled stay off unless you need the polling path. Docs: n8n Credentials OpenAI: add API key and attach to Categorize Meeting. Anthropic: add API key and attach to both notetaker agents. Notion: create an internal integration, share your Meetings and Tasks databases with it, then attach the credential to Notion nodes. Google Drive: OAuth2 credential for Create File. Map your databases and properties Replace the placeholder Notion database IDs with your Meetings and Tasks DB IDs. Verify property names like Meeting Name|title, Summary|rich_text, Category|multi_select, Assignee|people, etc., match your schema. Drive folder Update the folderId in Create File to your preferred folder. Ensure link-sharing fits your privacy policy. Webhook Expose New Meeting Webhook via your n8n instance. Send a sample payload from your meeting recorder to verify the calendar_invitees, transcript, title, and url fields match the code node expectations. Test Run the flow with a recorded meeting. Confirm: Page created in Meetings DB with structured sections. Transcript file created in Drive and linked back to Notion. Tasks created in Tasks DB when assignee = "Matty Reed". Notes and tips Schemas are strict.** Both notetakers output fixed JSON keys. Missing values become empty strings. PII handling.** Transcripts may include personal data. Limit access to Notion pages and Drive files per policy. Do not hardcode secrets.** Store API keys in n8n credentials. Avoid putting tokens in Code nodes. Rate limits.** Long transcripts increase token usage. Consider chunking upstream if needed. Extensibility.* Add more branches in *Switch** for other meeting types with custom prompts and parsers. Resources n8n Webhook Node – https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/ n8n HTTP Request Node – https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/ OpenAI Responses – https://platform.openai.com/docs/guides/realtime-and-responses/responses Anthropic Docs – https://docs.anthropic.com/en/docs Notion API – https://developers.notion.com/docs Google Drive API – https://developers.google.com/drive/api. An n8n automation workflow template by Matty Reed.

By higashiyama

AI Team Morale Monitor Who’s it for For team leads, HR, and managers who want to monitor the emotional tone and morale of their teams based on message sentiment. How it works Trigger: Runs every Monday at 9 AM. Config: Defines your Teams and Slack channels. Fetch: Gathers messages for the week. AI Analysis: Evaluates tone and stress levels. Aggregate: Computes team sentiment averages. Report: Creates a readable morale summary. Slack Post: Sends report to your workspace. How to set up Connect Microsoft Teams and Slack credentials. Enter your Team and Channel IDs in the Workflow Configuration node. Adjust the schedule if desired. Requirements Microsoft Teams and Slack access. Gemini (or OpenAI) API credentials set in AI nodes. How to customize Modify the AI prompts for different insight depth. Replace Gemini with other LLMs if preferred. Change posting platform or format. Note: This workflow uses only linguistic data — no personal identifiers or private metadata. An n8n automation workflow template by higashiyama.

By Ranjan Dailata

This workflow automates company research and intelligence extraction from Glassdoor using Decode API for data retrieval and Google Gemini for AI-powered summarization. Who this is for This workflow is ideal for: Recruiters, analysts, and market researchers looking for structured insights from company profiles. HR tech developers and AI research teams needing a reliable way to extract and summarize Glassdoor data automatically. Venture analysts or due diligence teams conducting company research combining structured and unstructured content. Anyone who wants instant summaries and insights from Glassdoor company pages without manual scraping. What problem this workflow solves Manual Data Extraction**: Glassdoor company details and reviews are often scattered and inconsistent, requiring time-consuming copy-paste efforts. Unstructured Insights**: Raw reviews contain valuable opinions but are not organized for analytical use. Fragmented Company Data**: Key metrics like ratings, pros/cons, and FAQs are mixed with irrelevant data. Need for AI Summarization**: Business users need a concise, executive-level summary that combines employee sentiment, culture, and overall performance metrics. This workflow automates data mining, summarization, and structuring, transforming Glassdoor data into ready-to-use JSON and Markdown summaries. What this workflow does The workflow automates the end-to-end pipeline for Glassdoor company research: Trigger Start manually by clicking “Execute Workflow.” Set Input Fields Define company_url (e.g., a Glassdoor company profile link) and geo (country). Extract Raw Data from Glassdoor (Decodo Node) Uses the Decodo API to fetch company data — including overview, ratings, reviews, and frequently asked questions. Generate Structured Data (Google Gemini + Output Parser) The Structured Data Extractor node (powered by Gemini AI) processes raw data into well-defined fields: Company overview (name, size, website, type) Ratings breakdown Review snippets (pros, cons, roles) FAQs Key takeaways Summarize the Insights (Gemini AI Summarizer) Produces a detailed summary highlighting: Company reputation Work culture Employee sentiment trends Strengths and weaknesses Hiring recommendations Merge and Format Combines structured data and summary into a unified object for output. Export and Save Converts the final report into JSON and writes it to disk as C:\{{CompanyName}}.json. Binary Encoding for File Handling Prepares data in base64 for easy integration with APIs or downloadable reports. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n instance** (cloud or self-hosted) Decodo API credentials** (added as decodoApi) Google Gemini (PaLM) API credentials** Access to the Glassdoor company URLs Make sure to install the Decodo Community Node. Steps Import this workflow JSON file into your n8n instance. Configure your credentials for: Decodo API Google Gemini (PaLM) API Open the Set the Input Fields node and replace: company_url → with the Glassdoor URL geo → with the region (e.g., India, US, etc.) Execute the workflow. Check your output folder (C:\) for the exported JSON report. How to Customize This Workflow You can easily adapt this template to your needs: Add Sentiment Analysis** Include another Gemini or OpenAI node to rate sentiment (positive/negative/neutral) per review. Export to Notion or Google Sheets** Replace the file node with a Notion or Sheets integration for live dashboarding. Multi-Company Batch Mode** Convert the manual trigger to a spreadsheet or webhook trigger for bulk research automation. Add Visualization Layer** Connect the output to Looker Studio or Power BI for analytical dashboards. Change Output Format** Modify the final write node to generate Markdown or PDF summaries using the pypandoc or reportlab module. Summary This n8n workflow combines Decode web scrapping with Google Gemini’s reasoning and summarization power to build a fully automated Glassdoor Research Engine. With a single execution, it: Extracts structured company details Summarizes thousands of employee reviews Delivers insights in an easy-to-consume format Ideal for: Recruitment intelligence Market research Employer branding Competitive HR analysis. An n8n automation workflow template by Ranjan Dailata.

By Jaures NYA

This workflow automates the process of generating personalized UGC (User-Generated Content) images based on form submissions. It accepts a form with a character type (e.g., male/female) and an uploaded image, merges them, sends them to an AI model (Google Gemini via OpenRouter) for creative generation, and posts the resulting content as a Telegram photo message. Who’s it for This automation template is designed for marketers, AI creators, content teams, or interactive community platforms that want to let users submit content (image + character type), enrich it with AI-generated descriptions, and instantly publish results to Telegram — without writing a single line of code. How it works Trigger: Workflow starts when a form is submitted by a user. Extract file: The uploaded image file is converted to a Base64 string. Merge data: The character type and image data are combined into one payload. Format to Data URL: The image is wrapped as a proper data:image/... format for API use. Prepare payload: The text and image are mapped into a structure compatible with Gemini API. Generate AI content: Sends the input to Google Gemini (via OpenRouter) to generate a UGC description. Transform response: Cleans and extracts the result from Gemini’s response. Convert back to file: Transforms the Base64 image back into a real image file. Send to Telegram: The image and its AI-generated description are sent as a photo message to your Telegram channel. How to use Set up a form with a dropdown for character type (e.g., Male/Female) and an image upload field. Configure the Gemini API access through OpenRouter. Connect your Telegram bot and channel to receive the final result. Start the workflow → users submit the form, and their data is processed and shared as AI-enhanced UGC. Requirements OpenRouter API key to access Google Gemini. A Telegram Bot connected to your Telegram channel. ❓ Need help Contact me for consulting and support: LinkedIn / YouTube / Skool. An n8n automation workflow template by Jaures NYA.