Browse 13,012 Workflows

By Calistus Christian

Pulls free business and economic headlines from multiple publicly available RSS feeds (e.g., Reuters, Wall Street Journal, Federal Reserve, St. Louis Fed, BNP Paribas, WTO). De-duplicates stories, keeps only the last 24 hours, and limits to a manageable number. Uses OpenAI to generate a concise market brief with sections and "Why it matters." Sends a clean HTML email via Gmail. Category: Business / Economics / News\ Time to set up: ~10--15 minutes\ Difficulty: Beginner--Intermediate\ Cost: Free (except minimal OpenAI tokens if summarization is used) * What you'll need n8n (recent version) OpenAI credentials (for summaries, optional if you want raw feeds only) Gmail (or SMTP) credentials A few free RSS feed URLs (swap in/out as you like) * Set up steps Trigger -- Add a Cron to run daily (pick your time and timezone). Fetch -- Add one RSS Read node per source and connect all to a Merge (append). De-duplicate (this run) -- Add Remove Duplicates and compare on a stable key (prefer the article URL). Freshness -- Add an IF to pass only items published in the last 24 hours. Limit -- Add Limit to cap the total items (e.g., 25). Summarize -- Add OpenAI → Message a model to produce a JSON brief with subject + HTML body. Email -- Add Gmail → Send to deliver the brief to your inbox. * Tips & troubleshooting If everything gets discarded at de-dup while testing, switch to "within current input" or reset the node's stored values. If no items pass the IF, widen the date window temporarily (some feeds publish late). If the email arrives blank, ensure Gmail email type is set to HTML and the subject/body fields map to the model's output. * Free sources you can start with (swap freely) Yahoo News Financial Times. An n8n automation workflow template by Calistus Christian.

By Ronnie Craig

Coach Onboarding & Training Automation - Setup Guide Prerequisites n8n instance (self-hosted or cloud) Google Sheets account Twilio account with SMS-enabled phone number Setup Steps 1. Configure Settings Node Update the "Configuration Settings" node with: GOOGLE_SHEET_ID: Your Google Sheets ID from the URL TWILIO_PHONE_NUMBER: Your Twilio number (format: +1XXXXXXXXXX) BUSINESS_NAME: Your company name TRAINING_PROGRAM_NAME: Your program name MAIN_PRODUCT_NAME: Your main product/service 2. Create Google Sheets Database Create a new Google Sheet with 2 tabs: Sheet1 (Coaches) - Column headers: Name | Phone | Email | Goals | Status | Start Date | Current Day | Last Contact Sheet2 (Training Content) - Column headers: Day | Topic | Message | Audio_URL Add your 30-day training content to Sheet2 (rows 1-30). 3. Setup Credentials in n8n Google Sheets OAuth2 API: Name: "Google Sheets account" Follow Google OAuth setup in n8n Twilio API: Name: "Twilio account" Account SID: Your Twilio SID Auth Token: Your Twilio Auth Token 4. Configure Webhooks Registration Webhook: /webhook/coach-registration Accepts POST with: name, phone, email, goals Response Webhook: /webhook/coach-response Configure in Twilio for incoming SMS 5. Activate Workflow Enable the workflow and test with sample data. Testing Test registration: curl -X POST https://your-n8n-url/webhook/coach-registration \ -H "Content-Type: application/json" \ -d '{"name":"Test Coach","phone":"5551234567","email":"test@example.com","goals":"Test goals"}' Troubleshooting SMS not sending: Verify Twilio credentials Check phone number format (+1XXXXXXXXXX) Confirm Twilio account has balance Google Sheets errors: Verify OAuth permissions Check column names match exactly Ensure Sheet ID is correct Daily automation not running: Check cron schedule is active Verify timezone settings Confirm coaches have "active" status 3. description.md - Marketplace Description (Use the marketplace description from artifact #2, or create a shorter version): Coach Onboarding & Training Automation Automate coaching business onboarding with SMS-based 30-day training programs. Features Automated coach registration via webhook Daily training SMS delivery (9 AM) Smart keyword auto-responses Progress tracking in Google Sheets Weekly motivation messages Audio lesson support SMS compliance (STOP handling) Use Cases Business coaches scaling onboarding Sales trainers automating team development Course creators with SMS follow-up Network marketing team training Requirements Google Sheets account Twilio account with SMS number OPTIONAL: Screenshots If possible, include: Workflow overview screenshot Sample Google Sheets structure Example SMS messages received. An n8n automation workflow template by Ronnie Craig.

By Rahul Joshi

Description: Accelerate VIP support handling with this n8n workflow template that automatically identifies high-priority customers and ensures their tickets get instant attention. This automation pulls customer ticket data from Google Sheets, checks for the VIP tag, and seamlessly creates a priority task in ClickUp, while sending an instant Telegram alert to your team. What This Template Does: 🔍 Detects VIP-tagged customers in real time 📝 Creates high-priority ClickUp tasks for their tickets 📱 Sends Telegram alerts with ticket details (subject + requester email) 📊 Organizes VIP workload for easy tracking in ClickUp Built-in logic ensures: • Only VIP-tagged customers are escalated • Priority tasks are auto-assigned without delays • Teams receive instant notifications for fast response • No missed high-value customer interactions Requirements: • Google Sheets API credentials • ClickUp API credentials • Telegram Bot token & Chat ID • n8n instance (self-hosted or cloud) Perfect For: Customer support teams, sales organizations, and service-based businesses who need to prioritize VIP tickets instantly and streamline customer experience. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description: Stay on top of your support pipeline with this Ticket Status Digest automation for Zendesk. Built in n8n, this workflow automatically fetches tickets from Zendesk, filters only open ones, enriches them with requester details, and saves them into Google Sheets. 📊 Instead of manually checking Zendesk, you get a real-time digest of pending tickets with full customer details—perfect for support leads who need a quick snapshot of unresolved cases. Whether you’re tracking team workload, prioritizing open issues, or preparing daily status reports, this automation ensures your support data is always structured, centralized, and up to date. 🚀 What This Template Does (Step-by-Step) 🔔 Trigger – Manual Start (or Schedule) Begin workflow with a manual trigger (ideal for testing). Can be switched to scheduled runs (daily, hourly) for automated digests. 🎫 Fetch All Tickets (Zendesk) Pulls all tickets from Zendesk API. Captures ticket ID, subject, description, status, priority, tags, and timestamps. 🔍 Filter Open Tickets Only Includes only tickets where status = open. Skips closed, solved, or pending tickets. 👤 User Information Enrichment Looks up requester details (name, email, organization). Converts raw IDs into human-readable contact info. 📊 Save to Google Sheets Appends/updates ticket rows in “Ticket status dummy → Sheet1”. Columns: Ticket No. | Description | Status | Owner | Email | Tag. Required Integrations: Zendesk API (OAuth or API Key) Google Sheets (OAuth2 credentials) Best For: 🧑‍💼 Support leads monitoring unresolved tickets 📈 Managers building daily ticket status dashboards 🤝 Teams that need centralized visibility of customer issues ⏱️ Anyone tired of manual Zendesk data exports Key Benefits: ✅ Automated ticket sync to Google Sheets ✅ Real-time visibility of open issues ✅ Centralized view with enriched requester details ✅ Reduces manual tracking and reporting ✅ Scalable for daily, weekly, or custom digest runs. An n8n automation workflow template by Rahul Joshi.

By Tamas Demeter

This n8n template shows you how to turn outbound sales into a fully automated machine: scrape verified leads, research them with AI, and fire off personalized cold emails while you sleep. Use cases are simple: scale B2B lead gen without hiring more SDRs, run targeted outreach campaigns that don’t feel generic, and give founders or agencies a repeatable system that books more calls with less effort. Good to know At time of writing, each AI call may incur costs depending on your OpenAI plan. This workflow uses Apollo/Apify for lead scraping, which requires an active token. Telegram approval flow is optional but recommended for quality control. How it works Define your ICP (role, location, industry) in the workflow. Generate Apollo search URLs and scrape verified contacts. AI enriches leads with personal + company research. Hormozi-style cold emails are generated and queued for approval. Approve drafts in Telegram, then Gmail automatically sends them out. How to use Start with the included Schedule Trigger or replace with a Webhook/Form trigger. Adjust ICP settings in the Set node to fit your target audience. Test with a small batch of leads before scaling to larger runs. Requirements Google Sheets, Docs, Drive, and Gmail connected to n8n Apollo/Apify account and token OpenAI API key Telegram bot for approvals Customising this workflow Swap Apollo scraping with another data source if needed. Adapt the AI prompt for a different email tone (formal, friendly, etc.). Extend with a CRM integration to sync approved leads and outreach results. An n8n automation workflow template by Tamas Demeter.

By Davide Boizza

This workflow automates analyzing Gmail threads and drafting AI-powered replies with the new model Anthropic Sonnet 4.5. This workflow automates the process of analyzing incoming emails and generating context-aware draft replies by examining the entire email thread. Key Advantages ✅ Time-Saving – Automates repetitive email replies, reducing manual workload. ✅ Context-Aware Responses – Replies are generated using the entire email thread, not just the latest message. ✅ Smart Filtering – The classifier prevents unnecessary drafts for spam or promotional emails. ✅ Human-in-the-Loop – Drafts are created instead of being sent immediately, allowing manual review and corrections. ✅ Scalable & Flexible – Can be adapted to different accounts, reply styles, or workflows. ✅ Seamless Gmail Integration – Directly interacts with Gmail threads and drafts via OAuth. How it Works This workflow automates the process of analyzing incoming emails and generating context-aware draft replies by examining the entire email thread. Trigger & Initial Filtering: The workflow is automatically triggered every minute by the Gmail Trigger node, which detects new emails. For each new email, it immediately performs a crucial first step: it uses an AI Email Classifier to analyze the email snippet. The AI determines if the email is a legitimate message that warrants a reply (categorized as "ok") or if it's spam, a newsletter, or an advertisement. This prevents the system from generating replies for unwanted emails. Context Aggregation: If an email is classified as "ok," the workflow fetches the entire conversation thread from Gmail using the threadId. A Code Node then processes all the messages in the thread, structuring them into a consistent format that the AI can easily understand. AI-Powered Draft Generation: The structured conversation history is passed to the Replying email Agent with Sonnet 4.5. This agent, powered by a language model, analyzes the entire thread to understand the context and the latest inquiry. It then drafts a relevant and coherent HTML email reply. The system prompt instructs the AI not to invent information and to use placeholders for any missing details. Draft Creation: The final step takes the AI-generated reply and the original email's metadata (subject, recipient, threadId) and uses them to create a new draft email in Gmail. This draft is automatically placed in the correct email thread, ready for the user to review and send. Set up Steps To implement this automated email reply system, you need to configure the following: Configure Gmail & OpenAI Credentials: Ensure the following credentials are set up in your n8n instance: Gmail OAuth2 Credentials: The workflow uses the same Gmail account for the trigger, fetching threads, and creating drafts. Configure this in the "Gmail Trigger," "Get a thread," and "Create a draft" nodes. OpenAI API Credentials: Required for both the "Email Classifier". Provide your API key in the respective OpenAI Chat Model nodes. Anthropic API Credentials: Required for the main "Replying email Agent." Provide your API key in the respective Antrhopic Chat Model nodes. Review AI Classification & Prompting: Email Filtering: Check the categories in the Email Classifier node. The current setup marks only non-advertising, non-newsletter emails as "ok." You can modify these categories to fit your specific needs and reduce false positives. Reply Agent Instructions: Review the system message in the Replying email Agent. You can customize the AI's persona, tone, and instructions (e.g., making it more formal, or instructing it to sign with a specific name) to better align with your communication style. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Karol Otręba

How it works This workflow automates publishing content from any RSS feed directly to Facebook and Instagram. It reads new RSS entries, extracts the article content, generates a short social-media-friendly summary using an AI model, and then creates an AI-generated image based on the topic. The post is uploaded to Facebook and Instagram (via Graph API) and logged in Google Sheets for reference. Finally, a Telegram bot sends you a notification with links to the published posts. Set up steps Insert your RSS feed URL in the RSS Feed Trigger node. Configure Google Sheets credentials and replace the example sheet with your own. In Supabase Config, insert your Supabase URL and bucket name. In Facebook/Instagram nodes, replace [INSERT_YOUR_SITE_ID] with your own page or account ID. Connect your Facebook Graph API credentials (remove hardcoded tokens). Connect your OpenAI / Anthropic / Gemini credentials for text and image generation. Set up your Telegram Bot credentials if you want to receive notifications. Notes • Sticky notes inside the workflow explain each section (RSS trigger, filtering, content generation, posting, logging, notifications). • No credentials are saved in the template – you must connect your own before running. • All generated content (text + images) is fully automated but can be customized (e.g. change AI prompts for your preferred style). An n8n automation workflow template by Karol Otręba.

By 8Automator

Example generated with this workflow: Simply upload a image and a watermark file, and the workflow will automatically combine them into a professional watermarked image. Use cases include adding logos to content, branding product photos, or protecting images with copyright marks. Good to know Completely free solution with no ongoing costs or subscriptions Processing typically takes 5-15 seconds depending on image size The workflow uses a polling mechanism to check job completion every 3 seconds Supports standard image formats (PNG, JPG, etc.) No credit card required to get started How it works The Form Trigger creates a user-friendly upload interface for two files: main image and watermark Both images are uploaded simultaneously to the API's file storage via parallel HTTP requests The uploaded file URLs are aggregated and used to create an image composition job The workflow polls the API every 3 seconds to check job completion status Once completed, the final watermarked image is downloaded and returned as a file download The watermark is automatically positioned in the bottom-right corner with 50% opacity, but this can be easily customized. How to use The form trigger provides a clean interface, but you can replace this with other triggers like webhooks or manual triggers if needed. The workflow handles all file processing automatically and returns the result as a downloadable file. Requirements Free account at jsoncut.com API key with full access (generated at app.jsoncut.com) HTTP Header Auth credential configured in n8n with header name x-api-key Setup steps Sign up for a free account at jsoncut.com Navigate to your dashboard at app.jsoncut.com → API Keys and create a new key with full access In n8n, create an HTTP Header Auth credential named "JsonCut API Key" Set the header name to x-api-key and the value to your API key Apply this credential to all HTTP Request nodes in the workflow Customising this workflow The watermark positioning, size, and opacity can be easily adjusted by modifying the JSON body in the "Create Job" node. You can change: Position coordinates (x, y values from 0 to 1) Watermark dimensions (width, height in pixels) Transparency (opacity from 0.1 to 1.0) Output image dimensions Fit options (cover, contain, fill) For more advanced image generation examples and configuration options, check out the documentation and image generation examples. For bulk processing, you could extend this workflow to handle multiple images or integrate it with cloud storage/database services. An n8n automation workflow template by 8Automator.

By Lenouar

Automate Video Editing with AI Who’s it for This workflow is ideal for content creators, training providers, agencies, and businesses that need to quickly turn raw videos into polished, captioned, or narrated content — without hiring editors or spending hours in manual editing tools. It’s especially valuable for those who want full freedom of video editing capacity on their own platform instead of relying on costly SaaS tools with heavy limitations, recurring fees, or watermarks. With this template, you get enterprise-grade AI editing self-hosted in your n8n, under your control. Perfect for: E-learning & educators** producing accessible multilingual lessons Corporate trainers** automating internal tutorials and compliance walkthroughs Social media teams** creating captioned, high-engagement clips Product teams** generating quick demos and explainer videos How it works / What it does This template combines AI transcription, TTS voiceover, and video editing with FFmpeg into a single automated pipeline: Voiceover Mode** Transcribes video with OpenAI Whisper Cleans text using on-screen frames for accuracy Generates natural AI voiceovers (EN/AR) with OpenAI Speech Re-times the video to match the narration → synced professional dub Subtitle Mode** Merges multiple video clips with FFmpeg Transcribes or translates audio to generate SRT subtitles Hardcodes captions directly into the final MP4 (style customizable) ✅ Output: a ready-to-publish MP4 with AI voiceover or burned-in subtitles. Requirements n8n self-hosted or cloud instance Server with FFmpeg installed OpenAI API key** (Whisper + Speech) (Optional) Google Drive credentials for delivery How to customize the workflow Swap voices in the OpenAI Speech node (change “ash” / “verse” to another). Add languages by extending the dropdown in the Upload Video form. Change subtitle style (font, margins, background) in the Apply Subtitle node. Route final videos to Slack, Notion, or Dropbox instead of Drive. Why it matters / Benefits ⚡ Save hours of manual editing — no need for Premiere/DaVinci for basic voiceovers and captions. 💰 Cut production costs — avoid hiring voice actors and editors for every video. 🌍 Multilingual content instantly — create English ↔ Arabic versions without re-recording. 📈 Boost engagement — subtitles increase video watch time on social media. 🎨 Professional results on autopilot — clean transcripts, natural AI voices, synced visuals. 💡 SaaS vs Self-Hosted Descript, Kapwing, Synthesia** → $30–100/month per user, limited exports, watermarks on free tiers. This workflow* → one-time template + your own server, only pay *OpenAI usage (~$0.006/min for Whisper)**. You get unlimited exports, no restrictions, and full data ownership. What you win buying this template A ready-made AI editing studio inside n8n. End-to-end automation: upload → AI → polished video. Works for solo creators and agencies delivering client-ready assets. Scales with your content: handle 1 video or 100, just drop them in. 👉 By purchasing, you get: Full workflow JSON file. Email delivery with setup guidelines. Access to a step-by-step walkthrough video. Contact Us** via services@quantumti.ae. An n8n automation workflow template by Lenouar.

By Dmytro

Description This workflow allows you to turn any idea for a post into platform-specific content using AI. You simply provide the concept, topic, or description of a post, and the AI generates drafts adapted to multiple social media platforms — LinkedIn, Telegram, TikTok, YouTube, X/Twitter, Instagram, Bluesky and Threads. Posts are created in PostPulse ready for review, scheduling, or publishing. ⚠️ Disclaimer: This workflow uses the community node @postpulse/n8n-nodes-postpulse. Make sure community nodes are enabled in your n8n instance before importing and using this template. 👉 To install it: Go to Settings → Community Nodes → Install and enter:"@postpulse/n8n-nodes-postpulse". 💡 For more details, see n8n Integration Guide: PostPulse Developers – n8n Integration Who Is This For? Social media managers** who want to create content for multiple platforms quickly. Content creators** who need posts automatically adapted to different platforms’ character limits. Agencies** managing multiple accounts who want to save time on copywriting and formatting. What Problem Does This Workflow Solve? Instead of manually writing, adapting, and publishing posts, you get: AI-powered content creation:** Generate posts from any idea you provide. Platform optimization:** Posts are automatically adapted to platform-specific character limits and formatting. Seamless publishing:** Draft posts are sent to PostPulse for scheduling or immediate publishing. Hashtag suggestions:** AI adds relevant hashtags for each platform. Time saving:** Automates content generation and publishing, freeing you for more strategic tasks. How It Works This workflow takes your idea, generates platform-specific posts with AI, and sends them to PostPulse: 1. Idea input: Enter any post concept in the idea node. 2. Setting Restrictions and Hashtags: Optional: adjust character limits or the number of hashtags. 3. AI Content Adapter: Generates text for each platform based on the input idea. 4. Unification of Platforms and Text + Merge: Aligns AI-generated content with the correct platforms. 5. Publish Post: Creates draft posts in PostPulse ready for scheduling or publishing. Setup 1. Connect PostPulse to n8n Request your OAuth client key and secret from PostPulse support at support@post-pulse.com. Add your PostPulse account in the Credentials section in n8n. 2. Enter an idea in the idea node Type any concept, topic, or description of a post. 3. (Optional) Adjust restrictions in Setting Restrictions and Hashtags node Change maximum characters per platform or number of hashtags if desired. 4. Run the workflow AI generates platform-specific drafts and sends them to PostPulse as draft posts. Requirements Connected PostPulse accounts** (TikTok, Instagram, YouTube, LinkedIn, Telegram, Bluesky, X, Threads). OAuth client key and secret** obtained from PostPulse. An n8n instance** with community nodes enabled. ✨ With this workflow, PostPulse and n8n become your all-in-one automation hub for generating and publishing social media posts. How To Customize The Workflow This workflow is flexible and adaptable to your needs: Character limits:** Adjust maximum characters per platform while respecting platform limits. Hashtags:** Modify the number of hashtags added by the AI. AI prompt:** Change text tone or style in the AI Content Adapter node. Add platforms:** Extend supported platforms by updating platform mappings in the workflow. Scheduling:** Adjust scheduledTime in Publish Post node for automated scheduling. 💡 Tip: Fully functional out-of-the-box, but easily customizable to match your brand’s tone, posting strategy, or any platform-specific rules. An n8n automation workflow template by Dmytro.

By Luis Hernandez

Overview This comprehensive n8n workflow automates the generation and distribution of detailed monthly technical support reports from GLPI (IT Service Management platform). The workflow intelligently calculates SLA compliance, analyzes technician performance, and delivers professionally formatted HTML reports via email. ✨ Key Features Intelligent SLA Calculation Business Hours Tracking: Automatically calculates resolution time considering only working hours (excludes weekends and lunch breaks) Configurable Schedule: Customizable work hours (default: 8 AM - 12 PM, 1 PM - 6 PM) Dynamic SLA Monitoring: Real-time compliance tracking with configurable thresholds (default: 24 hours) Visual Indicators: Color-coded alerts for critical SLA breaches and high-volume warnings Comprehensive Reporting General Summary: Total cases, open, in-progress, resolved, and closed tickets Performance Metrics: Total and average resolution hours in both decimal and formatted (hours/minutes) display Technician Breakdown: Individual performance analysis per technician including case distribution and SLA compliance Smart Alerts: Automatic warnings for high case volumes (>100 in-progress) and critical SLA levels (<50%) Professional Email Delivery Responsive HTML Design: Mobile-optimized email templates with elegant styling Dynamic Content: Conditional formatting based on performance metrics Automatic Scheduling: Monthly execution on the 6th day to ensure accurate SLA measurement 💼 Business Benefits Time Savings Eliminates Manual Work: Saves 2-4 hours per month previously spent compiling reports manually Automated Data Collection: No more exporting CSVs or copying data between systems One-Click Setup: Configure once and receive reports automatically every month Improved Decision Making Real-Time Insights: Identify bottlenecks and performance issues immediately Technician Accountability: Clear visibility into individual and team performance SLA Compliance Tracking: Proactively manage service level agreements before they become critical Enhanced Communication Stakeholder Ready: Professional reports suitable for management presentations Consistent Format: Standardized metrics ensure month-over-month comparability Instant Distribution: Automatic email delivery to relevant stakeholders 🔧 Technical Specifications Requirements n8n instance (self-hosted or cloud) GLPI server with API access enabled Gmail account (or any SMTP-compatible email service) GLPI API credentials (App-Token and User credentials) Configuration Points Variables Node: Server URL, API tokens, entity name, work hours, SLA limits Schedule Trigger: Monthly execution timing (default: 6th of each month) Email Recipient: Target email address for report delivery Date Range Logic: Automatic previous month calculation Data Processing Retrieves up to 999 tickets per execution (configurable) Filters by entity and date range Excludes weekends and non-business hours from calculations Groups data by technician for detailed analysis 📋 Setup Instructions Prerequisites GLPI Configuration: Enable API and configure the Tickets panel with required fields (ID, -Title, Status, Opening Date, Closing Date, Resolution Date, Priority, Requester, Assigned To) API Credentials: Create Basic Auth credentials in n8n for GLPI API access Email Authentication: Set up Gmail OAuth2 or SMTP credentials in n8n Implementation Steps Import the workflow JSON into your n8n instance Configure the Variables node with your GLPI server details and business hours Set up GLPI API credentials in the HTTP Request nodes Configure email credentials in the Gmail node Update the recipient email address Test the workflow manually before enabling the schedule Activate the workflow for automatic monthly execution 🎯 Use Cases IT Support Teams: Track helpdesk performance and SLA compliance Service Managers: Monitor team productivity and identify training needs Executive Reporting: Provide high-level summaries to stakeholders Resource Planning: Identify workload distribution and capacity issues Compliance Auditing: Maintain historical records of SLA performance 📈 ROI Impact Time Savings: 24-48 hours annually in manual reporting eliminated Error Reduction: Eliminates human calculation errors in SLA tracking Faster Response: Early alerts enable proactive issue resolution Better Visibility: Data-driven insights improve team management. An n8n automation workflow template by Luis Hernandez.

By Vadim

What it does This workflow automates content syndication and posting to LinkedIn and X/Twitter. It takes existing long-form articles and generates from them engaging social posts optimized for each platform. The workflow takes links to existing articles from a given sitemap. It randomly selects the next article to republish, making sure that articles are not repeated. For simplicity it uses a Google spreadsheet to track the articles that have already been republished. Requirements Existing sitemap Google Gemini API key (or other model provider's key) Google Sheets credentials LinkedIn credentials X/Twitter credentials How to set up Adjust the schedule as needed (by default triggers daily at noon) Configure parameters in the parameters node: Set the sitemap URL (e.g. https://example.com/sitemap.xml) Set the language of the posts Enable/disable channels as needed Configure Google Sheets credentials for get processed articles and add processed articles nodes Create a new Google spreadsheet document with "url", "status", "timestamp", "LinkedIn post" and "Twitter post" columns Specify that spreadsheet document in get processed articles node (other nodes will take it from here) Add Google Gemini API key for the model (or change to any other model of choice) Configure LinkedIn and X/Twitter credentials for publishing. An n8n automation workflow template by Vadim.

By Muhammad Asadullah

Reddit Posts & Comments Scraper A powerful workflow to scrape Reddit posts and comments by keywords and/or subreddit, with intelligent filtering and formatting. How it works Search Reddit - Accepts keywords and/or subreddit parameters via webhook to search for relevant posts Filter & Sort - Filters posts by date (last 60 days), minimum upvotes (20+), removes duplicates, and sorts by popularity Extract Comments - For each post, retrieves and extracts the top 20 most upvoted comments with their reply threads Format Results - Structures all posts and comments into a clean, readable markdown report Return Data - Sends the formatted report back as a webhook response, ready for use in AI tools or other applications Set up steps Time to set up: ~10 minutes 1. Create Reddit App (5 minutes) Go to https://www.reddit.com/prefs/apps and create a new app Add your n8n URL and callback URL in the "redirect uri" field (you'll find this in the Reddit OAuth2 credentials setup in n8n) Copy your app's Client ID and Client Secret 2. Configure Reddit Credentials in n8n (2 minutes) In n8n, create new Reddit OAuth2 API credentials Paste your Client ID and Client Secret from step 1 Complete the OAuth2 authentication flow 3. Update Webhook URLs (2 minutes) Update the webhook URLs in the example HTTP request nodes to match your n8n instance URL The workflow has two webhooks: /webhook/reddit-search-keyword - for searching by keywords only /webhook/reddit-search-subreddit - for searching within a specific subreddit 4. Customize Filters (1 minute - optional) Date filter**: Line 6 in "Posted in Last x days" node (default: 60 days) Upvote filter**: "Upvotes Requirement Filtering" node (default: 20+ upvotes) Post limit**: "Limit" node (default: 10 posts) 5. Test the Workflow Use the example HTTP request nodes to test both search methods: Keywords only: ?keywords=your,keywords,here Subreddit search: ?keywords=your,keywords&subreddit=SubredditName Usage Examples Search by keywords: GET https://your-n8n.com/webhook/reddit-search-keyword?keywords=AI,machine learning Search within subreddit: GET https://your-n8n.com/webhook/reddit-search-subreddit?keywords=ChatGPT,GPT-4&subreddit=OpenAI The workflow returns a formatted text report with all posts, their metadata, and top comments ready for analysis or AI processing. An n8n automation workflow template by Muhammad Asadullah.

By Ossian Madisson

This n8n template allows you to, on a schedule, list all files that have been modified since the last execution in a Google Drive folder and in all its subfolders While Google Drive is accessible and easy to use, file listings via API are limited to either all files in the entire Drive or all files in a specific folder. This also means that the n8n triggers for Google Drive are limited to changes to a specific file or folder. This template is built to replace the built-in trigger nodes in the situations when you need to trigger on new or changed files in a folder or any of its subfolders. Use cases Trigger a RAG pipeline to update with new or updated documents Push newly uploaded or updated documents into CMS, project management tool or other external platform Log changes to build an audit trail Trigger a backup job or sync process only for files that have changed since the last run, saving bandwidth and processing time. Notify team or client about new documents Can also be run without the scheduling part to perform a one-time iteration of all files Good to know Works well if you attach a loop node to the "output node" to run additional actions on the files The workflow is designed to use a minimal amount of custom code, preferring built-in nodes in n8n Does not identify file removals How it works Recursively executes a subworkflow for each folder in the main folder Each subworkflow execution sends a list of all files in the folder to an "output node" that checks if the files was created or modified since the last execution When all subworkflows have been executed, the files in the main folder are sent to the "output node" A persistent variable (time of trigger node activation) is set for timestamp comparison on the next execution (this is only set on non-manually triggered active workflow executions) How to use Set schedule interval in the trigger node (default every 60min) Add Google Drive credentials to the four Google Drive nodes Define your main/root folder in the two nodes inside the red box Connect your workflow to process the files after the node in the yellow box, please note that there will be "one output" per folder. An n8n automation workflow template by Ossian Madisson.

By Ruslan Elishev

🛡️ BotGuard - Telegram Bot Authorization Layer What This Workflow Does Ever noticed how most Telegram bot tutorials assume everyone can just... use your bot? No questions asked, no protection, nothing. That's fine for a simple "Hello World" bot, but the moment you connect AI APIs, paid services, or sensitive operations - you're in trouble. Anyone who discovers your bot can drain your API credits, overload your systems, or access things they shouldn't. BotGuard fixes this in the simplest way possible: a whitelist. Only User IDs you explicitly allow can interact with your bot. Everyone else gets a polite "access denied" message. Plus, you get instant notifications when someone unauthorized tries to use your bot - complete with their User ID, so you can add them if they're legit. Think of it as a bouncer for your bot. No fancy authentication flows, no databases, no complexity. Just a clean authorization check that sits between the Telegram trigger and your actual workflow. Your expensive AI calls, paid API requests, and sensitive operations stay protected. 🚀 Getting Started in 2 Minutes Step 1: Import and Configure Import this workflow into n8n and connect your Telegram bot credentials. You'll see a clean workflow with sticky notes explaining everything. Step 2: Add Your User ID Don't know your Telegram User ID? No problem. Just message your bot - you'll get denied, but the message will show: Your User ID: 123456789. Copy that number. Open the "BotGuard Authorization" node and add yourself: const AllowedUsers = [ { userId: 222222222, userName: 'allowed_user_name', subscriptionType: 'admin' }, { userId: YOUR_USER_ID_HERE, userName: 'your_username', subscriptionType: 'premium' } ]; Step 3: Test It Save, activate the workflow, and message your bot again. You're in! Try from another account - denied. Check your admin account for the unauthorized access notification. 🎨 Making It Yours Want to Change the Messages? All user-facing messages are in the BotGuard Authorization node. Look for these lines: authorizedMessage - What approved users see (default: "✅ Authorization Successful...") userMessage - What denied users see (default: "🚫 Access Denied...") adminMessage - What you receive for each unauthorized attempt Make them friendlier, add your support contact, suggest a /request command - whatever fits your bot's personality. Need Subscription Tiers? The workflow already supports it! Each user has a subscriptionType field (basic/premium/admin). Use this in your main workflow to enable/disable features based on their tier. The BotGuard passes all this data forward in the botGuard object. Want Multiple Admins? Just add more entries to the Administrators array. Every admin receives notifications when unauthorized users attempt access: const Administrators = [ { userId: 111111111, userName: 'admin_user_name', chatId: 111111111 }, { userId: 333333333, userName: 'your_cofounder', chatId: 333333333 } ]; 💡 Why This Workflow Exists I built this after watching someone's OpenAI credits get drained in 3 hours because their bot went viral on a Telegram group. No authorization, no rate limiting, nothing. Just a helpful bot that cost them $200 before they noticed. Most tutorials skip authorization entirely - it's not sexy, not what people want to learn. But the moment you deploy something real, you need it. Instead of everyone reinventing the wheel with complex databases and auth systems, here's a simple pattern you can copy-paste into any bot workflow. The multi-admin notification system came from needing to know WHO was trying to access our bots. Sometimes it's legitimate users who found your bot organically. Sometimes it's automated scanners. Either way, if you want to know, now you can. 🔧 Real-World Tips After protecting dozens of production bots: Do: Keep the User ID list in code for small teams (5-50 users) - it's simple and works Set up admin notifications - you'll catch legitimate users before they give up Include the User ID in denial messages - makes it easy for users to request access Test with an unauthorized account first - make sure the denial flow is clear Don't: Hard-code thousands of users - if you're that big, use a database instead Skip the admin notifications - they're your early warning system Forget to update the placeholder IDs (111111111, etc.) - those won't work! Share your workflow publicly with real User IDs - privacy matters. An n8n automation workflow template by Ruslan Elishev.

By Greypillar

How it works • RSS feed monitors your blog for new posts automatically • Extracts and cleans full article content from the blog post • AI Chain (GPT-4o) transforms content into 5 platform-optimized formats (LinkedIn, Twitter, Instagram, Email, Video) • Unsplash API suggests relevant images for each content piece • Slack notification alerts content team with preview of all formats • Airtable logs everything for content calendar tracking • Optional auto-posting to LinkedIn and Twitter (disabled by default) • Structured output parser ensures all 5 formats are generated correctly with proper character limits Set up steps • Time to set up: 10-15 minutes • Replace RSS feed URL with your blog's feed (common formats: /feed, /rss, /feed.xml) • Get Slack channel ID for content team notifications • Create Airtable base with 14 columns (Original_Title, Original_URL, Published_Date, LinkedIn_Post, LinkedIn_Hashtags, Twitter_Thread, Twitter_Hashtags, Instagram_Caption, Instagram_Hashtags, Email_Subject, Email_Body, Video_Script, Suggested_Images, Status) • Add credentials: OpenAI (GPT-4o), Unsplash API, Slack OAuth2, Airtable Token • Replace placeholder IDs in Slack and Airtable nodes • Optional: Enable LinkedIn/Twitter auto-posting nodes and add OAuth2 credentials What you'll need • OpenAI API - GPT-4o access for AI content repurposing • Unsplash API - Free tier available for image suggestions • Slack - Standard workspace for team notifications • Airtable - Free plan works for content tracking • Blog with RSS feed - WordPress, Ghost, Medium, Webflow all supported • LinkedIn/Twitter OAuth2 (optional) - For auto-posting feature Who this is for Content creators, marketing teams, and agencies that want to maximize content ROI by automatically repurposing blog posts into platform-specific content. Perfect for B2B companies publishing regular blog content who need consistent multi-platform presence without manual reformatting. An n8n automation workflow template by Greypillar.

By Guilherme Campos

This n8n workflow automates the process of creating high-quality, scroll-stopping LinkedIn posts based on live research, AI insight generation, and Google Sheets storage. Instead of relying on recycled AI tips or boring summaries, this system combines real-time trend discovery via Perplexity, structured idea shaping with GPT-4, and content generation tailored to a bold, human LinkedIn voice. The workflow saves each post idea (with image prompt, tone, and summary) to a Google Sheet, sends you a Telegram alert, and even formats your content for direct publishing. Perfect for solopreneurs, startup marketers, or anyone who posts regularly on LinkedIn and wants to sound original, not robotic. Who’s it for Content creators and solopreneurs building an audience on LinkedIn Startup teams, PMs, and tech marketers looking to scale thought leadership Anyone tired of generic AI-generated posts and craving structured, edgy output How it works Daily trigger at 6 AM starts the workflow. Pulls recent post history from Google Sheets to avoid repeated ideas. Perplexity AI scans the web Generates 3 structured post ideas (including tone, hook, visual prompt, and summary). GPT-4 refines each into a bold, human-style LinkedIn post, following detailed brand voice rules. Saves everything to Google Sheets (idea, content, image prompt, post status). Sends a Telegram notification to alert you new ideas are ready. How to set up Connect your Perplexity, OpenAI, Google Sheets, and Telegram credentials. Point to your preferred Google Sheet and sheet tab for storing post data. Adjust the schedule trigger if you want more or fewer ideas per week. (Optional) Tweak the content style prompt to match your personal tone or niche. Requirements Perplexity API account OpenAI API access (GPT-4 or GPT-4-mini) Telegram bot connected to your account Google Sheets document with appropriate column headers How to customize the workflow Change the research sources or prompt tone (e.g., more tactical, more spicy, more philosophical) Add an image generation tool to turn prompts into visuals for each post Filter or tag ideas based on type (trend, tip, story, etc.) Post automatically via LinkedIn API or Buffer integration. An n8n automation workflow template by Guilherme Campos.

By Tegar karunia ilham

🎯 Smart Job Hunter Pro - AI-Powered Multi-Platform Job Automation Transform your job search with this comprehensive n8n workflow that automatically searches, analyzes, and applies to relevant positions across multiple job platforms. Perfect for developers, engineers, and tech professionals looking to streamline their job hunting process. ✨ Key Features 🔄 Multi-Platform Job Search**: Simultaneously searches Jooble, JobStreet, Indeed, and WhatJobs APIs 🤖 AI-Powered Job Analysis**: Uses Google Gemini AI to analyze job compatibility and generate tailored cover letters 📊 Smart Scoring System**: Automatically scores job matches based on your skills and requirements 📝 Auto-Apply Threshold**: Only applies to jobs above your specified compatibility score 📋 Notion Integration**: Automatically tracks applications in organized Notion database 💬 Telegram Notifications**: Real-time alerts for high-match job opportunities ☁️ Google Drive Storage**: Saves personalized cover letters for each application ⚠️ Error Handling**: Comprehensive error tracking with Telegram notifications ⏰ Automated Scheduling**: Runs every 8 hours to find fresh opportunities 🛠 What This Workflow Does Scheduled Search: Automatically searches multiple job platforms every 8 hours Data Normalization: Standardizes job data from different API sources AI Analysis: Gemini AI evaluates each job posting against your skills profile Smart Filtering: Only processes jobs above your compatibility threshold (default: 75%) Application Tracking: Creates detailed records in Notion with match scores and status Instant Alerts: Sends Telegram notifications for promising opportunities Cover Letter Generation: AI creates personalized cover letters for each position Document Management: Automatically saves all cover letters to Google Drive 🔧 Required Integrations Job APIs**: Jooble API, WhatJobs API (JobStreet & Indeed use web scraping) AI Service**: Google Gemini API for job analysis Productivity**: Notion database for application tracking Communication**: Telegram bot for notifications Storage**: Google Drive for cover letter management 💡 Perfect For Software Developers** seeking JavaScript, React, Node.js positions Full-Stack Engineers** wanting automated job discovery Tech Professionals** needing organized application tracking Remote Workers** searching across multiple platforms Career Changers** looking for systematic job hunting 🎛 Customizable Variables Job Keywords**: Define your target roles and skills Location & Radius**: Set geographic search parameters Auto-Apply Threshold**: Control compatibility score requirements Results Limit**: Adjust number of jobs per platform Schedule Frequency**: Modify search intervals 📈 Benefits Save 10+ hours weekly** on manual job searching Never miss opportunities** with automated monitoring Professional application tracking** with detailed analytics Personalized cover letters** for every application Instant notifications** for high-match positions Complete audit trail** of all job search activities 🚀 Getting Started Import the workflow to your n8n instance Configure API credentials for all job platforms Set up Notion database with provided template structure Create Telegram bot and Google Drive folder Customize job search parameters for your profile Activate workflow and start receiving opportunities! 📝 Additional Notes Uses placeholder credentials for security ({{PLACEHOLDER_API_KEY}}) Comprehensive error handling prevents workflow failures Includes detailed setup instructions via sticky notes Optimized for Indonesian job market (JobStreet.co.id) Easily adaptable for other regions and job types Perfect for developers, engineers, and automation enthusiasts who want to leverage AI and n8n's power to dominate their job search process! 🚀. An n8n automation workflow template by Tegar karunia ilham.

By Onur

🏠 Extract Zillow Property Data to Google Sheets with Scrape.do This template requires a self-hosted n8n instance to run. A complete n8n automation that extracts property listing data from Zillow URLs using Scrape.do web scraping API, parses key property information, and saves structured results into Google Sheets for real estate analysis, market research, and property tracking. 📋 Overview This workflow provides a lightweight real estate data extraction solution that pulls property details from Zillow listings and organizes them into a structured spreadsheet. Ideal for real estate professionals, investors, market analysts, and property managers who need automated property data collection without manual effort. Who is this for? Real estate investors tracking properties Market analysts conducting property research Real estate agents monitoring listings Property managers organizing data Data analysts building real estate databases What problem does this workflow solve? Eliminates manual copy-paste from Zillow Processes multiple property URLs in bulk Extracts structured data (price, address, zestimate, etc.) Automates saving results into Google Sheets Ensures repeatable & consistent data collection ⚙️ What this workflow does Manual Trigger → Starts the workflow manually Read Zillow URLs from Google Sheets → Reads property URLs from a Google Sheet Scrape Zillow URL via Scrape.do → Fetches full HTML from Zillow (bypasses PerimeterX protection) Parse Zillow Data → Extracts structured property information from HTML Write Results to Google Sheets → Saves parsed data into a results sheet 📊 Output Data Points | Field | Description | Example | |-------|-------------|---------| | URL | Original Zillow listing URL | https://www.zillow.com/homedetails/... | | Price | Property listing price | $300,000 | | Address | Street address | 8926 Silver City | | City | City name | San Antonio | | State | State abbreviation | TX | | Days on Zillow | How long listed | 5 | | Zestimate | Zillow's estimated value | $297,800 | | Scraped At | Timestamp of extraction | 2025-01-29T12:00:00.000Z | ⚙️ Setup Prerequisites n8n instance (self-hosted) Google account with Sheets access Scrape.do account with API token (Get 1000 free credits/month) Google Sheet Structure This workflow uses one Google Sheet with two tabs: Input Tab: "Sheet1" | Column | Type | Description | Example | |--------|------|-------------|---------| | URLs | URL | Zillow listing URL | https://www.zillow.com/homedetails/123... | Output Tab: "Results" | Column | Type | Description | Example | |--------|------|-------------|---------| | URL | URL | Original listing URL | https://www.zillow.com/homedetails/... | | Price | Text | Property price | $300,000 | | Address | Text | Street address | 8926 Silver City | | City | Text | City name | San Antonio | | State | Text | State code | TX | | Days on Zillow | Number | Days listed | 5 | | Zestimate | Text | Estimated value | $297,800 | | Scraped At | Timestamp | When scraped | 2025-01-29T12:00:00.000Z | 🛠 Step-by-Step Setup Import Workflow: Copy the JSON → n8n → Workflows → + Add → Import from JSON Configure Scrape.do API: Sign up at Scrape.do Dashboard Get your API token In HTTP Request node, replace YOUR_SCRAPE_DO_TOKEN with your actual token The workflow uses super=true for premium residential proxies (10 credits per request) Configure Google Sheets: Create a new Google Sheet Add two tabs: "Sheet1" (input) and "Results" (output) In Sheet1, add header "URLs" in cell A1 Add Zillow URLs starting from A2 Set up Google Sheets OAuth2 credentials in n8n Replace YOUR_SPREADSHEET_ID with your actual Google Sheet ID Replace YOUR_GOOGLE_SHEETS_CREDENTIAL_ID with your credential ID Run & Test: Add 1-2 test Zillow URLs in Sheet1 Click "Execute workflow" Check results in Results tab 🧰 How to Customize Add more fields**: Extend parsing logic in "Parse Zillow Data" node to capture additional data (bedrooms, bathrooms, square footage) Filtering**: Add conditions to skip certain properties or price ranges Rate Limiting**: Insert a Wait node between requests if processing many URLs Error Handling**: Add error branches to handle failed scrapes gracefully Scheduling**: Replace Manual Trigger with Schedule Trigger for automated daily/weekly runs 📊 Use Cases Investment Analysis**: Track property prices and zestimates over time Market Research**: Analyze listing trends in specific neighborhoods Portfolio Management**: Monitor properties for sale in target areas Competitive Analysis**: Compare similar properties across locations Lead Generation**: Build databases of properties matching specific criteria 📈 Performance & Limits Single Property**: ~5-10 seconds per URL Batch of 10**: 1-2 minutes typical Large Sets (50+)**: 5-10 minutes depending on Scrape.do credits API Calls**: 1 Scrape.do request per URL (10 credits with super=true) Reliability**: 95%+ success rate with premium proxies 🧩 Troubleshooting | Problem | Solution | |---------|----------| | API error 400 | Check your Scrape.do token and credits | | URL showing "undefined" | Verify Google Sheet column name is "URLs" (capital U) | | No data parsed | Check if Zillow changed their HTML structure | | Permission denied | Re-authenticate Google Sheets OAuth2 in n8n | | 50000 character error | Verify Parse Zillow Data code is extracting fields, not returning raw HTML | | Price shows HTML/CSS | Update price extraction regex in Parse Zillow Data node | 🤝 Support & Community Scrape.do Documentation Scrape.do Dashboard Scrape.do Zillow Scraping Guide n8n Forum n8n Docs 🎯 Final Notes This workflow provides a repeatable foundation for extracting Zillow property data with Scrape.do and saving to Google Sheets. You can extend it with: Historical tracking (append timestamps) Price change alerts (compare with previous scrapes) Multi-platform scraping (Redfin, Realtor.com) Integration with CRM or reporting dashboards Important: Scrape.do handles all anti-bot bypassing (PerimeterX, CAPTCHAs) automatically with rotating residential proxies, so you only pay for successful requests. Always use super=true parameter for Zillow to ensure high success rates. An n8n automation workflow template by Onur.

By Greypillar

How it works • Twilio webhook detects missed/unanswered calls automatically • Analyzes call context (time of day, business hours, weekend/weekday) • Checks CRM for existing customer data and purchase history (optional) • AI Chain (GPT-4o) generates personalized recovery messages for SMS and Email • Sends instant apology with booking link via SMS and/or Email • Logs all interactions to Airtable for tracking • Slack alerts sales team with customer priority and context • Waits 24 hours and checks if customer booked • Sends automatic follow-up SMS if no booking detected • Structured output parser ensures reliable JSON formatting Set up steps • Time to set up: 15-20 minutes • Add Twilio credential and configure phone number in both SMS nodes • Get Slack channel ID for sales team alerts • Create Airtable base with 10 columns (Caller_Number, Customer_Name, Call_Time, Priority, SMS_Sent, Email_Sent, Booking_Link, Status, Urgency_Score, Follow_Up_Date) • Replace booking URL with your Cal.com or Calendly link • Configure business email for SMTP sending • Update business phone and name in follow-up SMS • Add credentials: Twilio API, OpenAI (GPT-4o), Slack OAuth2, Airtable Token, SMTP Email • Replace placeholder IDs in Slack and Airtable nodes • Optional: Configure CRM API for existing customer lookup (or disable those nodes) What you'll need • Twilio - Phone number with SMS capability • OpenAI API - GPT-4o access for AI message generation • Slack - Standard workspace for sales alerts • Airtable - Free plan works for call tracking • Email SMTP - Gmail, SendGrid, or any SMTP provider • Cal.com or Calendly - Booking link for instant scheduling • CRM API (optional) - HubSpot, Salesforce, or custom CRM Who this is for Service businesses, agencies, and sales teams that lose revenue from missed calls. Perfect for businesses with high call volume that need instant personalized follow-up to recover lost opportunities. An n8n automation workflow template by Greypillar.

By Greypillar

How it works • Webhook receives lead form submissions from your website • AI Agent (GPT-4o) analyzes lead quality using intelligent scoring framework • Clearbit enriches company data automatically (employee count, industry, revenue) • Qualification score (0-100) determines routing: high-quality leads → HubSpot CRM + Slack alert, low-quality leads → Airtable for manual review • Structured output parser ensures reliable JSON formatting every time Set up steps • Time to set up: 15-20 minutes • Import the Clearbit sub-workflow first (separate workflow file included) • Create 7 custom properties in HubSpot (qualification_score, buying_intent, urgency_level, budget_indicator, ai_summary, pain_points, recommended_action) • Create Airtable base with 14 columns for low-quality lead tracking • Get Slack channel IDs for sales alerts and review requests • Add credentials: OpenAI (GPT-4o), Clearbit API, HubSpot OAuth2, Slack OAuth2, Airtable Token • Replace placeholder IDs in Slack and Airtable nodes • Configure the Clearbit Enrichment Tool node with your sub-workflow ID What you'll need • OpenAI API - OpenAI model access for AI qualification • Clearbit API - Free tier available for company enrichment • HubSpot - Free CRM account works • Slack - Standard workspace • Airtable - Free plan works • Website form - To send webhook data Who this is for Sales teams and agencies that want to automatically qualify inbound leads before they hit the CRM. Perfect for B2B companies with high lead volume that need intelligent routing. An n8n automation workflow template by Greypillar.

By Mark Hansen

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

By Yasser Sami

Customer Support AI Agent for Gmail This n8n template demonstrates how to build an AI-powered customer support workflow that automatically handles incoming Gmail messages, classifies them, finds answers from your knowledge base, and sends a personalized reply. Who’s it for SaaS founders or teams who want to automate customer support. Freelancers and solopreneurs who receive repetitive customer queries. Companies that want to reduce manual email triage and improve response times. How it works / What it does Trigger: A new email arrives in Gmail. Classification: The workflow uses a text classifier to decide whether the email is customer support-related or not. If not, it’s ignored. If yes, it proceeds. AI Agent: Queries a knowledge base (vector database with OpenAI embeddings). Retrieves the most relevant answer. Drafts a reply using AI (OpenAI or Google Gemini model). Post-processing: Labels the email in Gmail for organization. Sends a reply automatically. This ensures that your customers get timely, relevant responses without manual intervention. How to set up Import this template into your n8n account. Connect your Gmail account in the Gmail Trigger, Label, and Reply nodes. Connect your AI model provider (OpenAI or Google Gemini). Configure the knowledge base embeddings (upload your docs/FAQ into the vector database). Activate the workflow — and your AI customer support agent is live! Requirements n8n account. Gmail account (with API access enabled). OpenAI or Google Gemini account for LLM and embeddings. Knowledge base data (FAQ, documentation, or past tickets). Google Drive account for auto update your vector database(with API access enabled). How to customize the workflow Knowledge Base**: Replace or expand with your own company docs, FAQs, or past conversations. Classification Rules**: Train or adjust the classifier to handle more categories (e.g., Sales, Partnership, Technical Support). Reply Style**: Customize AI prompts for tone — professional, casual, or friendly. Labels**: Change Gmail labels to match your workflow (e.g., “Support,” “Sales,” “Priority”). Multi-language**: Add translation steps if your customers speak different languages. This template saves you hours of manual email triage and ensures your customers always get quick, accurate responses. An n8n automation workflow template by Yasser Sami.

By Facundo Cabrera

Automated Meeting Minutes from Video Recordings This workflow automatically transforms video recordings of meetings into structured, professional meeting minutes in Notion. It uses local AI models (Whisper for transcription and Ollama for summarization) to ensure privacy and cost efficiency, while uploading the original video to Google Drive for safekeeping. Ideal for creative teams, production reviews, or any scenario where visual context is as important as the spoken word. 🔄 How It Works Wait & Detect: The workflow monitors a local folder. When a new .mkv video file is added, it waits until the file has finished copying. Prepare Audio: The video is converted into a .wav audio file optimized for transcription (under 25 MB with high clarity). Transcribe Locally: The local Whisper model generates a timestamped text transcript. Generate Smart Minutes: The transcript is sent to a local Ollama LLM, which produces structured, summarized meeting notes. Store & Share: The original video is uploaded to Google Drive, a new page is created in Notion with the notes and a link to the video, and a completion notification is sent via Discord. ⏱️ Setup Steps Estimated Time**: 10–15 minutes (for technically experienced users). Prerequisites**: Install Python, FFmpeg, and required packages (openai-whisper, ffmpeg-python). Run Ollama locally with a compatible model (e.g., gpt-oss:20b, llama3, mistral). Configure n8n credentials for Google Drive, Notion, and Discord. Workflow Configuration**: Update the file paths for the helper scripts (wait-for-file.ps1, create_wav.py, transcribe_return.py) in the respective "Execute Command" nodes. Change the input folder path (G:\OBS\videos) in the "File" node to your own recording directory. Replace the Google Drive folder ID and Notion database/page ID in their respective nodes. > 💡 Note: Detailed instructions for each step, including error handling and variable setup, are documented in the Sticky Notes within the workflow itself. 📁 Helper Scripts Documentation wait-for-file.ps1 A PowerShell script that checks if a file is still being written to (i.e., locked by another process). It returns 0 if the file is free and 1 if it is still locked. Usage: .\wait-for-file.ps1 -FilePath "C:\path\to\your\file.mkv" create_wav.py A Python script that converts a video file into a .wav audio file. It automatically calculates the necessary audio bitrate to keep the output file under 25 MB—a common requirement for many transcription services. Usage: python create_wav.py "C:\path\to\your\file.mkv" transcribe_return.py A Python script that uses a local Whisper model to transcribe an audio file. It can auto-detect the language or use a language code specified in the filename (e.g., meeting.en.mkv for English, meeting.es.mkv for Spanish). The transcript is printed directly to stdout with timestamps, which is then captured by the n8n workflow. Usage: Auto-detect language python transcribe_return.py "C:\path\to\your\file.mkv" Force language via filename python transcribe_return.py "C:\path\to\your\file.es.mkv" `. An n8n automation workflow template by Facundo Cabrera.

By Abdullahi Osman

AI Email Dispatcher: Classify, Process, and Route Emails with Multiple Agents This n8n template automatically classifies incoming emails (Sales, Support, Internal, Finance, Promotions) and routes them to a dedicated OpenAI LLM Agent for processing. Depending on the category, the agent will then: Internal/Customer Support:** Draft a reply and send it. Sales/Finance/Promotions:** Generate a summary, notification, or draft reply for a human to review. This is the ultimate workflow for managing a high volume of emails, ensuring every message gets a fast, appropriate, and structured AI-powered response or initial analysis. How it works The Gmail Trigger node monitors your inbox for unread emails. The Text Classifier node uses AI to read the email body and subject to categorize it as Internal, Customer Support, Sales, Promotions, or Admin/Finance. The workflow then uses a Split In Batches node and multiple If nodes to send the email data to a specific, specialized OpenAI Agent (LLM node) based on the classification. Each AI Agent has a custom system prompt (e.g., "Customer Support Agent," "Promotions Analyst") to ensure it processes the email with the right rules, tone, and output format. Finally, the workflow either automatically replies via Gmail (for Internal and Support) or creates a draft/summary and sends a notification (for Sales, Finance, and Promotions) for human review. Set up steps Setting up the accounts and nodes should take about 10–15 minutes. Gmail Account: You'll need to set up two Gmail credentials for the workflow: One for the Gmail Trigger to watch for new unread emails. A second one for the Gmail action nodes to label, draft, and reply to messages. OpenAI Account: Connect your OpenAI API Key to the five different LLM Agent nodes. Telegram/Slack: Set up your Telegram or Slack credentials to receive the 'New Sales Opportunity' and 'New Finance' notifications. Labels in Gmail: Before activating the workflow, make sure you have created the necessary labels in your Gmail account for the classifier (Internal, Customer Support, Promotions, Admin/Finance, Sales Opportunity). Review Agent Prompts: The instructions and logic for each AI Agent are in the system messages. You might want to review and customize these prompts to match your specific business rules and tone. Requirements Gmail** Account OpenAI** Account (or another LLM provider for the agents) Telegram** (or Slack/other notification tool of your choice) Customising this workflow You can easily adapt this template to suit your needs! New Categories:* Modify the *Text Classifier** node to add or remove categories (e.g., "Job Applications," "Partnerships"). You would then add a new LLM Agent and routing logic for the new category. Different LLMs:* You can swap the OpenAI nodes for any other LLM service supported by n8n, such as *Gemini* or *Anthropic Claude**, by simply changing the node type or model ID. More Actions:* Instead of just sending a notification to Telegram, you could modify the logic to create a task in *ClickUp, a lead in **Salesforce, or an entry in a Google Sheet when a "Sales Opportunity" email is identified. 📬✨. An n8n automation workflow template by Abdullahi Osman.

By Florent

n8n Restore workflows & credentials from Disk - Self-Hosted Solution This n8n template provides a safe and intelligent restore solution for self-hosted n8n instances, allowing you to restore workflows and credentials from disk backups. Perfect for disaster recovery or migrating between environments, this workflow automatically identifies your most recent backup and provides a manual restore capability that intelligently excludes the current workflow to prevent conflicts. Works seamlessly with date-organized backup folders. Good to know This workflow uses n8n's native import commands (n8n import:workflow and n8n import:credentials) Works with date-formatted backup folders (YYYY-MM-DD) for easy version identification The restore process intelligently excludes the current workflow to prevent overwriting itself Requires proper Docker volume configuration and file system permissions All operations are performed server-side with no external dependencies Compatible with backups created by n8n's export commands How it works Restore Process (Manual) Manual trigger with configurable pinned data options (credentials: true/false, workflows: true/false) The Init node sets up all necessary paths, timestamps, and configuration variables using your environment settings The workflow scans your backup folder and automatically identifies the most recent backup If restoring credentials: Direct import from the latest backup folder using n8n's import command Credentials are imported with their encrypted format intact If restoring workflows: Scans the backup folder for all workflow JSON files Creates a temporary folder with all workflows from the backup Intelligently excludes the current restore workflow to prevent conflicts Imports all other workflows using n8n's import command Cleans up temporary files automatically Optional email notifications provide detailed restore summaries with command outputs How to use Prerequisites Existing n8n backups in date-organized folder structure (format: /backup-folder/YYYY-MM-DD/) Workflow backups as JSON files in the date folder Credentials backups in subfolder: /backup-folder/YYYY-MM-DD/n8n-credentials/ For new environments: N8N_ENCRYPTION_KEY from source environment (see dedicated section below) Initial Setup Configure your environment variables: N8N_ADMIN_EMAIL: Your email for notifications (optional) N8N_BACKUP_FOLDER: Location where your backups are stored (e.g., /files/n8n-backups) N8N_PROJECTS_DIR: Projects root directory GENERIC_TIMEZONE: Your local timezone N8N_ENCRYPTION_KEY: Required if restoring credentials to a new environment (see dedicated section below) Update the Init node: (Optional) Configure your email here: const N8N_ADMIN_EMAIL = $env.N8N_ADMIN_EMAIL || 'youremail@world.com'; Set PROJECT_FOLDER_NAME to "Workflow-backups" (or your preferred name) Set credentials to "n8n-credentials" (or your backup credentials folder name) Verify BACKUP_FOLDER path matches where your backups are stored Ensure your Docker setup has: Mounted volume containing backups (e.g., /local-files:/files) Access to n8n's CLI import commands Proper file system permissions (read access to backup directories) Performing a Restore Open the workflow and locate the "Start Restore" manual trigger node Edit the pinned data to choose what to restore: credentials: true - Restore credentials workflows: true - Restore workflows Set both to true to restore everything Click "Execute workflow" on the "Start Restore" node to execute the restore The workflow will automatically find the most recent backup (latest date) Check the console logs or optional email for detailed restore summary Important Notes The workflow automatically excludes itself during restore to prevent conflicts Credentials are restored with their encryption intact. If restoring to a new environment, you must configure the N8N_ENCRYPTION_KEY from the source environment (see dedicated section below) Existing workflows/credentials with the same names will be overwritten Test in a non-production environment first if unsure ⚠ Critical: N8N_ENCRYPTION_KEY Configuration Why this is critical: n8n generates an encryption key automatically on first launch and saves it in the ~/.n8n/config file. However, if this file is lost (for example, due to missing Docker volume persistence), n8n will generate a NEW key, making all previously encrypted credentials inaccessible. When you need to configure N8N_ENCRYPTION_KEY: Restoring to a new n8n instance When your data directory is not persisted between container recreations Migrating from one server to another As a best practice to ensure key persistence across updates How credentials encryption works: Credentials are encrypted with a specific key unique to each n8n instance This key is auto-generated on first launch and stored in /home/node/.n8n/config When you backup credentials, they remain encrypted but the key is NOT included If the key file is lost or a new key is generated, restored credentials cannot be decrypted Setting N8N_ENCRYPTION_KEY explicitly ensures the key remains consistent Solution: Retrieve and configure the encryption key Step 1: Get the key from your source environment Check if the key is defined in environment variables docker-compose exec n8n printenv N8N_ENCRYPTION_KEY If this command returns nothing, the key is auto-generated and stored in n8n's data volume: Enter the container docker-compose exec n8n sh Check configuration file cat /home/node/.n8n/config Exit container exit Step 2: Configure the key in your target environment Option A: Using .env file (recommended for security) Add to your .env file N8N_ENCRYPTION_KEY=your_retrieved_key_here Then reference it in docker-compose.yml: services: n8n: environment: N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY} Option B: Directly in docker-compose.yml (less secure) services: n8n: environment: N8N_ENCRYPTION_KEY=your_retrieved_key_here Step 3: Restart n8n docker-compose restart n8n Step 4: Now restore your credentials Only after configuring the encryption key, run the restore workflow with credentials: true. Best practice for future backups: Always save your N8N_ENCRYPTION_KEY in a secure location alongside your backups Consider storing it in a password manager or secure vault Document it in your disaster recovery procedures Requirements Existing Backups Date-organized backup folders (YYYY-MM-DD format) Backup files created by n8n's export commands or compatible format Environment Self-hosted n8n instance (Docker recommended) Docker volumes mounted with access to backup location Optional: SMTP server configured for email notifications Credentials (Optional) SMTP credentials for email notifications (if using email nodes) Technical Notes Smart Workflow Exclusion During workflow restore, the current workflow's name is cleaned and matched against backup files This prevents the restore workflow from overwriting itself The exclusion logic handles special characters and spaces in workflow names A temporary folder is created with all workflows except the current one Timezone Handling All timestamps use UTC for technical operations Display times use local timezone for user-friendly readability Backup folder scanning works with YYYY-MM-DD format regardless of timezone Security Credentials are imported in n8n's encrypted format (encryption preserved) Ensure backup directories have appropriate read permissions Consider access controls for who can trigger restore operations No sensitive data is logged in console output Troubleshooting Common Issues No backups found: Verify the N8N_BACKUP_FOLDER path is correct and contains date-formatted folders Permission errors: Ensure Docker user has read access to backup directories Path not found: Verify all volume mounts in docker-compose.yml match your backup location Import fails: Check that backup files are in valid n8n export format Workflow conflicts: The workflow automatically excludes itself, but ensure backup files are properly named Credentials not restored: Verify the backup contains a n8n-credentials folder with credential files Credentials decrypt error: Ensure N8N_ENCRYPTION_KEY matches the source environment Version Compatibility Tested with n8n version 1.113.3 Compatible with Docker-based n8n installations Requires n8n CLI access (available in official Docker images) This workflow is designed for self-hosted server backup restoration. For FTP/SFTP remote backups, see the companion workflow "n8n Restore from FTP". Works best with backups from: "Automated n8n Workflows & Credentials Backup to Local/Server Disk & FTP". An n8n automation workflow template by Florent.

By Jitesh Dugar

Customer Onboarding Email Verification Automated email verification and welcome email workflow that validates new user signups, prevents fake emails, and creates a seamless onboarding experience with real-time team notifications. Features ✅ Real-time email validation with VerifiEmail API ✅ Automatic data sanitization (lowercase, trim whitespace) ✅ Smart typo detection and correction suggestions ✅ Disposable email domain blocking ✅ Professional HTML welcome emails with responsive design ✅ Automatic duplicate prevention in Google Sheets logging ✅ Real-time Slack notifications for sales/marketing teams ✅ MX record and SMTP deliverability checks What You Need Required Accounts/APIs: VerifiEmail API - For email validation (verifi.email) Gmail account (or SMTP server) - For sending welcome emails Google Sheets - For logging verified users Slack workspace - For team notifications (optional but recommended) Setup Instructions Create Google Sheet Create new spreadsheet named "Verified Users" Add headers: Name | Email | Status | Verified At | Original Email | Validation Score Connect Credentials Add VerifiEmail API key in n8n credentials Connect Gmail via OAuth2 (enable 2FA, generate app password if needed) Connect Google Sheets via OAuth2 Connect Slack workspace via OAuth2 Customize Email Template Open "Personalize Welcome Email" node Replace "Your Company" with your brand name (appears 3 times) Update CTA URLs: yourapp.com/dashboard → Your actual dashboard URL yourapp.com/getting-started → Your docs/guide URL yourapp.com/support → Your support page URL Modify colors: Purple gradient #667eea to #764ba2 (line 37) Configure Slack Channel Create #new-signup channel in Slack (or use existing) Update channel in "Team Notification" node Test Workflow Activate workflow Copy webhook URL from Webhook node Test with: curl -X POST [webhook-url] -H "Content-Type: application/json" -d '{"name":"Test User","email":"test@gmail.com"}' Integrate with Your Signup Form Point form submission to webhook URL Ensure payload includes name and email fields Input Format Send POST request to webhook with this JSON: { "name": "John Doe", "email": "johndoe@gmail.com" } The workflow handles various input formats (nested in body field, query params, etc.) and sanitizes automatically. Output After execution, you'll get: Email validated via VerifiEmail API with deliverability score Welcome email sent to user with personalized greeting and CTAs User logged to Google Sheets with timestamp and validation details Slack notification sent to team with user details and status Invalid emails blocked with typo correction suggestions prepared For Valid Emails (~85-90%): Professional HTML welcome email delivered Entry added to "Verified Users" sheet Real-time Slack alert to #new-signup channel For Invalid Emails (~10-15%): Workflow stops with error message No email sent (prevents bounces) Typo suggestion prepared (e.g., gmial.com → gmail.com) Customization Change Email Design: Edit the "Personalize Welcome Email" node HTML: Colors**: Change gradient in line 37: background: linear-gradient(135deg, #667eea 0%, #764ba2 100%) Logo**: Add `` tag in header section Buttons**: Modify CTA text and links in lines 45-65 Footer**: Update copyright year and company name Modify Validation Rules: In "Prepare Correction Email" node, add more typo patterns: const commonTypos = { 'gmial': 'gmail', 'gmai': 'gmail', // Add your custom patterns: 'yourdomain': 'yourcorrectdomain' } Enable Correction Email Sending: Replace "Stop and Error" node with Gmail "Send Email" node: Connect from "Prepare Correction Email" Use {{ $json.email }} as recipient Use {{ $json.emailBody }} as message User receives helpful correction suggestion instead of silent failure Add More Notification Channels: After "Log Valid Users" node, add: Discord webhook for team notifications Microsoft Teams connector Email to sales@ or support@ Custom webhook to your CRM Log Invalid Attempts: Add Google Sheets node after "Prepare Correction Email": Create "Invalid Attempts" tab in same spreadsheet Log: Name, Email, Reason, Suggestion, Timestamp Analyze patterns weekly for form improvements Troubleshooting "undefined" error in Data Sanitization: Check webhook payload structure Verify name and email fields are present Test with the debug code provided in sticky notes All emails marked as invalid: Verify VerifiEmail API key is active Test API directly at verifi.email dashboard Welcome emails not sending: Confirm Gmail OAuth2 is connected (check for expired tokens) Verify sending limits not exceeded Check spam folder if testing with personal email Review Gmail "Sent" folder for delivery confirmation No Slack notifications: Verify OAuth2 connection is active Check bot has permission to post in #new-signup channel Confirm channel ID is correct Test Slack credentials in n8n Duplicate entries in Google Sheets: Verify "Email" is set as matching column Confirm operation is "Append or Update" not just "Append" Check Sheet1 has the exact column names expected High validation failure rate: Review invalid emails in execution logs Check for form submission issues (bots, testing) Verify VerifiEmail API is not blocking legitimate domains Performance Optimization For high-volume signups (>100/day): Switch Slack notifications to hourly digest Implement rate limiting on webhook Consider caching frequent domain validations Use Google Workspace for higher email sending limits Maintenance Weekly: Check VerifiEmail API usage and quota Review Slack notifications for anomalies Scan Google Sheets for data quality Test with sample signup Monthly: Archive old Google Sheets data (>90 days) Review invalid email patterns Update email template if needed Audit credential security Support For issues or questions, visit the n8n community forum. An n8n automation workflow template by Jitesh Dugar.

By Mano

📰 What This Workflow Does This intelligent news monitoring system automatically: • RSS Feed Aggregation: Pulls the latest headlines from Google News RSS feeds and Hacker News • AI Content Filtering: Identifies and prioritizes AI-related news from the past 24 hours • Smart Summarization: Uses OpenAI to create concise, informative summaries of top stories • Telegram Delivery: Sends formatted news digests directly to your Telegram channel • Scheduled Execution: Runs automatically every morning at 8:00 AM (configurable) 🎯 Key Features ✅ Multi-Source News: Combines Google News and Hacker News for comprehensive coverage ✅ AI-Powered Filtering: Automatically identifies relevant AI and technology news ✅ Intelligent Summarization: OpenAI generates clear, concise summaries with key insights ✅ Telegram Integration: Instant delivery to your preferred chat or channel ✅ Daily Automation: Scheduled to run every morning for fresh news updates ✅ Customizable Timing: Easy to adjust schedule for different time zones 🔧 How It Works Scheduled Trigger: Workflow activates daily at 8:00 AM (or your preferred time) RSS Feed Reading: Fetches latest articles from Google News and Hacker News feeds Content Filtering: Identifies AI-related stories from the past 24 hours AI Summarization: OpenAI processes and summarizes the most important stories Telegram Delivery: Sends formatted news digest to your Telegram channel 📋 Setup Requirements • OpenAI API Key: For AI-powered news summarization • Telegram Bot: Create via @BotFather and get bot token + chat ID • RSS Feed Access: Google News and Hacker News RSS feeds (public) ⚙️ Configuration Steps Set Up Telegram Bot: Message @BotFather on Telegram Create new bot with /newbot command Save bot token and chat ID Configure OpenAI: Add OpenAI API credentials in n8n Ensure access to GPT models for summarization Update RSS Feeds: Verify Google News RSS feed URLs Confirm Hacker News feed accessibility Schedule Timing: Adjust Schedule Trigger for your time zone Default: 8:00 AM daily (modify as needed) Test & Deploy: Run test execution to verify all connections Activate workflow for daily automation 🎨 Customization Options Time Zone Adjustment: Modify Schedule Trigger for different regions News Sources: Add additional RSS feeds for broader coverage Filtering Criteria: Adjust AI prompts to focus on specific topics Summary Length: Customize OpenAI prompts for different detail levels Delivery Format: Modify Telegram message formatting and structure 💡 Use Cases • AI Professionals: Stay updated on latest AI developments and industry news • Tech Teams: Monitor technology trends and competitor announcements • Researchers: Track academic and industry research developments • Content Creators: Source material for AI-focused content and newsletters • Business Leaders: Stay informed about AI market trends and opportunities. An n8n automation workflow template by Mano.

By Florent

Restore workflows & credentials from FTP - Remote Backup Solution This n8n template provides a safe and intelligent restore solution for self-hosted n8n instances, allowing you to restore workflows and credentials from FTP remote backups. Perfect for disaster recovery or migrating between environments, this workflow automatically identifies your most recent FTP backup and provides a manual restore capability that intelligently excludes the current workflow to prevent conflicts. Works seamlessly with date-organized backup folders stored on any FTP/SFTP server. Good to know This workflow uses n8n's native import commands (n8n import:workflow and n8n import:credentials) Works with date-formatted backup folders (YYYY-MM-DD) stored on FTP servers The restore process intelligently excludes the current workflow to prevent overwriting itself Requires FTP/SFTP server access and proper Docker volume configuration All downloaded files are temporarily stored server-side before import Compatible with backups created by n8n's export commands and uploaded to FTP Supports selective restoration: restore only credentials, only workflows, or both How it works Restore Process (Manual) Manual trigger with configurable pinned data options (credentials: true/false, worflows: true/false) The Init node sets up all necessary paths, timestamps, and configuration variables using your environment settings The workflow connects to your FTP server and scans for available backup dates Automatically identifies the most recent backup folder (latest YYYY-MM-DD date) Creates temporary restore folders on your local server for downloaded files If restoring credentials: Lists all credential files from FTP backup folder Downloads credential files to temporary local folder Writes files to disk using "Read/Write Files from Disk" node Direct import using n8n's import command Credentials are imported with their encrypted format intact If restoring workflows: Lists all workflow JSON files from FTP backup folder Downloads workflow files to temporary local folder Filters out the credentials subfolder to prevent importing it as a workflow Writes workflow files to disk Intelligently excludes the current restore workflow to prevent conflicts Imports all other workflows using n8n's import command Optional email notifications provide detailed restore summaries with command outputs Temporary files remain on server for verification (manual cleanup recommended) How to use Prerequisites Existing n8n backups on FTP server in date-organized folder structure (format: /ftp-backup-folder/YYYY-MM-DD/) Workflow backups as JSON files in the date folder Credentials backups in subfolder: /ftp-backup-folder/YYYY-MM-DD/n8n-credentials/ FTP/SFTP access credentials configured in n8n For new environments: N8N_ENCRYPTION_KEY from source environment (see dedicated section below) Initial Setup Configure your environment variables: N8N_ADMIN_EMAIL: Your email for notifications (optional) FTP_BACKUP_FOLDER: FTP path where backups are stored (e.g., /n8n-backups) N8N_PROJECTS_DIR: Projects root directory (e.g., /files/n8n-projects-data) GENERIC_TIMEZONE: Your local timezone (e.g., Europe/Paris) N8N_ENCRYPTION_KEY: Required if restoring credentials to a new environment (see dedicated section below) Create your FTP credential in n8n: Add a new FTP/SFTP credential Configure host, port, username, and password/key Test the connection Update the Init node: (Optional) Configure your email here: const N8N_ADMIN_EMAIL = $env.N8N_ADMIN_EMAIL || 'youremail@world.com'; Set PROJECT_FOLDER_NAME to "Workflow-backups" (or your preferred name) Set FTP_BACKUP_FOLDER to match your FTP backup path (default: /n8n-backups) Set credentials to "n8n-credentials" (or your backup credentials folder name) Set FTPName to a descriptive name for your FTP server (used in notifications) Configure FTP credentials in nodes: Update the FTP credential in "List Credentials Folders" node Verify all FTP nodes use the same credential Test connection by executing "List Credentials Folders" node Optional: Configure SMTP for email notifications: Add SMTP credential in n8n Activate "SUCCESS email Credentials" and "SUCCESS email Workflows" nodes Or remove email nodes if not needed Performing a Restore Open the workflow and locate the "Start Restore" manual trigger node Edit the pinned data to choose what to restore: { "credentials": true, "worflows": true } credentials: true - Restore credentials from FTP worflows: true - Restore workflows from FTP (note: typo preserved from original) Set both to true to restore everything Update the node's notes to reflect your choice (for documentation) Click "Execute workflow" on the "Start Restore" node The workflow will: Connect to FTP and find the most recent backup Download selected files to temporary local folders Import credentials and/or workflows Send success email with detailed operation logs Check the console logs or email for detailed restore summary Important Notes The workflow automatically excludes itself during restore to prevent conflicts Credentials are restored with their encryption intact. If restoring to a new environment, you must configure the N8N_ENCRYPTION_KEY from the source environment (see dedicated section below) Existing workflows/credentials with the same names will be overwritten Temporary folders are created with date prefix (e.g., 2025-01-15-restore-credentials) Test in a non-production environment first if unsure Critical: N8N_ENCRYPTION_KEY Configuration Why this is critical: n8n generates an encryption key automatically on first launch and saves it in the ~/.n8n/config file. However, if this file is lost (for example, due to missing Docker volume persistence), n8n will generate a NEW key, making all previously encrypted credentials inaccessible. When you need to configure N8N_ENCRYPTION_KEY: Restoring to a new n8n instance When your data directory is not persisted between container recreations Migrating from one server to another As a best practice to ensure key persistence across updates How credentials encryption works: Credentials are encrypted with a specific key unique to each n8n instance This key is auto-generated on first launch and stored in /home/node/.n8n/config When you backup credentials, they remain encrypted but the key is NOT included If the key file is lost or a new key is generated, restored credentials cannot be decrypted Setting N8N_ENCRYPTION_KEY explicitly ensures the key remains consistent Solution: Retrieve and configure the encryption key Step 1: Get the key from your source environment Check if the key is defined in environment variables docker-compose exec n8n printenv N8N_ENCRYPTION_KEY If this command returns nothing, the key is auto-generated and stored in n8n's data volume: Enter the container docker-compose exec n8n sh Check configuration file cat /home/node/.n8n/config Exit container exit Step 2: Configure the key in your target environment Option A: Using .env file (recommended for security) Add to your .env file N8N_ENCRYPTION_KEY=your_retrieved_key_here Then reference it in docker-compose.yml: services: n8n: environment: N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY} Option B: Directly in docker-compose.yml (less secure) services: n8n: environment: N8N_ENCRYPTION_KEY=your_retrieved_key_here Step 3: Restart n8n docker-compose restart n8n Step 4: Now restore your credentials Only after configuring the encryption key, run the restore workflow with credentials: true. Best practice for future backups: Always save your N8N_ENCRYPTION_KEY in a secure location alongside your backups Consider storing it in a password manager or secure vault Document it in your disaster recovery procedures Requirements FTP Server FTP or SFTP server with existing n8n backups Read access to backup folder structure Network connectivity from n8n instance to FTP server Existing Backups on FTP Date-organized backup folders (YYYY-MM-DD format) Backup files created by n8n's export commands or compatible format Credentials in subfolder structure: YYYY-MM-DD/n8n-credentials/ Environment Self-hosted n8n instance (Docker recommended) Docker volumes mounted with write access to project folder Access to n8n CLI commands (n8n import:credentials and n8n import:workflow) Proper file system permissions for temporary folder creation Credentials FTP/SFTP credential configured in n8n Optional: SMTP credentials for email notifications Technical Notes FTP Connection and Download Process Uses n8n's built-in FTP node for all remote operations Supports both FTP and SFTP protocols Downloads files as binary data before writing to disk Temporary local storage required for import process Smart Workflow Exclusion During workflow restore, the current workflow's name is cleaned and matched against backup files This prevents the restore workflow from overwriting itself The exclusion logic handles special characters and spaces in workflow names A bash command removes the current workflow from the temporary restore folder before import Credentials Subfolder Filtering The "Filter out Credentials sub-folder" node checks for binary data presence Only items with binary data (actual files) proceed to disk write Prevents the credentials subfolder from being imported as a workflow Timezone Handling All timestamps use UTC for technical operations Display times use local timezone for user-friendly readability FTP backup folder scanning works with YYYY-MM-DD format regardless of timezone Security FTP connections should use SFTP or FTPS for encrypted transmission Credentials are imported in n8n's encrypted format (encryption preserved) Temporary files stored in project-specific folders Consider access controls for who can trigger restore operations No sensitive credential data is logged in console output Troubleshooting Common Issues FTP connection fails: Verify FTP credentials are correctly configured and server is accessible No backups found: Ensure the FTP_BACKUP_FOLDER path is correct and contains date-formatted folders (YYYY-MM-DD) Permission errors: Ensure Docker user has write access to N8N_PROJECTS_DIR for temporary folders Path not found: Verify all volume mounts in docker-compose.yml match your project folder location Import fails: Check that backup files are in valid n8n export format Download errors: Verify FTP path structure matches expected format (date folder / credentials subfolder / files) Workflow conflicts: The workflow automatically excludes itself, but ensure backup files are properly named Credentials not restored: Verify the FTP backup contains a n8n-credentials subfolder with credential files Credentials decrypt error: Ensure N8N_ENCRYPTION_KEY matches the source environment Error Handling "Find Last Backup" node has error output configured to catch FTP listing issues "Download Workflow Files" node continues on error to handle presence of credentials subfolder All critical nodes log detailed error information to console Email notifications include stdout and stderr from import commands Version Compatibility Tested with n8n version 1.113.3 Compatible with Docker-based n8n installations Requires n8n CLI access (available in official Docker images) Works with any FTP/SFTP server (Synology NAS, dedicated FTP servers, cloud FTP services) This workflow is designed for FTP/SFTP remote backup restoration. For local disk backups, see the companion workflow "n8n Restore from Disk". Works best with backups from: "Automated n8n Workflows & Credentials Backup to Local/Server Disk & FTP". An n8n automation workflow template by Florent.

By Keith Uy

Quick overview This is a starting point for building a Slack AI agent. The base handles four input types: voice, pictures, video, and text, through the AI model of your choice. From here you connect tools to expand what the agent can do inside your n8n workflows. How it works Input: a Slack message that mentions the bot in a channel. A Switch node sorts the message by type: Voice message Picture message Video message Text message It currently uses OpenAI and Gemini to analyze voice, photos, and video, but you can swap in other models. The model reads the message, generates a response from the system prompt, and posts it back to Slack. Setup Create the Slack bot and token. At https://api.slack.com/apps/ create an app from scratch. Add these Bot Token Scopes: app_mentions:read, channels:history, channels:join, channels:read, chat:write, files:read, links:read, links:write. Enable Event Subscriptions with your n8n webhook URL, install the bot to your workspace, and add it to the channel. Add the Slack credential in n8n. Open the Slack trigger node, create a credential, and paste the Bot User OAuth token. Add the bot token to the HTTP Request nodes. On the HTTP Request nodes, add the token under Header Parameters as Bearer [your bot token]. Configure the Slack nodes. Point all Slack nodes at the correct workspace and channel. Add the LLM credentials. Add your OpenAI and Gemini keys (and any other model you prefer) to the LLM nodes, then pick your model, and make sure each account has credits. Guides: OpenAI (voice) → https://winflowai.com/blog/get-openai-api-key/ and Google Gemini (images and video) → https://winflowai.com/blog/get-gemini-api-key/ Customization Adjust the system prompts to shape the agent's behavior Add tools (calendars, databases, and more) to expand what it can do. An n8n automation workflow template by Keith Uy.

By Dele Tosh @ Protomated

🚀 Automate your social media presence! This workflow duo automatically curates content from your Wallabag RSS feeds, generates platform-specific posts using AI, and publishes them—complete with AI-generated images. ⚙️ Setup & Configuration Required Credentials & Services: To run this workflow, you will need to set up the following credentials in n8n: Wallabag RSS Feeds:** This workflow uses Wallabag as your content curation service. Wallabag is the most cost-effective option—easy to self-host or use as a paid service. You'll need to generate access tokens for RSS feed access. Airtable API Key:** To create and update records in your "Content Store" database. LLM Provider API Key:* To power the social media content generation. The demo uses *Groq (llama-3.3-70b-versatile)**, but this can be replaced with any preferred LLM (OpenAI, Anthropic, etc.). GetLate API Key:** To authenticate and post to your social media platforms. Imgbb API Key:** To host the AI-generated images. An Image Generation Service API Key:* For creating images from prompts. The demo uses *Hugging Face (stable-diffusion-xl-base-1.0)**, but this can be swapped for any other service (Fal.ai, Stability AI, etc.). Key Setup Requirement: Define Your Tagging Convention Before running this workflow, establish a consistent tagging system in Wallabag where each tag corresponds to a specific social media platform. For example: #to-share-linkedin for LinkedIn content #to-share-bluesky for Bluesky content #to-share-instagram for Instagram content Adding More Feeds & Platforms: New Feeds:** Simply duplicate the example sub-workflows and update the RSS feed URL and target platform information for each new tag/platform combination. New Platforms:** To add support for additional social platforms, duplicate one of the existing platform sub-workflows (LinkedIn or Bluesky) and update the platform-specific parameters, prompts, and GetLate API settings for your new platform. Airtable Database Schema: "RSS Feed - Content Store" The workflow uses an Airtable base with the following fields to track content from ingestion to publication: id (Primary Field): Formula, for unique record ID (RECORD_ID()) audience_targeted: Long text author: Long text character_count: Number content_markdown: Long text cta_used: Long text feed_id: Single line text goal_applied: Long text image_filename: Singe line text image_id: Single line text image_link: URL image_prompt: Long text is_posted: Number, default is 0 platform: Single line text post_text: Long text suggested_hashtags: Long text title: Long text tone_applied: Long text article_url: URL Customizable User Inputs: This workflow is built for flexibility. Key inputs you can customize include: Wallabag RSS Feed URL & Platform Tag:** The specific feed and platform-specific tag (e.g., #to-share-linkedin) to monitor in Workflow #1. Target Social Platform:** Defined per feed in the "Edit Field" node. Content Generation Schedule:** The frequency for auto-posting in the Schedule Trigger. Brand Voice & LLM Parameters:** The tone, style, and specific instructions for the AI in the "Set Custom SMCG Prompt" node. Platform-Specific Prompts:** The template used to generate posts for each social network (Instagram, LinkedIn, etc.). Posting Behavior & Image Generation:* Configured within the *SMCG (Social Media Content Generation) node**. This is where you set the posting mode (immediate vs. draft) and define a boolean for each platform to enable or disable AI-generated images for its posts. 📥 Workflow 1: RSS Aggregator & Content Store RSS Trigger** → Pulls tagged articles from Wallabag feeds using platform-specific tags Platform Assignment** → Sets target social platform based on tag Content Conversion** → HTML to Markdown formatting Airtable Storage** → Saves articles to content database 🌟 Adding New RSS Feeds: To monitor additional Wallabag feeds for different content sources, simply duplicate the existing RSS feed sub-workflow and update the RSS URL with your new Wallabag access token and platform-specific tag. Each feed can target a different social platform or content category. 🔄 Workflow 2: AI Content Generator & Publisher Schedule Trigger** → Runs on your preferred frequency Content Selection** → Pulls unpublished articles from Airtable AI Configuration** → Sets brand voice, posting behavior, and image generation preferences Platform Routing** → Directs to appropriate social platform workflow AI Content Generation** → Creates posts and image prompts using LLM Image Generation** → Creates & hosts images when enabled Social Publishing** → Posts to platforms via GetLate API Database Update** → Marks content as published in Airtable 🌟 Adding New Platform Support: To extend this workflow to additional social platforms, simply duplicate one of the existing platform sub-workflows and update the platform-specific parameters, LLM prompts, and GetLate API configuration for your target platform. An n8n automation workflow template by Dele Tosh @ Protomated.

By Jitesh Dugar

Meeting Minutes & Action Item Tracker Fully automated meeting documentation workflow that uses AI to transform raw transcripts into professional PDFs and actionable tasks. Features AI-powered summary generation (GPT-4) Automatic action item extraction with assignees, deadlines, and priorities Professional PDF generation with custom styling Multi-channel distribution (Email, Slack, Google Drive) Task creation in Google Tasks Personalized notifications to each assignee Deadline tracking and urgency detection Setup Instructions REQUIRED CREDENTIALS: OpenAI API - Get from Gmail OAuth2 - Connect your Google account Google Drive OAuth2 - Same Google account Google Tasks OAuth2 - Same Google account Slack OAuth2 - Connect your workspace htmlcsstopdf API - Get from CONFIGURATION STEPS: WEBHOOK: Note your webhook URL after activation EMAIL NODES: "Email All Participants": Uses participants array from input "Send Individual Task Emails": Change @yourcompany.com to your domain GOOGLE DRIVE: Select folder where PDFs should be stored Recommended: Create "Meeting Minutes" folder SLACK: Select channel for team notifications Recommended: Create #meeting-notes channel GOOGLE TASKS: Select task list where tasks should be created Default list works fine TESTING: Use the webhook URL with sample meeting data Check execution log for any errors Verify PDF in Google Drive Check emails were sent Confirm tasks created in Google Tasks Example Input Format POST : Headers: Content-Type: application/json Body: { "title": "Weekly Team Standup", "date": "2025-09-29", "participants": [ "john@company.com", "sarah@company.com", "joe@company.com" ], "duration": "30 minutes", "transcript": "John started the meeting by discussing the progress on the API development. Sarah mentioned that she's working on the dashboard and needs to prepare mockups by Thursday. The team agreed that Sarah will review the API documentation before the client demo on Friday. Akshita confirmed she finished the database schema redesign and needs to schedule a meeting with DevOps team by next Monday to discuss production deployment." } This will generate: Professional PDF with summary and action items Emails to all participants Individual task emails to John, Sarah, and Joe Tasks in Google Tasks Slack notification Output After execution, you'll get: Professional PDF stored in Google Drive Email sent to all participants with meeting overview Individual emails to each assignee with their tasks Slack notification with summary and download link Tasks created in Google Tasks with deadlines CUSTOMIZATION: Modify PDF styling in "Generate PDF Document" node Adjust email templates in Gmail nodes Change AI prompts in OpenAI nodes for different output Modify priority/deadline logic in "Parse and Enrich Data" Troubleshooting Workflow stops at validation: Ensure transcript has >50 words Check that webhook payload is correctly formatted No PDF generated: Verify htmlcsstopdf API credentials Check API usage limits Tasks not created: Verify deadline format is YYYY-MM-DD Check Google Tasks API connection Emails not sending: Confirm Gmail OAuth2 is connected Check that email addresses are valid Support For issues or questions, visit the n8n community forum. License MIT License - Feel free to modify and share!. An n8n automation workflow template by Jitesh Dugar.

By Rahul Joshi

Description Automate your GoHighLevel (GHL) pipeline tracking and deal management process. This workflow fetches all opportunities, calculates the time spent in each stage, logs historical pipeline data in Google Sheets, identifies deals stuck for more than 7 days, generates HTML and text reports, and sends alerts via Gmail and Slack. It also produces a weekly pipeline velocity report for sales leadership, helping teams quickly spot bottlenecks and optimize pipeline performance. 🚀📊📈📧💬 What This Template Does Triggers automatically every Monday at 8 AM ⏰ Fetches all opportunities and stage history from GoHighLevel pipelines 🔍 Calculates days spent in each stage, including historical and current stages 📅 Logs historical pipeline data in Google Sheets for trend tracking 📊 Filters deals stuck in a stage for more than 7 days ⚠️ Generates detailed HTML and text stuck deal alert emails ✉️ Sends Slack notifications for stuck deals 💬 Generates weekly pipeline velocity report showing bottleneck and fastest stages 📈 Sends weekly report via Gmail to sales leadership 🏆 Sends error notifications via Gmail in case of workflow failures 🚨 Key Benefits Saves time by automating pipeline tracking and reporting ⏱️ Provides visibility into pipeline bottlenecks and stuck deals 🔍 Maintains historical data for trend analysis and decision-making 📊 Ensures consistent reporting to sales leadership and management 🤝 Automates notifications for timely action on stuck deals ⚡ Reduces manual errors and improves sales process efficiency 🧹 Features Weekly trigger for automated execution 📆 GHL API integration to fetch opportunities and stage history ⚡ Code node to calculate stage durations and transform data 🛠️ Google Sheets automation for historical data storage 📂 If nodes to filter deals and handle errors ✅ Automated Gmail and Slack alerts for stuck deals ✉️💬 Weekly report generation with HTML and text formats 📊 Bottleneck and fastest stage identification for actionable insights 🔎 Error handling and notification for workflow reliability 🚨 Requirements n8n instance (cloud or self-hosted) GoHighLevel account with API access 🔑 Google Workspace (Sheets, Gmail) 📊 Slack workspace with Bot Token & channel access 💬 Target Audience Sales managers & teams using GoHighLevel for pipeline tracking 🏢 Operations teams seeking visibility into deal progress 💼 Leadership wanting automated weekly pipeline performance reports 📈 Agencies managing multiple deals and pipelines efficiently 🚀 Teams aiming to quickly identify bottlenecks and stuck deals ⚡ Step-by-Step Setup Instructions Configure n8n schedule trigger → Set to run every Monday at 8 AM. Connect GoHighLevel OAuth2 credentials → Ensure access to opportunities & pipeline data. Connect Google Sheets OAuth2 → Select document ID & sheet tab for logging data. Configure Gmail OAuth2 → Replace hardcoded email addresses with intended recipients. Connect Slack API → Select channel for stuck deal notifications. Update stuck deal threshold in “Filter Stuck Deals” node (default 7 days). Import workflow into n8n → Map credentials and test nodes sequentially. Enable workflow → Pipeline velocity tracking, stuck deal alerts, and weekly reports are fully automated. ✅. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description This workflow automates personalized candidate communication for both shortlisted and rejected applicants. It fetches candidate details, processes resumes, checks for errors, and uses GPT-4o to generate professional HTML emails. Shortlisted candidates receive congratulatory onboarding plans, while rejected candidates receive polite rejections with learning resources. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Starts the workflow execution. 📑 Candidate Data Fetch (Google Sheets) – Pulls structured candidate data (name, email, resume link, skills, job info, status). 📥 Resume Downloader (Google Drive) – Downloads candidate resumes from sheet links. ✅ Resume File Check (If Condition) – Ensures the resume file is valid before proceeding. ⚠️ Error Logging (Google Sheets) – Records failed or missing resumes in a dedicated sheet for audit. 📄 PDF → Text Extractor – Extracts raw resume text for deeper AI analysis. 🧩 Candidate Data Builder (Code Node) – Combines Google Sheets data with extracted resume text into a single enriched JSON object. 🎯 Shortlisted vs Rejected (If Condition) – Splits candidates into two flows based on their status field. Shortlisted Path 🎉 Congrats + Onboarding Plan (LLM Chain) – GPT-4o generates a congratulatory HTML email including: Identified skill gaps Recommended online courses (Coursera/Udemy/LinkedIn Learning) Next onboarding steps 📧 Candidate Mailer – Shortlisted (Gmail) – Sends the onboarding email directly to the candidate. Rejected Path 🙏 Polite Rejection + Learning Plan (LLM Chain) – GPT-4o generates a professional rejection email including: Empathetic rejection message Constructive feedback on skill gaps Learning resources to improve for future opportunities 📧 Candidate Mailer – Rejected (Gmail) – Sends the polite rejection + learning plan to the candidate. Prerequisites Google Sheets (candidate database + error log) Google Drive (resume storage) Gmail API (for sending candidate emails) Azure OpenAI (GPT-4o-mini model access) Key Benefits ✅ Automates candidate communication (both shortlisted & rejected) ✅ Delivers professional, HTML-ready emails ✅ Enhances candidate experience with personalized learning plans ✅ Prevents silent rejections by providing constructive resources ✅ Improves employer branding with empathetic communication ✅ Error resilience via logging and validation steps Perfect For Recruitment teams managing high candidate volume Companies looking to humanize rejections HR departments that want automated but personalized communication Organizations investing in candidate experience & employer brand. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description This workflow automates the evaluation of interviewer feedback using AI. It retrieves raw notes from Google Sheets, processes them through GPT-4o-mini for structured scoring, validates outputs, and calculates weighted quality scores. The system provides real-time Slack feedback to interviewers, logs AI errors for transparency, and recommends training if the feedback quality is low. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Runs the workflow manually to start evaluation. 📋 Fetch Raw Feedback Data (Google Sheets) – Reads all feedback entries (Role, Stage, Interviewer Email, Feedback Text, row_number). 🧠 AI Quality Evaluator (Azure GPT-4o-mini) – Processes feedback into structured JSON across 5 dimensions. 🔍 Analyze Feedback Quality (LLM Chain) – Applies scoring rules (Specificity, STAR, Bias-Free, Actionability, Depth) and outputs structured JSON. ✅ Validate AI Response – Ensures AI output isn’t undefined or malformed. 🚨 Log AI Errors (Google Sheets) – Records invalid AI responses for debugging and auditing. 🔄 Parse AI JSON Output (Code Node) – Converts AI JSON text into structured n8n objects with error handling. 🧮 Calculate Weighted Quality Score (Code Node) – Computes final weighted score (0–100), generates flags, formats vague phrases, and preserves context. 💾 Save Scores to Spreadsheet (Google Sheets) – Updates the original feedback row with Score, Flags, and AI JSON. 💬 Send Feedback Summary to Interviewer (Slack) – Sends interviewers a structured Slack report (score, flags, vague phrases, STAR improvement tips). 🎯 Check if Training Needed – Applies threshold logic: if score < 50, route to training recommendations. 📚 Send Training Recommendations (Slack) – Delivers STAR method guides and bias-free interviewing resources to low scorers. Prerequisites Google Sheets (Raw_Feedback + Error Log Sheet) Azure OpenAI API credentials (for GPT-4o-mini) Slack API credentials (for sending feedback & training notifications) n8n instance (cloud or self-hosted) Key Benefits ✅ Automated interview feedback quality scoring ✅ Bias detection and vague feedback flagging ✅ Real-time Slack feedback to interviewers ✅ Error logging for AI reliability tracking ✅ Training recommendations for low scorers ✅ Audit trail maintained in Google Sheets Perfect For HR & Recruitment teams ensuring structured interviewer feedback Organizations enforcing STAR method & bias-free hiring Teams seeking continuous interviewer coaching Companies needing audit-ready records of interview quality. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Automate your GoHighLevel (GHL) client onboarding process from the moment a deal is marked as “Won.” This workflow seamlessly generates client folders in Google Drive, duplicates contract and kickoff templates, schedules kickoff calls, sends branded welcome emails, creates onboarding tasks in GHL, and notifies your team in Slack. 🚀📂📧📅💬 What This Template Does Triggers automatically when an opportunity is marked as Won in GHL 🏆 Validates and formats client data to ensure clean records 🔍 Creates structured client folders in Google Drive 📂 Copies contract & kickoff deck templates with client-specific naming 📝 Sends personalized welcome email via Gmail ✉️ Schedules kickoff call in Google Calendar 📅 Creates onboarding tasks in GHL for account managers ✅ Sends Slack notifications to keep your team informed instantly 💬 Catches errors and sends alerts to a Slack error channel 🚨 Key Benefits Saves 30–45 minutes per onboarding ⏱️ Eliminates manual data entry and human errors 🧹 Guarantees consistent client experience across all deals 🤝 Automates document creation & sharing 📄 Ensures team visibility and faster response times 📲 Built-in validation and error handling for reliability 🔐 Features Webhook-based trigger from GoHighLevel ⚡ Automatic client data formatting and validation 🛠️ Google Drive folder & document automation with templates 📂 Personalized Gmail welcome email with branding ✉️ Automated kickoff call scheduling in Google Calendar 📅 Task creation in GHL for seamless follow-up 📌 Slack notifications for both success and error handling 💬 Error channel with detailed failure reports 🚨 Requirements n8n instance (cloud or self-hosted) GoHighLevel account with API access 🔑 Google Workspace (Drive, Gmail, Calendar) 📊 Slack workspace with Bot Token & channel access 💬 Pre-created contract and kickoff deck templates in Google Drive 📄 Target Audience Agencies & consultants using GoHighLevel for client management 🏢 Sales teams wanting instant onboarding after a deal closes 💰 Operations teams seeking consistent and repeatable onboarding flows ⚙️ Account managers who need structured onboarding tasks ✅ Businesses scaling client onboarding and reducing manual workload 🚀 Step-by-Step Setup Instructions Configure GHL webhook → Trigger on “Opportunity Status Changed = Won.” Connect your GHL API credentials (OAuth2 or API key). Add Google Drive OAuth2 credentials → Set parent folder ID & template IDs. Configure Gmail OAuth2 → Replace hardcoded email with client email variable. Connect Google Calendar → Select the calendar for kickoff calls. Connect Slack API → Choose channels for onboarding updates and errors. Update template IDs for contract and kickoff deck in the workflow. Import workflow into n8n, map credentials, and test once. Enable workflow → onboarding is now fully automated. ✅. An n8n automation workflow template by Rahul Joshi.

By Sheikh Masem Mandal

🚀 Cybersecurity News Automation Workflow This n8n automation workflow fetches daily cybersecurity news, cleans it, summarizes with AI, and posts it automatically to a Telegram channel. 🔎 Workflow Steps 1. Triggering the Workflow 9 AM - Schedule Trigger: Starts the workflow every day at 9 AM. 2. Fetching Cybersecurity News Bleeping Computer Security Bulletin: Pulls the latest news from the RSS feed. 3. Processing Articles HTTP Request → Filter Body → Extract Images: Retrieves the full article, cleans the HTML, and pulls image links. AI Agent (OpenRouter Grok): Summarizes the article snippet into 2 short sentences. Memory Buffer: Maintains short-term context across articles. 4. Merging Data Merge Node: Combines images, cleaned text, and AI-generated summaries. 5. Filtering Sponsored Content Sponsored Removal: Excludes articles with “Sponsored” in the creator field. 6. Posting to Telegram Loop Over Items + Send Photo Message: Publishes sponsor-free, summarized articles to @DailySecurityNewss telegram Channel. Each post includes: title, author, date, AI summary, categories, image (if available), and the “Read more” link. Wait 1 min: Adds a short delay to avoid spamming Telegram. 🎯 Outcome ✅ Daily feed of cybersecurity news ✅ Clean, AI-simplified summaries ✅ Images & links preserved ✅ Sponsored posts filtered ✅ Auto-posted to Telegram at 9 AM. An n8n automation workflow template by Sheikh Masem Mandal.

By Naveen Choudhary

Complete Template Description Automate LinkedIn Sales Navigator contact extraction to Google Sheets This workflow scrapes LinkedIn Sales Navigator search results and automatically saves contact details to Google Sheets with pagination support and rate limiting protection. Who's it for Sales teams, recruiters, and business development professionals who need to extract and organize LinkedIn contact data at scale without manual copy-pasting. What it does The workflow connects to a LinkedIn scraping API to fetch contact information from Sales Navigator search results. It handles pagination automatically, extracts contact details (name, title, company, location, profile URL), and appends them to a Google Sheet. Built-in rate limiting (30-60 second delays) prevents API blocks and mimics natural browsing behavior. Requirements Self-hosted n8n instance** (this workflow will NOT work on n8n Cloud due to cookie requirements and third-party API usage) LinkedIn Sales Navigator account Google Sheets account EditThisCookie browser extension API access from the creator (1 month free trial available) How to set up Step 1: Get API Access Email the creator to request 1 month of free API access using the link in the workflow. You'll receive your API key within 24 hours. Step 2: Configure API Authentication Click the "Scrape LinkedIn Contacts API" node Under Authentication, select "Header Auth" Create new credential with Name: x-api-key and your received API key as the Value Save the credential Step 3: Extract LinkedIn Cookies Install the EditThisCookie extension Navigate to LinkedIn Sales Navigator Click the cookie icon in your browser toolbar Click "Export" and copy the cookie data Paste into the cookies field in the "Set Search Parameters" node Step 4: Configure Your Search In the "Set Search Parameters" node, update: cookies: Your exported LinkedIn cookies url: Your LinkedIn Sales Navigator search URL total_pages: Number of pages to scrape (default: 2, each page = ~25 contacts) Step 5: Set Up Google Sheets Make a copy of the template Google Sheet (or create your own with matching column headers) In the "Save Contacts to Google Sheets" node, connect your Google Sheets account Select your destination spreadsheet and sheet name Important Security Note: Keep your LinkedIn cookies private. Never share them with others or commit them to public repositories. Customization options Adjust total_pages to control how many contacts you scrape Modify the delay in "Rate Limit Delay Between Requests" node (default: 30-60 seconds random) - do not lower this to avoid API blocks Customize which contact fields to save in the Google Sheets column mapping Change the search URL to target different prospect segments or filters. An n8n automation workflow template by Naveen Choudhary.

By Yang

Who’s it for This workflow is for marketers, influencer agencies, or outreach teams who want to quickly check if a TikTok user meets certain criteria before adding them to an influencer list. No manual profile checking—just drop in a username, and the system does the rest. What it does This workflow takes a TikTok username submitted via form, fetches the user’s profile using Dumpling AI, then evaluates the user using GPT-4 to decide if they qualify for influencer outreach based on predefined rules: 40+ videos 100,000+ followers 300,000+ total likes It then checks Google Sheets: If the user does not exist, it adds a new row If the user already exists, it updates the row How it works Form Trigger: Collects TikTok username Dumpling AI: Pulls TikTok profile (username, ID, followers, videos, likes, etc.) GPT-4: Checks if the user meets outreach criteria Google Sheets: Checks if user already exists Updates or appends user data + qualification status Requirements ✅ Dumpling AI API key (HTTP Header Auth) ✅ OpenAI API key (GPT-4) ✅ Google Sheets integration with the following columns: Tik Tok user User ID Follower Count Following Count Heart Count Video Count Qualified? How to customize Change the qualification logic in the GPT-4 prompt Add additional TikTok data (bio, profile pic, location, etc.) Send a notification if the user is qualified Push the qualified leads to Airtable, Notion, or your CRM > This workflow gives you a plug-and-play tool to qualify TikTok influencers instantly using AI—without leaving your browser or spreadsheet. An n8n automation workflow template by Yang.

By Nitesh

🧠 How It Works This AI Agent automatically qualifies property buyer leads from form submissions and sends them directly to your CRM. 🔄 Workflow Steps Form Submission Trigger When a user submits their details via a property inquiry form, the workflow is activated. AI Lead Classification The buyer’s input (budget, location, timeline, etc.) is analyzed by OpenAI. Structured data is extracted, and a lead score (0–100) is generated. Lead Qualification Logic Leads with a score ≥ 70 are marked as qualified. Leads with a lower score can be ignored or stored separately for later review. Follow-Up Actions (for Qualified Leads) An email notification is sent to the real estate agent. A record is created in Airtable to act as a lightweight CRM. ⚙️ How to Set Up 1. Form Setup Replace the default trigger with your preferred source: Typeform, Google Forms, Webflow form, etc. Ensure your form collects the following fields: Name, Email, Budget, Location, Timeline, Property Type 2. Connect Your Credentials Add your OpenAI API key for the LLM node Connect your Gmail account for notifications Link your Airtable base & table to store qualified leads 3. Customize Scoring Logic (Optional) Edit the Information Extractor prompt to tweak how scoring is calculated Example: prioritize budget fit, location, or timeline 4. Test the Workflow Submit a test entry via the form Confirm: You receive the notification email A new lead record appears in Airtable 5. Activate & Go Live Turn on the workflow Start qualifying real buyer leads in real-time 🎯 🚀 Use Cases Realtors → Filter out unqualified leads automatically Agencies → Save time by only engaging with high-quality inquiries Teams → Centralize qualified leads in Airtable for instant collaboration. An n8n automation workflow template by Nitesh.

By Yang

Who’s it for This template is perfect for digital agencies, SDRs, lead generators, or outreach teams that want to automatically convert LinkedIn company profiles into high-quality cold emails. If you spend too much time researching and writing outreach messages, this workflow does all the heavy lifting for you. What it does Once a LinkedIn company profile URL is submitted via a web form, the workflow: Scrapes detailed company data using Dumpling AI Enriches the contact (email, name, country) using Dropcontact Sends company data and contact info to GPT-4, which generates: A personalized subject line (max 8 words) A short HTML cold email (4–6 sentences) Sends the cold email via Gmail Logs the lead details to Airtable for tracking All AI-generated content follows strict formatting and tone guidelines, ensuring it's professional, human, and clean. How it works Form Trigger: Collects the LinkedIn URL Dumpling AI: Extracts company name, description, size, location, website, etc. Dropcontact: Finds the contact's email and name based on enriched company details GPT-4: Writes a structured cold email and subject line in JSON format Gmail: Sends the personalized email to a fixed recipient Airtable: Logs the lead into a specified base/table for follow-up Requirements ✅ Dumpling AI API key (stored in HTTP header credentials) ✅ Dropcontact API key ✅ OpenAI GPT-4 credentials ✅ Gmail account (OAuth2) ✅ Airtable base & table set up with at least these fields: Name LinkedIn Company URL People website How to customize Modify the GPT prompt to reflect your brand tone or service offering Replace Gmail with Slack, Outlook, or another communication tool Add a “review and approve” step before sending emails Add logic to avoid duplicates (e.g., check Airtable first) > This workflow lets you go from LinkedIn profile to inbox-ready cold email in less than a minute—with full AI support. An n8n automation workflow template by Yang.

By Yang

Who’s it for This template is perfect for content marketers, social media managers, and creators who want to repurpose YouTube videos into platform-specific posts without manual work. If you spend hours brainstorming captions, resizing content, or creating images for different platforms, this workflow automates the entire process from video selection to ready-to-publish posts. What it does The workflow takes a topic from a Google Sheet, finds the most relevant and recent YouTube video using Dumpling AI and GPT-4o, then automatically generates unique posts for Instagram, Facebook, and LinkedIn. Each post comes with a tailored AI-generated image, and all content is saved back into a Google Sheet for easy scheduling and review. Here’s what happens step by step: Picks an unsearched topic from Google Sheets Searches YouTube via Dumpling AI and sorts videos Uses GPT-4o to select the most relevant video Extracts the video transcript using Dumpling AI Generates three platform-specific posts using GPT-4o Creates matching images for each post using Dumpling AI image generation Saves the final Instagram, Facebook, and LinkedIn posts into a Google Sheet Marks the topic as processed so it won’t repeat How it works Scheduled Trigger: Starts the workflow automatically on a set schedule Google Sheets: Retrieves one unprocessed topic from the YouTube Topics sheet Dumpling AI: Finds and filters YouTube videos matching the topic GPT-4o: Chooses the best video and turns the transcript into three unique posts Dumpling AI (Image): Generates platform-specific visuals for each post Google Sheets: Saves all posts and images to the Social Media Post sheet for publishing Requirements ✅ Dumpling AI API key stored as credentials ✅ OpenAI GPT-4 credentials ✅ Google Sheets connection with the following sheets: YouTube Topics with columns Youtube Topics and Searched? Social Media Post with columns platform, Content, Image How to customize Adjust the GPT prompt to match your brand voice or content style Add or remove platforms depending on your posting strategy Change the schedule trigger frequency to fit your content calendar Integrate with scheduling tools like Buffer or Hootsuite for auto-publishing Add review or approval steps before posts are finalized > This workflow helps you transform a single YouTube video into three polished, platform-ready posts with matching visuals, in minutes—not hours. An n8n automation workflow template by Yang.

By Kaden Reese

Sync Open House Leads to HubSpot CRM Automatically capture and sync every open house visitor from SignSnapHome.com directly into HubSpot with intelligent lead scoring, automated follow-up emails, and comprehensive contact enrichment. Full Blog Writeup and Setup Video Overview This n8n workflow connects SignSnapHome (open house sign-in app) directly to HubSpot CRM. Every visitor who signs in at your open house is automatically created or updated as a contact in HubSpot, scored as HOT/WARM/COLD lead, and sent a personalized thank you email. Full Setup Tutorial: https://youtu.be/5GrrojIXr40 Perfect for: Real estate agents, brokerages, property managers, and home builders using SignSnap Home for open house sign-ins. Key Features Intelligent Lead Scoring (0-100 points) Base score: 50 points No real estate agent: +30 points High rating (4-5): +20 points Low rating (1-2): -20 points No buyer agreement: +10 points Final status: HOT (70+), WARM (50-69), COLD (0-39), OPEN (40-49) Automated Email Follow-Up Immediate personalized thank you email Conditional messaging based on agent status Different content for leads without agents (offers home buying assistance) Always includes invitation to ask questions Smart Contact Management UPSERT functionality (updates existing or creates new - no duplicates) Sets lifecycle stage to "Lead" Tags source as "Open House" with SignSnap attribution Comprehensive notes with visit details and scoring Flexible Custom Field Support Automatically detects ANY custom fields from your form No workflow modification needed for new fields Formats field names nicely (snake_case → Title Case) Workflow Structure Nodes: Webhook: SignSnap Home - Receives POST data Parse SignSnap Data - Processes and scores leads Has Email? - Validates required field Create/Update HubSpot Contact - Upserts contact Send Thank You Email - Automated follow-up Log Missing Email - Error handling Flow: SignSnap → Parse & Score → Email Check → HubSpot + Email └→ Log Error Setup Instructions Prerequisites SignSnap Home account HubSpot account (free or paid) SMTP email service (Gmail, SendGrid, etc.) n8n instance (self-hosted or cloud) Configuration Steps Configure HubSpot Credentials Add HubSpot OAuth2 credential in n8n Follow OAuth flow to connect Configure Email Credentials Add SMTP credential in n8n Test connection Update Email Settings Open "Send Thank You Email" node Change fromEmail to your address Customize footer if desired Activate & Connect Activate workflow in n8n Copy webhook URL Go to SignSnapHome.com → Settings → Automations Paste webhook URL Enable "Send on each submission" Optional: Custom HubSpot Properties Create these properties in HubSpot (Settings → Properties) for enhanced tracking: last_open_house_property (Text) - Property address visited last_open_house_date (Date) - Visit timestamp has_real_estate_agent (Dropdown) - Yes/No/Not specified property_interest_rating (Number) - 1-5 scale lead_score (Number) - Calculated score lead_status (Dropdown) - HOT/WARM/COLD/OPEN Note: Workflow functions without these - they enhance reporting only. What Gets Synced To HubSpot: Email, first name, last name, phone Lifecycle stage: "Lead" Lead source: "Open House" Visit details in notes (property, date, agent status, rating) Lead score and status All custom form fields Email Sent: Personalized greeting with first name Thank you for visiting [property] Conditional offer to help (if no agent) Invitation to ask questions Professional signature Lead Scoring Logic | Factor | Points | Reasoning | |--------|--------|-----------| | Base | 50 | Starting point | | No Agent | +30 | Available, not represented | | Rating 4-5 | +20 | High interest | | Rating 1-2 | -20 | Low interest | | No Buyer Agreement | +10 | Not contractually bound | Email Personalization Without Agent: > Hi [Name]! Thank you for visiting [Property] today. Our team would love to help you on your home buying journey! We specialize in this area and can provide exclusive listings and personalized service. If you have any questions... With Agent: > Hi [Name]! Thank you for visiting [Property] today. If you have any questions about this property or would like to schedule another viewing, please don't hesitate to reply... Error Handling No Email Provided: Cannot create HubSpot contact (email required) Lead logged to error output Can connect to Google Sheets or alert system Recommendation: Make email required in SignSnap Customization Ideas Auto-assign to agent - Match property to territory Create deals - Automatic deal creation for HOT leads Add to lists - Property-specific list segmentation Trigger workflows - HubSpot nurture sequences SMS follow-up - Add Twilio for text messages Photo upload - Attach guest photos to contacts Troubleshooting "Invalid email" - Check SignSnap email validation "Property doesn't exist" - Create custom property or remove from config "Authentication failed" - Reconnect HubSpot OAuth2 "No contacts appearing" - Check execution history, verify email provided "Email not sending" - Verify SMTP credentials and FROM address Analytics & Reporting Create these HubSpot reports: Open house conversion funnel Property performance by address Lead quality distribution (HOT/WARM/COLD) Agent performance metrics Source ROI analysis Use Cases Solo agents: Instant lead capture and follow-up Real estate teams: Centralized lead database Brokerages: Multi-agent, multi-property tracking Property managers: Attendance monitoring Home builders: Model home visitor capture Technical Details Endpoint: /signsnap-hubspot Method: POST Content-Type: application/json Processing Time: <2 seconds Error Rate: <1% (typically missing email only) Why Use This Workflow Zero manual data entry Instant lead scoring and prioritization Automated multi-channel follow-up No transcription errors Scales to unlimited open houses Works for solo agents or large teams Tags real-estate crm hubspot lead-management open-house signsnap automation contact-sync email-automation lead-scoring Difficulty: Intermediate Nodes: 6 Services: SignSnap Home, HubSpot, SMTP Setup Time: ~15 minutes. An n8n automation workflow template by Kaden Reese.

By Kaden Reese

🏠 SignSnapHome.com Open House Lead Management System Automatically capture, qualify, and follow up with open house visitors in real-time This comprehensive n8n workflow transforms your SignSnap Home open house sign-ins into a complete lead management system with instant notifications, intelligent lead scoring, and automated multi-channel follow-ups. View full blog writeup and YouTube video here: Open House n8n + SignSnapHome Automation 🎯 What This Workflow Does Transform every open house visitor into a managed lead with automated processing, scoring, and outreach—all without lifting a finger. Core Features 📸 Visual Lead Capture Automatically processes guest photos from sign-in Converts base64 images to proper binary format Displays guest photos as thumbnails in Discord notifications Supports JPEG, PNG, and other image formats 🎨 Smart Lead Scoring System 🔴 HOT Leads**: No agent + high rating (4-5 stars) → Immediate follow-up priority 🟠 WARM Leads**: Has agent but no buyer agreement → Potential opportunity 🟡 MEDIUM Leads**: Standard engagement level 🔵 COLD Leads**: Has agent with signed agreement OR low rating (1-2 stars) Color-coded Discord embeds for instant visual prioritization 📊 Rich Discord Notifications Beautiful embed cards with all guest information Guest photo thumbnail displayed inline Conditional fields (rating only shows if you have it enabled) Custom field support - ANY extra form fields automatically included Timestamp, contact info, property details Lead priority badge and color coding 📱 Intelligent SMS Follow-up (via Twilio) Sends personalized text message if phone number provided Different messaging for leads with/without agents Professional, warm tone that encourages response Simple "thank you for visiting" approach 📧 Professional Email Follow-up Beautiful HTML email template with gradient header Conditionally shows rating if available Different call-to-action based on agent status Branded footer with SignSnap Home mention Only sends if no phone number (SMS takes priority) Fallback to email if SMS not available ⚙️ Flexible Custom Field Support Automatically detects and processes ANY custom fields No workflow modification needed for new form fields Formats field names nicely (snake_case → Title Case) Displays all custom fields in Discord notification Perfect for additional questions like buyer agreements, prequalification status, etc. 📋 Workflow Structure Node Breakdown Webhook Trigger - Receives POST data from SignSnap Home Parse & Enrich Data - Extracts and processes all form data Separates standard vs custom fields Calculates lead priority score Formats timestamps and names Detects optional fields (like rating) Convert Image to Binary - Transforms base64 photo to n8n binary format Discord Notification - Sends rich embed with photo thumbnail Has Phone Number? - Conditional routing based on contact preference Send SMS (Twilio) - Priority follow-up via text message Has Email? - Fallback check if no phone provided Send Welcome Email - Professional HTML email follow-up ✨ Key Highlights Dynamic & Flexible No hardcoded fields** - automatically adapts to YOUR SignSnap form Works with default fields AND any custom fields you add Rating field is completely optional Handles missing data gracefully Smart Routing SMS-first approach (higher engagement rates) Automatic fallback to email if no phone Only sends what makes sense for each lead Professional Presentation Discord: Visual dashboard for your team SMS: Quick, personal outreach Email: Professional, branded communication Lead Intelligence Automatic qualification based on agent status Rating consideration (when available) Buyer agreement detection Priority-based follow-up suggestions 🔧 Setup Requirements Services Needed SignSnap Home Account - For open house sign-in app Discord Webhook - For team notifications Twilio Account - For SMS (optional but recommended) SMTP Email - For email follow-ups (optional) Configuration Steps Import this workflow into your n8n instance Set up Discord webhook: Create a webhook in your Discord channel Replace YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN in the HTTP Request node Configure Twilio (if using SMS): Add Twilio credentials in n8n Set your Twilio phone number Configure Email (if using email): Add SMTP credentials in n8n Update the "from" email address Activate your workflow Copy the webhook URL from n8n Configure SignSnap Home: Go to your open house settings Add the n8n webhook URL as your automation endpoint Enable "Send on each submission" (not batch) 📝 Optional Features You Can Add Rating Field Add a "What did you rate the house?" field (1-5 scale) Workflow automatically detects and displays it Affects lead scoring (high ratings = hotter leads) Buyer Agreement Field Add "Do you have a signed buyer agreement?" field Helps identify truly available leads Factors into WARM vs COLD lead classification Any Custom Fields Add ANY additional questions to your form They'll automatically appear in Discord notifications No workflow changes needed! 🎨 Customization Ideas Modify Lead Scoring Edit the JavaScript in the "Parse & Enrich Data" node to adjust: Lead priority thresholds Color coding Scoring criteria Change Message Templates SMS message in "Send SMS (Twilio)" node Email HTML in "Send Welcome Email" node Discord embed structure in "Discord Notification" node Add More Automation Save to Google Sheets/Airtable Create tasks in your CRM Send to Slack instead of/in addition to Discord Add to email marketing list Trigger other workflows 💡 Use Cases Real Estate Agents**: Instant lead capture and follow-up Property Managers**: Track open house attendance Real Estate Teams**: Centralized lead dashboard Brokerages**: Multi-agent lead distribution Home Builders**: Model home visitor tracking 🚀 Why This Workflow Rocks ✅ Zero Manual Work - Completely automated from sign-in to follow-up ✅ Intelligent - Smart lead scoring and routing ✅ Flexible - Adapts to YOUR form fields ✅ Professional - Polished notifications and outreach ✅ Multi-Channel - Discord, SMS, and Email coverage ✅ Visual - See guest photos instantly ✅ Scalable - Handle unlimited open houses ✅ Customizable - Easy to modify for your needs 📊 What You Get Instant Visibility**: See every visitor as they sign in Lead Intelligence**: Know who's hot and who's not Fast Follow-up**: Reach out while interest is hot Team Coordination**: Everyone sees the same data Professional Image**: Automated, timely communication Time Savings**: Hours of manual work eliminated 🔗 Integration Details Webhook Endpoint: /signsnaphome-sign-in-trigger Method: POST Content-Type: application/json Expected Format: SignSnap Home standard output 📞 Support & Customization This workflow is designed to work out-of-the-box with SignSnap Home, but can be adapted for: Other open house sign-in apps Different notification platforms Custom CRM integrations Additional automation steps ⚡ Quick Start Summary Import workflow Add Discord webhook URL (Optional) Configure Twilio for SMS (Optional) Configure SMTP for email Activate workflow Copy webhook URL Add to SignSnap Home settings Start collecting leads! 🎯 Perfect For Solo agents wanting to professionalize their follow-up Teams needing centralized lead management Brokerages tracking multiple open houses Anyone using SignSnap Home for open house sign-ins Transform your open house visitors into qualified, followed-up leads automatically. Never miss an opportunity again! Tags: real-estate, lead-management, automation, discord, twilio, sms, email, webhook, signsnap, open-house, crm Difficulty: Intermediate Nodes Used: 8 External Services: SignSnap Home, Discord, Twilio (optional), SMTP (optional). An n8n automation workflow template by Kaden Reese.

By Paul

✍️ AI-Powered SEO Blog Automation Workflow Complete PostgreSQL-backed system: Keyword scoring → AI research → Multi-part content generation → fal.ai Nano Banana image generation → WordPress publishing Real Example: AI Applications in Real Estate Playbook — fully generated, optimized, and published with this automation. 🚀 What You Get Full n8n Workflow Package Pre-configured automation** with 80+ connected nodes PostgreSQL schema** for keyword tracking & blog management 3-phase system**: Scoring → Planning → Generation Setup documentation** with customization guide Each Blog Post Includes 2,100+ words across 6 sections (Intro, Dev 1, Dev 2, Conclusion, FAQ, Header) 2 AI-generated images via fal.ai Nano Banana (16:9 format) Internal links to your existing content External citations to authoritative sources Complete SEO metadata (title, slug, description, tags) WordPress-ready draft ⚡ Core Features Keyword Intelligence Multi-factor scoring algorithm (volume, competition, CPC, relevance) Usage tracking prevents cannibalization AI agent selects optimal clusters avoiding impossible competition AI Content Pipeline Perplexity Sonar Pro deep research GPT-5 parallel section generation Grade 13-15 reading level Natural keyword distribution (no over-optimization) Image Generation fal.ai Nano Banana model** for contextual visuals Featured image (16:9) from research summary Body image (16:9) embedded in content Automatic alt text generation 10s wait + 5s retry logic Automation Infrastructure Queries existing posts to prevent duplicates Scheduled execution (every 2-3 days) Error handling with retry logic Non-blocking image generation 🔗 Required Services OpenAI (GPT-5, GPT-4o) OpenRouter (GPT-5 Mini) Perplexity AI (Sonar Pro) fal.ai (Nano Banana model)** WordPress REST API PostgreSQL database n8n instance 📊 Database Schema Keywords Table - Tracks scoring, usage, and Google Ads metrics Cluster Blog Table - Manages topic pipeline and published URLs Full SQL schema included in setup documentation. 🎯 Production Ready 10-15 posts/week** on autopilot 60% faster** than sequential generation (parallel processing) Usage tracking** prevents keyword reuse Customizable** scoring weights and relevance terms for any niche 🛠️ Setup Process Import n8n JSON workflow Create PostgreSQL tables (schema provided) Add API credentials Import keywords from Google Ads Planner Customize relevance terms for your industry Configure schedules and domain URL Test manually → Enable automation 💡 Perfect For Content marketers scaling to 10+ posts/week SEO agencies managing multiple sites Niche site builders needing consistent output WordPress users wanting hands-off publishing Low-authority sites targeting winnable keywords 🔧 Key Customization Points Scoring algorithm weights (volume/competition/CPC/relevance) Relevance terms for your industry (default: AI/automation) Publishing schedule (daily/3x week/weekly) Content length per section Image aspect ratio and format Website domain URL Stop writing blogs manually. This workflow handles research, writing, fal.ai Nano Banana image generation, linking, and publishing while you focus on strategy. An n8n automation workflow template by Paul.

By Geoffroy

This n8n template demonstrates how to automatically generate and publish SEO/AEO-optimized Shopify blog articles from a list of keywords using AI for content creation, image generation, and metadata optimization. Who’s it for Shopify marketers, content teams, and solo founders who want consistent, hands-off blog production with built-in SEO/AEO hygiene and internal linking. What it does The workflow picks a keyword from your Google Sheet based on priority, search volume, and difficulty. It then checks your Shopify blog for existing slugs to avoid duplicate, drafts a 900+ word article optimized for SEO/AEO, generates a hero image, creates the article in Shopify, sets SEO metafields (title/description), and logs the result to your Sheets for tracking and future internal links. How it works Google Sheets → Candidate selection:* Reads *Keywords, **Links, and Published tabs: ranks by priority → volume → difficulty. (In the workflow it is explained how to exactly set up the Google Sheets) De-dupe slugs:** Paginates your blog via Shopify GraphQL to collect existing handles and make sure to use a different one. OpenAI content + image:** Builds a structured prompt (SEO/AEO and internal linking), calls Chat Completions and Image Generation for a hero image. Shopify publish:** Creates the article via REST and updates title_tag / description_tag metafields via GraphQL. Log + link graph:* Appends to *Published* tab to keep track of articles posted and *Links** tab for ongoing internal-link suggestions. How to set up Open Set – Config and fill: shopDomain, siteBaseUrl, blogId, blogHandle, sheetId, author. Optional: autoPublish, maxPerRun, tz. Create the Google Sheet with Keywords, Links, Published tabs using the provided column structure. I have personally used Semrush to generate that list of keywords. Add credentials: Shopify Admin token (Header/Bearer), OpenAI API key, and Google Service Account. Requirements Shopify store with Blog API access OpenAI API key Google Service Account with access to Google Sheets API (can be activated here here) How to customize Change the cron in Schedule Trigger for different days/times. Adjust maxPerRun, autoPublish, language or any other variables in the "Set - Config" node. Adjust the prompt from the "Code - Build Prompt" node. Extend the Sheets schema with extra scoring signals if needed. An n8n automation workflow template by Geoffroy.

By Buay Biel

Initial Outreach Email Workflow This n8n template demonstrates how to automate personalized cold email outreach using AI and a lead database. It’s designed to contact unengaged leads, personalize messages at scale, and schedule follow-ups automatically. Use cases are many: Reach out to new leads, qualify prospects, start conversations, and set up consistent follow-up routines. Great for sales teams, recruiters, and agencies running cold outreach campaigns. Good to know Each AI personalization costs about $0.001 with Groq (free tier available; pricing may vary by provider). The workflow limits emails to 15 per day by default to protect your email reputation and reduce spam risk. The email template is fully customizable to match your brand tone and offer. Outreach timing and follow-up intervals are easy to adjust within the workflow. How it works NocoDB** fetches leads who haven’t been contacted yet (no “Initial Contact Date”). The Limit node ensures no more than 15 emails per run. AI personalizes** your chosen email template with lead name and company. Emails are sent via SMTP or Gmail node. Each contacted lead is updated in the database with today’s Initial Contact Date and a Next Follow-up Date (default 3 days later). The workflow runs on a daily schedule at 10:30 AM (configurable). How to use Set up a NocoDB/any database table with: first_name email Initial Contact Date Next Follow up/Contact organization_name (optional) Customize the email template inside the AI node. Adjust the daily limit and schedule to match your outreach capacity. Import leads into NocoDB and configure credentials for NocoDB, AI provider, and SMTP. Run the workflow manually for testing before going live. An n8n automation workflow template by Buay Biel.

By Parth Pansuriya

Analyze Ingredient Photos using Telegram & Gemini AI Who’s it for Skincare enthusiasts who want to know if a product is safe. Food or supplement buyers checking ingredient safety. Parents reviewing kids’ products. Anyone wanting quick ingredient analysis before using/buying a product. How it works / What it does Telegram Input – User sends a photo of a product label or a text list of ingredients. Photo Handling – Workflow checks if the message contains a photo. If yes → retrieves the file, extracts ingredients using Google Gemini AI. If no → handles text/greetings/off-topic queries. Caption Branching With caption → Gives Use / Do Not Use recommendation + reason. Without caption → Gives Advantages, Disadvantages, Recommended For, Not Recommended For (3 points each). Response on Telegram – Sends a friendly, structured response back to the user. How to set up Import this workflow JSON into n8n. Create and connect a Telegram bot via BotFather → paste the API token in Telegram credentials. Add Google Gemini (PaLM) API credentials inside n8n. Activate the workflow and send your first product photo via Telegram! Requirements n8n instance (self-hosted or cloud). Telegram bot token. Google Gemini API credentials. How to customize the workflow Change AI Instructions** – Update system messages to tweak tone (more technical, casual, or medical). Adjust Output Format** – Edit Telegram response nodes for shorter/longer answers. Expand Analysis** – Add extra categories (e.g., allergens, environmental impact). Multi-language Support** – Modify prompts to output in the user’s preferred language. Add Database Logging** – Connect to MySQL, PostgreSQL to save conversations (user queries + AI responses). An n8n automation workflow template by Parth Pansuriya.