Browse 13,012 Workflows

By Nima Salimi

Overview This n8n workflow automatically retrieves the monthly CrUX (Chrome User Experience) Report from Google BigQuery and updates the data in NocoDB. It removes the previous month’s data before inserting the new dataset, ensuring your database always contains the latest CrUX rankings for website origins. The flow is fully automated, using schedule triggers to handle both data cleanup and data insertion each month. ✅ Tasks ⏰ Runs automatically on a monthly schedule 🔢 Converts the month name to a numeric value for table selection 🧹 Deletes last month’s CrUX data from NocoDB 🌐 Queries Google BigQuery for the latest monthly dataset 💾 Inserts the new CrUX rankings into NocoDB ⚙️ Keeps your database up to date with zero manual effort 🛠 How to Use 1️⃣ Set Up BigQuery Access Connect your Google BigQuery credentials. Make sure your project includes access to the chrome-ux-report public dataset. 2️⃣ Adjust the Query In the Google BigQuery node, change the LIMIT value to control how many top-ranked sites are retrieved. Ensure the {{ $json.table }} field correctly references the dataset for the desired month (e.g., 202509). 3️⃣ Prepare NocoDB Table Create a table in NocoDB with fields: origin, crux_rank, and any additional metadata you wish to track. 4️⃣ Schedule Automation The workflow includes two Schedule Trigger nodes: One runs the data cleanup process (deletes last month). One runs the data insertion for the new month. 5️⃣ Run or Activate the Workflow Activate it to run automatically each month. You can also run it manually to refresh data on demand. 📋 Prerequisites Before running this workflow, make sure you complete the following setup steps: 🧱 Enable BigQuery API Go to Google Cloud Console → APIs & Services Enable the BigQuery API for your project. 📊 Access the Chrome UX Report Dataset In BigQuery, search for “Chrome UX Report” in the Marketplace or go directly to: https://console.cloud.google.com/marketplace/product/chrome-ux-report/chrome-ux-report Click “View Dataset” and add it to your BigQuery project. 🔑 Connect BigQuery to n8n In n8n, create credentials for your Google BigQuery account using Service Account Authentication. Ensure the account has permission to query the chrome-ux-report dataset. 🗄️ Create a NocoDB Table In NocoDB, create a new table to store your CrUX data with the following fields: origin → Short text crux_rank → Number ⚙️ Connect NocoDB to n8n Use your NocoDB API Token to connect and allow the workflow to read/write data. What is CrUX Rank? CrUX Rank (Chrome User Experience Rank) is a metric from Google’s Chrome UX Report (CrUX) dataset that indicates a website’s popularity based on real user visits. It reflects how frequently an origin (website) is loaded by Chrome users around the world. A lower rank number means the site is more popular (e.g., rank 1 = top site). The data is collected from anonymized Chrome usage statistics, aggregated monthly. This rank helps you track site popularity trends and compare your domain’s visibility over time. An n8n automation workflow template by Nima Salimi.

By Anatoly

AI-Powered Voice Appointment Booking with ElevenLabs Transform your appointment scheduling with this production-ready workflow that connects ElevenLabs voice AI to your Google Calendar. Patients can call and book appointments naturally through conversation, while the system handles real-time availability checking, calendar management, and automated confirmations—completely hands-free. 🎯 What It Does: Voice-Activated Booking: Patients speak naturally to book appointments via ElevenLabs AI agent Real-Time Availability: Instantly checks calendar conflicts and returns available time slots Smart Scheduling: Automatically generates available 30-minute slots across business hours for the next 30 days Calendar Sync: Creates Google Calendar events with all appointment details, locations, and attendees Email Confirmations: Sends personalized HTML confirmation emails with appointment details and preparation instructions Dual Functionality: Handles both "check availability" queries and "book appointment" requests through a single webhook 💼 Perfect For: Medical/dental clinics • Beauty salons • Spas • Consulting services • Legal offices • Fitness studios • Therapy practices • Any appointment-based business seeking 24/7 automated scheduling Real conversation example: Voice version: https://drive.google.com/file/d/1CjhyjICTtLioA737SOkpbgcdLdUpVCr3/view Text version: ++AI Voice Assistant++ (00:00) Hello, I'm Ella from Evergreen Clinic. How can I assist you today? ++Patient++ (00:05) Hello Ella, I wanted to book an appointment for Botox treatment. ++AI Voice Assistant++ (00:11) I'd be happy to help you schedule a Botox appointment. Our Botox treatments take about 20 minutes and are performed by Dr. Sava or our nurse injector Sarah. Would you prefer our Zurich or Bern location? ++Patient++ (00:24) I prefer Zurich. ++AI Voice Assistant++ (00:28) great Zurich it is. Do you have a specific date in mind for your Botox appointment? ++Patient++ (00:32) Yeah, October the 7th and let's say 5 p.m. ++AI Voice Assistant++ (00:47) I have the 5 p.m. slot available on October 7th in Zurich. May I have your first name to proceed with the booking? ++Patient++ (00:54) Yes, my first name Anatoly, surname Sava. ++AI Voice Assistant++ (01:02) Thank you, Anatoly Sava. Could you please provide your email address for the appointment confirmation? Please spell it out slowly. ++Patient++ (01:08) [Your Email] ++AI Voice Assistant++ (01:19) Thank you. Just to confirm, your email is [Your Email] correct? ++Patient++ (01:29) Yes. ++AI Voice Assistant++ (01:34) Perfect. Lastly, may I have your phone number to complete the booking? ++Patient++ (01:39) My phone number is [Your Number] ++AI Voice Assistant++ (01:51) Thank you for the details, Anatoly. I will now book your Botox appointment in Zurich on October 7th at 5 p.m. Perfect. I've booked your Botox appointment at our Zurich clinic on October 7th at 5 p.m. A confirmation email will be sent to [Your Email]. Thank you for choosing Evergreen Clinic. If you have any questions before your appointment, please don't hesitate to call us back. Have a wonderful day. ++Patient++ (02:19) Perfect. You too. ++AI Voice Assistant++ (02:22) Thank you, take care and have a great day ahead. 🔧 Technical Features: Intelligent routing logic distinguishes between availability checks and booking requests Custom JavaScript algorithm calculates conflict-free time slots Timezone-aware date/time handling (customizable for any timezone) Configurable business hours, appointment duration, and look-ahead period Natural language date formatting for voice responses Webhook-based architecture for seamless ElevenLabs integration 📋 Requirements: ElevenLabs account (for voice agent) Google Calendar Gmail address for confirmations ⚡ Quick Setup: Step 1: n8n Configuration Connect your Google Calendar, customize business hours in the code node, update clinic details in the email template. Includes pinned test data for easy testing before going live. Step 2: ElevenLabs Agent Setup 1) Create a new Conversational AI Italicagent in ElevenLabs 2) Configure two tools into ElevenLabs with webhook URL pointing to this workflow: check_availability(date, time, appointmentType, location) book_appointment(fullName, email, phone, date, time, appointmentType, location) Create a detailed system prompt defining your agent's identity, personality, tone of voice, and conversation behavior This is a chunk of a system prompt (the full version is too long): IDENTITY You are Ella, an appointment scheduling voice assistant for Evergreen Clinic, which specializes in plastic surgery procedures. Your primary purpose is to efficiently schedule, confirm, reschedule, or cancel appointments while providing accurate information about services from your knowledge files only. VOICE & STYLE Use a friendly, professional yet warm tone suitable for a plastic surgery clinic Keep all your responses short and simple. Use casual language, phrases like "Umm..", "Well...", and "I mean" are preferred. NEVER interrupt a patient if they start talking This is a voice conversation, so keep your responses short, like in a real conversation. Don't ramble for too long. Keep responses concise (8-15 words per sentence ideal) Use natural speech patterns with occasional phrases like "I understand" and "Of course..." Insert brief pauses between information chunks to sound natural Show empathy and sensitivity appropriate for plastic surgery clients Never rush the caller, but keep the conversation focused Maintain a reassuring tone when discussing procedures Zürich — pronounce /ˈtsyːʁɪç/. In plain terms: start with “ts”, the ü is like French u in tu (rounded front, not “oo”), stress the first syllable, and the final “ch” is the soft German sound as in ich (not “k”). Avoid saying “ZOO-rich.” Bern — pronounce /bɛrn/. Short e like in bet, single r (not American “urn”), no extra vowel at the end. Avoid saying “BURN.” Full ElevenLabs set up guide: https://youtu.be/kbiWe93nFMk?si=_bQYIoq1cjXKO5kl 🎁 What You Get: Complete end-to-end automation with detailed sticky note documentation, live conversation example, video tutorial, system prompt template, customization guides, troubleshooting tips, and security best practices. An n8n automation workflow template by Anatoly.

By Shahrear

📜 AI-Powered Contract Management Pipeline (Google Drive + VLM Run + Sheets + Calendar + Slack) ⚙️ What This Workflow Does This workflow automatically extracts, organizes, and tracks legal contract details from documents uploaded to Google Drive. Using VLM Run’s Execute Agent, it parses key metadata such as contract ID, parties, dates, and terms — then stores, alerts, and schedules reminders through Google Sheets, Calendar, and Slack. 🧩 Requirements Google Drive OAuth2** for monitoring and downloads VLM Run API credentials** with Execute Agent access Google Sheets OAuth2** for structured record storage Google Calendar OAuth2** for key date reminders Slack API credentials** for team notifications A reachable Webhook URL (for receiving parsed contract data) ⚡Quick Setup Configure Google Drive OAuth2 and create upload folder and folder for saving extracted images. Install the verified VLM Run node by searching for VLM Run in the node list, then click Install. Once installed, you can start using it in your workflows. Add VLM Run API credentials for document parsing. Configure Google Sheet and Calendar. For Google Sheet, from the document list, pick your Google Sheet (e.g., test). Then select the sheet inside it (e.g., Sheet1). Set the operation to Append Row — this will add new contract details as new rows. Turn on Map Each Column Manually. Match each contract field (like Contract ID, Title, Parties, Effective Date, Termination Date) to its corresponding column in your Google Sheet. Configure Slack for notifications. ⚙️ How It Works Monitor Contract Uploads – Watches a target Google Drive folder for new file uploads (PDFs, images, or scans). Download Contract File – Automatically downloads new contracts for AI analysis. VLM Run ContractParser – Sends the file to the VLM Run Execute Agent, which extracts structured contract data, including: Contract ID Title Parties (with roles) Property address Effective date Termination date Rent, deposit, payment terms, and governing law Receive Contract Data – The webhook endpoint receives the structured JSON response. Format Contract Data – Normalizes fields, formats dates, and prepares for storage. Save to Expense Database (Google Sheets) – Appends extracted data to a master Google Sheet for centralized contract tracking. Notify via Slack – Posts a concise summary to a Slack channel, showing key contract details for visibility. Create Calendar Events – Automatically schedules Google Calendar events for: Effective Date Termination Date Renewal Reminder (60 days before termination) 💡 Why Use This Workflow Manual contract management is error-prone and time-consuming key details like renewal dates, payment terms, or termination clauses often get lost in email threads or folders. This workflow ensures: Zero missed deadlines** automatic Google Calendar reminders keep your team on track. Instant team visibility** - Slack notifications keep legal, finance, and operations aligned. End-to-end automation** no need for manual parsing, data entry, or follow-ups. 🧠 Perfect For Legal teams automating contract intake and tracking Real estate or lease management workflows Finance or procurement teams needing expiration alerts Organizations centralizing contract metadata in Sheets 🛠️ How to Customize Modify Extraction Fields Edit the VLM Run Execute Agent schema to add fields like contract value, payment schedule, department, or contact email. Change Storage Swap Google Sheets for Airtable, Notion, or BigQuery if you manage large datasets or need relational tracking. Customize Notifications Send Slack alerts only for high-value or expiring contracts, and tag relevant teams (e.g., @legal, @finance). Add Calendar Events Auto-create events for reviews or payment milestones using extra date fields. Add Approvals or Signatures Insert a Google Form or Slack approval step, or trigger DocuSign for e-signature automation. ⚠️ Community Node Disclaimer This workflow uses community nodes (VLM Run) that may need additional permissions and custom setup. An n8n automation workflow template by Shahrear.

By Yassin Zehar

Description This workflow sends a personalized email when a task in a Google Sheet is marked as Urgent, but only once per task. It prevents duplicate notifications by updating the sheet after the email is sent. Ideal for collaborative task tracking where multiple people edit the same spreadsheet. Context When working with shared task lists in Google Sheets, it’s easy to miss critical updates — or worse, trigger multiple alerts for the same task. This workflow ensures that each "Urgent" task only sends one email notification, and then marks it as “Notified” to avoid duplicates. Target Users Project Managers using Google Sheets Operations or support teams managing collaborative task boards Anyone who needs alert automation with built-in anti-spam logic Technical Requirements Google Sheets account with edit access Gmail account for sending notifications Google Sheet with columns: Priority Notified Task Owner Deadline Status Next Step Workflow Steps Trigger: Watches for changes in Google Sheets (e.g., edits to the "Priority" column) IF Node – Checks that: Priority = Urgent Notified is empty row exists (required for update) Send Email: Sends a personalized message with task details Update Row: Writes “Yes” in the Notified column to avoid duplicate alerts Setup Instructions To set up this workflow: Connect your Google Sheets and Gmail credentials in n8n. Copy the spreadsheet structure or use your own Import the workflow, select your Sheet (and the column to check if you use a different Google Sheets template), and test by marking a task as “Urgent”. Check that an email is sent and the “Notified” column updates to “Yes”.- Key Features ✅ One email per urgent task — prevents duplicates 📧 Dynamic email content with task info 🧠 Built-in anti-spam logic 📋 Simple to configure and reuse 💬 Customizable for any team’s needs Expected Output An email alert is sent only once per task marked as Urgent The Notified field is updated in the Google Sheet A clean and scalable alert system with no duplicates Tutorial video: Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin. An n8n automation workflow template by Yassin Zehar.

By Mihail Morosan

Get the latest news, from Kagi, with a workflow that lets you filter by news category. Feed the results in your voice assistant automations to get on-demand news. Or leverage LLM models to create daily summaries from the headlines you retrieved. How it works This workflow takes a category name, from the ones available on Kagi News, then uses the Kagi News API to get all of the day's stories in that category. It then does a bit of filtering, to make it easier to manipulate. But you can skip or change that to your liking. How to use To test it, simply change the pinned data in the Start node, particularly the category field. You can use such examples as World, UK or Technology. Unsure as to what options for category there are? Just run the workflow and check the output of the Split Categories node! It will list all categories available. Take the value from categoryName. Things to consider I used categoryName as the input instead of categoryId for one reason: to make it easier for LLMs to populate that field. If this doesn't work for you, it should be quite easy to change. It is also a single category at a time. If you want to get stories from more categories at once, you can take an array as input in Start, then filter on the categories list containing your entries, rather than an exact match. Finally, you will have to merge all calls to Split out stories after each call to the API. Requirements None beyond an internet connection for your n8n instance. There is no API access token needed or any authorisation of any kind. An n8n automation workflow template by Mihail Morosan.

By Julian Kaiser

Automatically Scrape Make.com Job Board with GPT-5-mini Summaries & Email Digest Overview Who is this for? Make.com consultants, automation specialists, and freelancers who want to catch new client opportunities without manually checking the forum. What problem does it solve? Scrolling through forum posts to find jobs wastes time. This automation finds new postings, uses AI to summarize what clients need, and emails you a clean digest. How it works: Runs on schedule → scrapes the Make.com professional services forum → filters jobs from last 7 days → AI summarizes each posting → sends formatted email digest. Use Cases Freelancers: Get daily job alerts without forum browsing, respond to opportunities faster Agencies: Keep sales teams informed of potential clients needing Make.com expertise Job Seekers: Track contract and full-time positions requiring Make.com skills Detailed Workflow Scraping: HTTP module pulls HTML from the Make.com forum job board Parsing: Extracts job titles, dates, authors, and thread links Filtering: Only jobs posted within last 7 days pass through (configurable) AI Processing: GPT-5-mini analyzes each post to extract: Project type Key requirements Complexity level Budget/timeline (if mentioned) Email Generation: Aggregates summaries into organized HTML email with direct links Delivery: Sends via SMTP to your inbox Setup Steps Time: ~10 minutes Requirements: OpenRouter API key (get one here) SMTP credentials (Gmail, SendGrid, etc.) Steps: Import template Add OpenRouter API key in "OpenRouter Chat Model" node Configure SMTP settings in "Send email" node Update recipient email address Set schedule (recommended: daily at 8 AM) Run test to verify Customization Tips Change date range: Modify filter from 7 days to X days: {{now - X days}} Keyword filtering: Add filter module to only show jobs mentioning "API", "Shopify", etc. AI detail level: Edit prompt for shorter/longer summaries Multiple recipients: Add comma-separated emails in Send Email node Different AI model: Switch to Gemini or Claude in OpenRouter settings Team notifications: Add Slack/Discord webhook instead of email. An n8n automation workflow template by Julian Kaiser.

By Jean-Marie Rizkallah

🛡️ Jamf Policy Integrity Monitor 🎯 Overview A security-focused n8n workflow that monitors Jamf Pro policies for any unauthorized or accidental modification. It delivers configuration integrity and real-time visibility across managed Apple environments. ⚙️ Setup Instructions Add your Jamf Pro and Slack credentials in n8n. Import the workflow template. Configure your preferred schedule and alert channel. No coding required. The setup takes minutes. 🔍 How It Works The workflow connects to Jamf Pro API, detects configuration changes, and sends instant alerts to Slack. It maintains awareness of policy integrity while minimizing manual checks. The logic runs automatically in the background for continuous monitoring. 📢 Slack Notification Example :warning: Policy: Uninstall EDR modified :calendar: DateTime: Oct 5, 2025, 10:23:27 AM ✅ Why It Matters Jamf provides no built-in alerts when policies are modified. This workflow closes that visibility gap and gives your team instant awareness of policy changes without manual auditing. Ideal for security engineers, Jamf administrators, and compliance teams focused on operational assurance. An n8n automation workflow template by Jean-Marie Rizkallah.

By Ahmed Sherif

Personalized Cold Email System with Google Gemini AI and Telegram Approval An AI-powered cold email automation that uses Google Gemini to generate personalized outreach and a Telegram workflow for manual approval, ensuring high-quality, human-in-the-loop campaigns. Features Smart Lead Selection**: Fetches leads with an "Available" status from a designated Google Sheet. AI Email Generation**: Google Gemini creates a personalized subject line and email body based on lead data. Telegram Approval**: Sends each generated email to a Telegram chat for a one-click "Approve" or "Reject" decision. Edit & Regenerate**: Allows users to provide feedback on rejected emails, which the AI uses to regenerate a new version for re-approval. Auto-Send**: Approved emails are automatically dispatched via a configured SMTP server, including a professional signature. Complete Tracking**: Updates three separate Google Sheets (Filtered Leads, Sent Leads, Emails Sent) to maintain a clear audit trail. Rate Limiting**: A one-second delay between email sends helps avoid spam filters and protects sender reputation. Batch Processing**: Handles three leads per execution by default, which is configurable to scale up or down. How It Works A manual trigger initiates the workflow and captures the current date and time for logging. The system fetches a set number of leads (default is three) from the Filtered Leads sheet where the status is "Available". It loops through each lead individually to generate and send a unique email. The AI generates a personalized email (Subject + Body) using the lead's data. A preview of the email is sent to a specified Telegram chat with "Approve" and "Reject" buttons. If approved: The email is sent via SMTP. The lead's status is updated, and logs are written to the Sent Leads and Emails Sent sheets. The system waits one second before processing the next lead. If rejected: The system prompts the user for feedback in Telegram. The feedback is combined with the original prompt to generate a new email draft, which is sent for re-approval. A final notification is sent to Telegram when the batch is complete. Requirements Google Sheets with three tabs (see structure below). Telegram Bot Token and user/group Chat ID. Google Gemini API Key. SMTP Email Account credentials (server, port, username, password). Setup Instructions Google Sheets Setup: Create a new Google Sheet. Rename three tabs to exactly Filtered Leads, Sent Leads, and Emails Sent. Populate the Filtered Leads sheet with your lead data according to the structure specified below. API Credentials: Google Gemini: Generate an API key from your Google AI Studio account. Telegram Bot: Create a new bot by messaging @BotFather on Telegram and follow the prompts to get your API token. Get your Chat ID by messaging @userinfobot. SMTP Configuration: Obtain the SMTP server address, port, username, and password from your email provider (e.g., Google Workspace, Outlook). Automation Platform: In your automation platform (e.g., n8n, Make), create a new workflow. Connect your Google Sheets account using OAuth2. Add the Gemini API Key, Telegram Bot Token, Chat ID, and SMTP credentials into the respective modules or credential stores. Map the sheet columns to the variables in the workflow modules. Google Sheets Structure The automation requires the following column headers in each sheet. The names must be exact. Filtered Leads (Input Sheet)** FirstName: Lead's first name. LastName: Lead's last name. Email: Lead's email address. CompanyName: Name of the lead's company. JobTitle: Lead's current job title. Website: Company website (for AI context). LinkedIn: URL of the lead's LinkedIn profile. Notes: Any specific details or pain points for personalization. Status: Workflow status. Set to Available for leads ready to be processed. Sent Leads (Tracking Sheet)** Email: Email address of the contacted lead. CompanyName: Name of the company. TimestampSent: Date and time the email was sent. Emails Sent (Archive Sheet)** RecipientEmail: The lead's email address. Subject: The exact subject line that was sent. Body: The full email body that was sent. TimestampSent: Date and time the email was sent. Customization Guide This template can be adapted to fit specific campaign needs. Batch Size**: The number of leads processed per execution is controlled by the initial "Get Leads" module. Change the Limit parameter from 3 to your desired number. AI Prompt**: The core of the personalization is the prompt sent to the Gemini API. Modify this prompt to change the email's tone, structure, or call-to-action. You can instruct the AI to focus on specific data from the Notes column or reference a different value proposition. Lead Filtering**: The trigger condition is set to pull leads where Status = "Available". This can be changed to any other logic, such as Priority = "High" or Campaign = "Q4-Push", by adjusting the filter in the Google Sheets module. Email Signature**: The signature is typically configured within the SMTP "Send Email" module. Update the HTML or plain text here to change the signature across all sends. Telegram Notifications**: The text and buttons sent to Telegram for approval can be modified. You can add more lead data to the approval message (e.g., Job Title, Company Name) to give the approver more context. An n8n automation workflow template by Ahmed Sherif.

By Gracewell

Who Is This For? This workflow is designed for educators, universities, examination departments, and EdTech institutions that need a faster, smarter, and standardized way to prepare exam question papers. What Problem Does This Solve? Creating balanced, outcome-based question papers can take hours or even days of manual effort. Faculty often struggle to: Ensure syllabus coverage across units Maintain Bloom’s Taxonomy alignment Keep a consistent difficulty balance Format papers in institution-specific templates How it works This workflow automatically generates an exam question paper based on syllabus topics submitted via a form and sends it to the entered email address. Here’s the flow in simple steps: Form Submission – A student or faculty fills out a form with subject code, syllabus topics, and their email. AI Question Generation – The workflow passes the syllabus to AI agents (Part A with 2 Marks, Part B with 13 Marks, and Part C with 14 Marks) to create question sets. The marks and the no. of question generated can be customized according to the convenience. Merging Questions – All AI-generated questions are combined into a single structured document. Format into HTML – The questions are formatted into a clean HTML exam paper (can also be extended to PDF). Send by Email– The formatted exam paper is sent to the user’s email (with option to CC/BCC). Set up steps Connect Accounts Connect your OpenAI (or LLM) credentials for AI-powered question generation. Connect your Gmail (or preferred email service) to send emails. Prepare Form Create an n8n form trigger with required fields: Subject with Code Syllabus for Unit 1, 2, 3… Email to receive the paper Customize Question Generation Modify the AI prompts for Parts A, B, and C to fit your syllabus style (e.g., 2-mark, 13-mark, 14-mark). Format the Exam Paper Adjust the HTML template to match your institution’s exam paper layout. Test & Deploy Submit a test form entry. Check the received email to ensure formatting looks good. Deploy the workflow to production for real usage. Need help customizing? Contact Me | LinkedIn. An n8n automation workflow template by Gracewell.

By John

How it works User Signup & Verification: The workflow starts when a user signs up. It generates a verification code and sends it via SMS using Twilio. Code Validation: The user replies with the code. The workflow checks the code and, if valid, creates a session for the user. Conversational AI: Incoming SMS messages are analyzed by Chat GPT AI for sentiment, intent, and urgency. The workflow stores the conversation context and generates smart, AI-powered replies. Escalation Handling: If the AI detects urgency or frustration, the workflow escalates the session—alerting your team and sending a supportive SMS to the user. Set up steps Estimated setup time:** 10–20 minutes for most users. What you’ll need:** A free n8n account (self-hosted or cloud) Free Twilio account (for SMS) OpenAI API key (for AI) A PostgreSQL database (Supabase, Neon, or local) Setup process:** Import this workflow into n8n. Add your Twilio and OpenAI credentials as environment variables or n8n credentials. Update webhook URLs in your Twilio console (for incoming SMS). (Optional) Adjust sticky notes in the workflow for detailed, step-by-step guidance. An n8n automation workflow template by John.

By Intuz

This n8n template from Intuz provides a complete and automated solution for identifying high-intent leads from LinkedIn job postings and automatically generating personalized outreach emails. Disclaimer Community nodes are used in this workflow. Who’s this workflow for? B2B Sales Teams & SDRs Recruitment Agencies & Tech Recruiters Startup Founders Growth Marketing Teams How it works 1. Scrape Hiring Signals: The workflow starts by using an Apify scraper to find companies actively hiring for specific roles on LinkedIn (e.g., “ML Engineer”). 2. Filter & Qualify Companies: It automatically filters the results based on your criteria (e.g., company size, industry) to create a high-quality list of target accounts. 3. Find Decision-Makers: For each qualified company, it uses Apollo.io to find key decision-makers (VPs, Directors, etc.) and enrich their profiles with verified email addresses using user’s Apollo API. 4. Build a Lead List: All the enriched lead data—contact name, title, email, company info—is systematically added to a Google Sheet. 5. Generate AI-Powered Emails: The workflow then feeds each lead’s data to a Google Gemini AI model, which drafts a unique, personalized cold email that references the specific job the company is hiring for. 6. Complete the Outreach List: Finally, the AI-generated subject line and email body are saved back into the Google Sheet, leaving you with a fully prepared, hyper-targeted outreach campaign. Setup Instructions 1. Apify Configuration: Connect your Apify account in the Run the LinkedIn Job Scraper node. You’ll need an apify scrapper, we have used this scrapper In the Custom Body field, paste the URL of your target LinkedIn Jobs search query. 2. Data Enrichment: Connect your account API of data providers like Clay, Hunter, Apollo, etc. using HTTP Header Auth in the Get Targeted Personnel and Email Finder nodes. 3. Google Gemini AI: Connect your Google Gemini (or PaLM) API account in the Google Gemini Chat Model node. 4. Google Sheets Setup: Connect your Google Sheets account. Create a spreadsheet and update the Document ID and Sheet Name in the three Google Sheets nodes to match your own. 5. Activate Workflow: Click “Execute workflow” to run the entire lead generation and email-writing process on demand. Connect with us: Website: https://www.intuz.com/n8n-workflow-automation-templates Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Workflow Automation Click here- Get Started. An n8n automation workflow template by Intuz.

By JinPark

🧩 Summary Easily digitize and organize your business cards! This workflow allows you to upload a business card image, automatically extract contact information using Google Gemini’s OCR & vision model, and save the structured data into a Notion database — no manual typing required. Perfect for teams or individuals who want to centralize client contact info in Notion after networking events or meetings. ⚙️ How it works Form Submission Upload a business card image (.jpg, .png, or .jpeg) through an n8n form. Optionally select a category (e.g., Partner, Client, Vendor). AI-Powered OCR (Google Gemini) The uploaded image is sent to Google Gemini Vision for intelligent text recognition and entity extraction. Gemini returns structured text data such as: { "Name": "Jung Hyun Park", "Position": "Head of Development", "Phone": "021231234", "Mobile": "0101231234", "Email": "abc@dc.com", "Company": "TOV", "Address": "6F, Donga Building, 212, Yeoksam-ro, Gangnam-gu, Seoul", "Website": "www.tov.com" } JSON Parsing & Cleanup The text response from Gemini is cleaned and parsed into a valid JSON object using a Code node. Save to Notion The parsed data is automatically inserted into your Notion database (Customer Business Cards). Fields such as Name, Email, Phone, Address, and Company are mapped to Notion properties. 🧠 Used Nodes Form Trigger** – Captures uploaded business card and category input Google Gemini (Vision)** – Extracts contact details from the image Code** – Parses Gemini’s output into structured JSON Notion** – Saves extracted contact info to your Notion database 📦 Integrations | Service | Purpose | Node Type | |----------|----------|-----------| | Google Gemini (PaLM) | Image-to-text extraction (OCR + structured entity parsing) | @n8n/n8n-nodes-langchain.googleGemini | | Notion | Contact data storage | n8n-nodes-base.notion | 🧰 Requirements A connected Google Gemini (PaLM) API credential A Notion integration with edit access to your database 🚀 Example Use Cases Digitize stacks of collected business cards after a conference Auto-save new partner contacts to your CRM database in Notion Build a searchable Notion-based contact directory Combine with Notion filters or rollups to manage client relationships 💡 Tips You can easily extend this workflow by adding an email notification node to confirm successful uploads. For multilingual cards, Gemini Vision handles mixed-language text recognition well. Adjust Gemini model (gemini-1.5-flash or gemini-1.5-pro) based on your accuracy vs. speed needs. 🧾 Template Metadata | Field | Value | |-------|--------| | Category | AI + Notion + OCR | | Difficulty | Beginner–Intermediate | | Trigger Type | Form Submission | | Use Case | Automate business card digitization | | Works with | Google Gemini, Notion |. An n8n automation workflow template by JinPark.

By rayane

Error Handler: WhatsApp Alert & Gmail Report for Failed Workflows 🎯 What This Template Does / How it Works This template provides a robust, two-step system for handling critical errors in your n8n workflows. It ensures that no workflow failure goes unnoticed, immediately notifying your team via a fast, urgent channel and providing a detailed record via a formal channel. Instant Trigger & Data Capture: The Error Trigger automatically captures all necessary metadata when an assigned workflow fails, including the error message and ID. Contact Configuration: The Set node centralizes and prepares recipient contact information (email and phone number) from the error data. Rapid Response: An urgent notification is sent via WhatsApp for immediate team awareness. Traceability & Record-Keeping: A short Wait node introduces a delay to prevent notification spam. Following the pause, a comprehensive report is sent via Gmail, ensuring a detailed record of the incident is archived. This design guarantees high-priority alerts are handled rapidly, while still maintaining essential documentation. Who’s It For This template is ideal for Ops Teams, Developers, and Automation Engineers who rely on mission-critical n8n workflows (e.g., payment processing, lead capture, data synchronization). If a failure requires immediate human intervention, this system is essential. How to Set Up Setting up this robust error handler is quick and essential for workflow stability: Configure Credentials: Ensure you have the necessary credentials added to your n8n instance for: WhatsApp Business API (for the Send message node). Gmail (for the Send Email node). Define Recipients: In the set_recipient_EMAIL/NUMBER node, replace the placeholder values with the actual email address and phone number of your incident team. Activate the Listener: Open the settings of the primary workflow you wish to monitor.Go to settings ,navigate to the Error Workflow field and select the name of this template (the Error Handler). Save Changes: Save both this Error Handler workflow and the primary workflow. Done! Any failure in the primary workflow will now automatically trigger this alert system. Requirements Gmail Account (Configured as a resource). WhatsApp Business API Access (Configured as a resource and a pre-approved template available). An n8n automation workflow template by rayane.

By Basil Irfan

WhatsApp RAG Agent (Text + Voice) with Weekly Google Drive Sync One-line summary : Answers WhatsApp in under 100 words, understands voice notes, and retrieves trusted answers from your Google Drive docs (RAG) kept fresh weekly. What this template does Reply to WhatsApp messages* in a polite, human tone with *≤100 words**. Understands text and voice notes**: auto-downloads audio and transcribes to text. Retrieves answers from your knowledge base (RAG)**: Google Drive docs → chunk → embed → store in Supabase → rerank with Cohere. Keeps short-term memory** across the conversation to avoid repetition. Weekly doc sync** from a selected Google Drive folder so non-technical staff can update content without touching n8n. Why it matters Zero busywork:** Update a Google Doc; the bot learns it on the next sync. Trustworthy answers:* Responses come from *your** vetted docs, not random web text. Voice-first friendly:** Handles the WhatsApp reality of “send a voice note.” Safer by design:** Guardrails—no pricing unless in KB, no pushy sales, no medical advice. Triggers WhatsApp Trigger:** Receives incoming messages (text or audio). Google Drive Trigger (weekly):** Detects new/updated files in the chosen folder for ingestion. App credentials required WhatsApp Business Cloud** (App ID, Token, Phone Number ID) OpenAI** (Chat + Embeddings) Cohere** (Rerank) Supabase** (SUPABASE_URL, ANON_KEY) Google Drive** (OAuth2) + target Folder ID Suggested environment variables WHATSAPP_APP_ID= WHATSAPP_TOKEN= WHATSAPP_PHONE_NUMBER_ID= OPENAI_API_KEY= COHERE_API_KEY= SUPABASE_URL= SUPABASE_ANON_KEY= GDRIVE_FOLDER_ID= RAG_TABLE_NAME="documents" # table to store vectors/metadata MAX_ANSWER_WORDS=100 # guardrail for concise replies Architecture overview Answer-time lane (RAG Tool):** Receive WhatsApp message → 2) Transcribe audio if present → 3) Maintain short-term memory → 4) Retrieve from Supabase vectors (topK) → 5) Rerank with Cohere → 6) Compose ≤100-word reply with sources → 7) Send on WhatsApp. Ingest lane (Weekly Sync):** A) Detect Drive file updates → B) Download & convert (Docs → text/plain) → C) Chunk (size/overlap) → D) Embed with OpenAI → E) Upsert to Supabase with metadata & hashes. How it works (node rundown) | # | Node | Key Inputs | Key Outputs | | -- | ------------------------------------------- | ------------------------------- | --------------------------------- | | 1 | WhatsApp Trigger | Incoming message | Raw WhatsApp payload | | 2 | Switch (Attachment presence/type) | Payload | Route: Text or Audio | | 3 | HTTP Request (Audio path) | attachments[0].data_url | Audio file | | 4 | OpenAI – Translate/ASR | Audio file | Transcribed text | | 5 | Merge | Text path + Audio path | Unified text message | | 6 | Simple Memory | Recent turns | Short-term context | | 7 | OpenAI Chat Model | Prompt + message + memory | Draft answer (tool calls allowed) | | 8 | Supabase Vector Tool (retrieve-as-tool) | Query text, topK=10 | Candidate KB passages | | 9 | Cohere Reranker | Candidates | Re-ranked context | | 10 | Send WhatsApp Message | to, body | Reply sent | | 11 | Google Drive Trigger (weekly) | Folder ID, fileUpdated | Changed files | | 12 | Set (File Id) | id from trigger | File ref | | 13 | Google Drive – Download File | Id (Docs→txt) | Raw text | | 14 | Character Text Splitter | chunkSize=2000, overlap=300 | Chunks | | 15 | Default Data Loader | Binary→Document | Clean docs | | 16 | OpenAI Embeddings (ingest) | Chunks | Vectors | | 17 | Supabase Vector Store (insert) | Table: documents | Upserted KB | Notes The KB Tool is the combo of steps 8–9–7 at answer time (retrieve → rerank → answer). The Ingest lane is steps 11–17 (weekly sync of your Drive folder). Setup (7‑minute sprint) Import the workflow JSON. Connect credentials: WhatsApp, OpenAI, Cohere, Supabase, Google Drive. Google Drive Trigger: paste your Folder ID; keep fileUpdated event. Download File: ensure Google Docs convert to text/plain. Supabase Vector Store (insert): set table name to documents (or your schema). Character Text Splitter: keep chunkSize=2000, overlap=300 (balanced recall/latency). Retrieve-as-tool: set topK=10 and enable reranker. Send WhatsApp Message mapping: Recipient: {{$("WhatsApp Trigger").item.json.messages[0].from}} Body: {{$json.output}} Test: Send a text and a voice note to your WhatsApp number → confirm concise answers. Drop a Google Doc into the watched folder → verify it’s chunked/embedded on the next weekly poll (or run ingest nodes once manually). Prompt, tone & guardrails System prompt:** Be polite, human, and concise (≤ MAX_ANSWER_WORDS). Cite or reference only the KB content; if unknown, say so and offer to escalate. No prices unless present in the KB. No medical advice. Temperature:* start at *0.2** for factual replies. Memory window:** keep a short rolling buffer (e.g., last 4–6 turns). Data model (minimum viable) Table documents (example columns): id (uuid) source_url (text) title (text) chunk (text) embedding (vector/float[] depending on extension) chunk_hash (text) updated_at (timestamp) Indexes Unique index on chunk_hash to dedupe Index on updated_at for syncs Observability & ops Log question, selected chunk ids/hashes, and final response to a DB/Sheet for QA. Add a low-confidence route (score threshold) → Slack/Telegram escalation to a human. Track latency and token usage to tune topK and chunk sizes. Customization Latency vs quality:** try topK=6–8 and chunkSize=1200 for speed. Languages:** ASR node can be swapped for native multilingual output. Escalation:** add channel handoff on low confidence or no KB hits. Sync cadence:* change Drive Trigger to *daily** if content updates frequently. Safety & compliance No medical advice.** If uncertain or clinical, ask to schedule a consult or refer to the right department. PII:** Don’t log full phone numbers in plaintext analytics; hash where possible. Prices & rates:** Only answer if present in the KB; otherwise hand off to front desk. Troubleshooting No reply sent:* Ensure *Send message** node reads {{$json.output}} (Agent’s response property). Audio path failing:** Confirm attachments[0].data_url exists and HTTP node fetches a valid file. KB not updating:** Manually execute the ingest lane; check rows in Supabase. Irrelevant answers:* Lower temperature to *0.2, increase overlap to **400, and verify Drive docs are clean and structured. Categories & tags Categories:** AI, Customer Support, Healthcare Ops, RAG, WhatsApp Tags:** WhatsApp, RAG, Google Drive, Supabase, OpenAI, Cohere, Voice Notes Pricing (rough, BYO keys) n8n:** self-host free; n8n.cloud billed by plan. OpenAI, Cohere:** usage-based by tokens/calls. Supabase:** free tier + usage; vector storage billed by size. WhatsApp Cloud:** Meta pricing per conversation. Nodes used in workflow WhatsApp Trigger, Switch, HTTP Request, OpenAI (ASR + Chat + Embeddings), Merge, Simple Memory, Supabase Vector Tool (retrieve), Cohere Reranker, Google Drive Trigger, Set, Google Drive – Download, Character Text Splitter, Default Data Loader. An n8n automation workflow template by Basil Irfan.

By András Farkas

UPDATES: 2025-12-03 fix JS code in calculate hourly sum node E.ON W1000 → n8n → Home Assistant (Spook) “Integration” This workflow processes emails from the E.ON portal containing 15-minute +A -A (import/export) data and daily 1.8.0 2.8.0 meter readings. It extracts the required columns from the attached XLSX file, groups the 15-minute values by hour, then: updates the Spook/Recorder statistics under the IDs sensor.grid_energy_import and sensor.grid_energy_export, and sets the current meter readings for the entities input_number.grid_import_meter and input_number.grid_export_meter. > You may need to modify the workflow if there are changes in how E.ON sends scheduled exports. If the exported data format changes, please report it on Github! Requirements n8n (cloud or self-hosted) HACS addon available here: Rbillon59/home-assistant-addons Official n8n Docker Compose template Simplified n8n Docker Compose template available on Github (For Gmail) Gmail API authentication (OAuth2) read-only email access to the account receiving the messages Setup guide available here (For IMAP) IMAP provider credentials Home Assistant access via Long-Lived Access Token or API key Setup guide available here Spook integration Documentation and installation guide available here E.ON Portal Setup Create a scheduled export on the E.ON portal with the following parameters: Under the Remote Meter Reading menu, click on the + new scheduled export setting button. Specify POD identifier(s): choose one of the PODs you want to query. Specify meter variables: select the following: +A Active Power Consumption -A Active Power Feed-In DP_1-1:1.8.0*0 Active Power Consumption Daily Reading DP_1-1:2.8.0*0 Active Power Feed-In Daily Reading Export sending frequency: daily Days of historical data to include: recommended 7 days to backfill missed data. Email subject: by default, use [EON-W1000]. If processing multiple PODs with the workflow, give each a unique identifier. Home Assistant Preparation Create the following input_number entities in configuration.yaml or via Helpers: input_number: grid_import_meter: name: grid_import_meter mode: box initial: 0 min: 0 max: 9999999999 step: 0.001 unit_of_measurement: kWh grid_export_meter: name: grid_export_meter mode: box initial: 0 min: 0 max: 9999999999 step: 0.001 unit_of_measurement: kWh > If you name the entities differently, make sure to reflect these changes in the workflow. Create the following template_sensor entities in configuration.yaml or via Helpers: input_number: grid_import_meter: name: grid_import_meter mode: box initial: 0 min: 0 max: 9999999999 step: 0.001 unit_of_measurement: kWh grid_export_meter: name: grid_export_meter mode: box initial: 0 min: 0 max: 9999999999 step: 0.001 unit_of_measurement: kWh >If you name the entities differently, make sure to reflect these changes in the workflow. create the following template_sensor entities in config.yaml or via Helpers: template: sensor: name: "grid_energy_import" state: "{{ states('input_number.grid_import_meter') | float(0) }}" unit_of_measurement: "kWh" device_class: energy state_class: total_increasing name: "grid_energy_export" state: "{{ states('input_number.grid_export_meter') | float(0) }}" unit_of_measurement: "kWh" device_class: energy state_class: total_increasing > If you name the entities differently, make sure to reflect these changes in the workflow. n8n import and authentication importing the workflow In n8n → Workflows → Import from File/Clipboard → paste the JSON. Select the downloaded JSON and paste it into a new workflow using Ctrl+V. Set up n8n Credentials The credentials must be configured in the Home Assistant and Gmail nodes. The setup process is described in the Requirements section. An n8n automation workflow template by András Farkas.

By Meak

Google Sheets → Personalized Email Reply Automation with OpenAI + Gmail Most teams reply to inbound leads manually — copying info from a CRM, drafting a response, and hitting send. This workflow automates lead intake, draft generation, and sending — directly from a Google Sheet trigger. Benefits Pull new leads and context automatically from Google Sheets Generate professional HTML replies with OpenAI Personalize each response using lead name, intent, and message Send replies via Gmail with your real display name + signature Save hours per week on repetitive inbox work How It Works Manual trigger starts the workflow Reads rows from Google Sheets (Email, First Name, Intent, Message) Fetches Gmail sendAs to capture display name for signature Calls OpenAI model (via n8n LangChain node) to generate HTML reply Sends email via Gmail node with subject = "Re:" + Intent and HTML body Continues for each row, even if one fails (alwaysOutputData enabled) Who Is This For Founders handling inbound leads manually SDRs and sales teams replying to prospects Agencies wanting consistent, on-brand email responses Setup Connect Google Sheets (replace with your Document ID + Sheet Name) Connect Gmail (OAuth2) and enable sendAs retrieval Add OpenAI API credentials (choose GPT-4/5 or Claude model) Set Gmail node emailType = html for proper formatting Test with a few leads before running in bulk ROI & Monetization Save 3–5 hours per week on manual email drafting Use as a client-facing “Inbox Automation” service Bundle with CRM sync or Zapier handoff for $500–$2k/month retainers Strategy Insights In the full walkthrough, I show how to: Build this system step by step in n8n Craft prompts that output clean HTML with signature Handle edge cases (missing fields, null intents) gracefully Turn this into a recurring email automation offer Check Out My Channel For more advanced AI automation systems that generate real business results, check out my YouTube channel where I share the exact strategies I use to build automation agencies, sell high-value services, and scale to $20k+ monthly revenue. An n8n automation workflow template by Meak.

By Anshul Chauhan

Deploy a Multi-Tool AI Assistant on WhatsApp with Google Gemini Deploy a true AI assistant on WhatsApp. This n8n workflow uses a sophisticated hierarchical agent structure to not only handle conversations but also manage your emails and calendar directly from your chat, all powered by Google Gemini. Key Features Powered by Google Gemini:** Utilizes the advanced capabilities of Google's Gemini models for understanding complex commands and generating natural, human-like responses. Intelligent Task Delegation (Hierarchical Agents):* Features a central *Personal Agent** that understands the user's intent and intelligently delegates tasks to specialized sub-agents for email, calendar, or general chat. Full Email & Calendar Management:** Connects directly to your Google Workspace to send emails, create drafts, apply labels, create/update/delete calendar events, check your availability, and more. Context-Aware Conversations:** Employs memory at multiple levels, allowing the assistant to remember the context of your requests for a coherent and intuitive user experience. Seamless WhatsApp Integration:** Connects directly with the WhatsApp Business API to send and receive messages, engaging users on one of the world's most popular messaging platforms. Easy to Deploy & Customize:** Get your assistant running with minimal configuration and easily extend its capabilities by adding new tools or modifying the prompts of the existing agents. How It Works The workflow uses an advanced agent-based model to process incoming messages: The Whatsapp Trigger node listens for and receives new messages sent to your WhatsApp Business number. The message is passed to the main Manager Agent. The Personal Agent analyzes the message to understand the user's intent (e.g., "send an email," "check my schedule," or just "hello"). Based on the intent, it routes the task to the appropriate sub-agent: the Email Tool, the Calendar Tool, or the general Chatbot Model. The selected sub-agent executes the task using its own dedicated tools (e.g., the Email Tool uses Gmail nodes to send a message). The result or response from the sub-agent is passed back to the Send message (WhatsApp) node, which delivers the reply to the user. Prerequisites An active n8n instance. A Meta Business Account and a configured Meta App with the "WhatsApp Business" product added. A Google Gemini API Key. A Google Account with pre-configured OAuth2 credentials in n8n for Gmail and Google Calendar. Step-by-Step Setup Guide 1. Configure WhatsApp Credentials: In your n8n instance, add new "WhatsApp Business" credentials. You will need a Permanent Access Token and a Phone Number ID from your Meta App's "WhatsApp > API Setup" dashboard. 2. Set Up the WhatsApp Trigger: Open the Whatsapp Trigger node. In the "Webhook URL" section, copy the Test URL. Go to your Meta App's dashboard under "WhatsApp > Configuration". Click "Edit" in the Webhooks section. Paste the n8n Test URL into the Callback URL field. Create and enter a Verify token (a simple password of your choice). Enter this same token in the Whatsapp Trigger node in n8n. Subscribe to the messages webhook event. Once verified, copy the Production URL from n8n and paste it into the same Callback URL field in the Meta dashboard. 3. Configure the Google Gemini Nodes: You must add your Google Gemini API Key to the credentials for all the Google Gemini Chat Model nodes. This includes the one in the Chatbot Model, Email Tool, and Calendar Tool. 4. Configure the Google Tools (Email & Calendar): Email Tool:* Open the group of nodes labeled *Email Tool**. For every Gmail node (Send Email, Create Draft, Get Labels, etc.), select your pre-configured Google OAuth2 credential. Calendar Tool:* Open the group of nodes labeled *Calendar Tool**. For every Google Calendar node (Create Event, Get all event, etc.), select your pre-configured Google OAuth2 credential. 5. Activate and Test: Save and activate the workflow. Send a message to your configured WhatsApp Business number. An n8n automation workflow template by Anshul Chauhan.

By Sabrina Ramonov 🍄

Description Fully automated pipeline where you send an email to yourself with a rough idea (subject contains “thread”), n8n’s Gmail trigger picks it up, OpenAI ChatGPT rewrites/apply a viral-thread template, and Blotato posts the long-form thread to X/Twitter, Bluesky, and Meta Threads (optionally schedule or include images/videos). Template is easily extensible to other social platforms. Who Is This For? Digital creators, content marketers, social media managers, agencies, entrepreneurs, and influencers who want fast, automated long-form thread posting. 📄 Documentation Full Step-by-Step Tutorial How It Works 1. Trigger: Gmail Connect your Gmail account. n8n monitors emails sent from you and filters for subjects containing the word “thread”. 2. AI Thread Writer: OpenAI ChatGPT Connect your OpenAI account. Prompt ChatGPT to clean up your draft and format a long-form viral thread. 3. Publish to Social Media via Blotato Connect your Blotato account and choose social accounts (X/Twitter, Threads, Bluesky). Schedule or post immediately. Supports optional image/video URLs via a mediaUrls array (publicly accessible URLs). Example email to trigger the workflow: Email Subject: thread Email Body: I'm obsessed with voice AI apps. Super Whisper is my current favorite because it runs locally and keeps my voice data private. I talk to it instead of typing. Way faster. Setup & Required Accounts Gmail account (used as trigger) n8n Gmail OAuth doc: https://docs.n8n.io/integrations/builtin/credentials/google/oauth-single-service OpenAI Platform account (access to ChatGPT) Blotato account: https://blotato.com Generate Blotato API Key: Settings > API > Generate API Key (paid feature only) Sign in to Blotato and create an API Key (required for posting) n8n: Ensure "Verified Community Nodes" enabled in your n8n Admin Panel Install the "Blotato" community node and create Blotato credentials Optional: Media & Style Tweaks Attach images/videos: insert publicly accessible URLs into the mediaUrls array (advanced). To emulate a specific tone/structure, provide ChatGPT examples of your favorite viral threads or replace the example viral-thread prompt with your preferred example. Voice-to-text tip: record ideas (e.g., Superwhispr) and send the transcript by email — ChatGPT will clean it up. Tips & Tricks During testing, use “Scheduled Time” in Blotato instead of immediate posting to preview before going live. Start with a single social platform while testing. If your script is long or includes media, processing may take longer. Many users prefer speaking their ideas (voice notes) then letting AI edit — faster than typing. Troubleshooting Check your Blotato API Dashboard to inspect each request, response, and error. Confirm API key validity, n8n node credentials, and that emails sent have subject containing “thread”. Need Help? In the Blotato web app, click the orange support button in the bottom right to access Blotato support. An n8n automation workflow template by Sabrina Ramonov 🍄.

By Rahi Uppal

LinkedIn to Apollo.io Lead Enrichment System with Google Sheets Automatically capture company and store details from LinkedIn posts, enrich them with domain names and key decision-maker (KDM) data from Apollo.io, and store everything neatly in Google Sheets. This workflow turns LinkedIn post data into a complete, structured lead database — fully automated from detection to enrichment. 🧾 Summary This workflow reads LinkedIn post data (in JSON format) received via a webhook, extracts company and location information using an AI agent, and progressively enriches the data in three stages: Find Company Domain using Apollo.io Fetch Key Decision Makers (KDMs) using the company domain Find Corporate Emails for those KDMs All results are automatically updated in Google Sheets, ensuring your lead list remains fresh, structured, and actionable. ⚙️ Prerequisites Before running the workflow, make sure you have: An Apollo.io API Key with company and people search access A connected Google Sheets account (OAuth2) A Webhook URL or LinkedIn scraper that feeds JSON-formatted post data (Optional) An OpenAI / AI Agent node to extract company names and store locations from post text 🧩 Example Input (Webhook JSON) Each LinkedIn post is received as a JSON object containing key clues: { "index": 1, "text": "Excited to announce the opening of our new KFC store at Sky City Mall, Borivali East 🎉🍗\n\nLooking forward to welcoming you all to experience the Finger Lickin’ Good taste at our newest location!\n\n#KFCIndia #NewStoreOpening #Borivali #SkyCityMall #Sapphirefoods", "CompanyName": "MockCompany", "NewStoreLocation": "optional", "PersonPosted": "https://linkedin.com/in/mockperson", "PostImage": null, "PostLink": "https://www.linkedin.com/search/results/all/?keywords=%23kfcindia&origin=HASH_TAG_FROM_FEED", "extracted_at": "2025-09-08T12:05:40.044101" } 🧠 Workflow Overview This workflow runs in three main stages, moving from LinkedIn data → company domain → people → emails. Stage 1: Company Name to Company Domain 🌐 Goal: Convert each company name into its website domain using Apollo.io. Nodes & Flow Schedule Trigger** — Runs automatically (e.g., once a week) to check your Google Sheet for companies missing a domain. IF Node (Check for Missing Domain)** — Filters only companies without a website. Loop Over Items** — Iterates through each company record. HTTP Request – Find Domain** — Calls the Apollo.io Company API to find the company’s domain (e.g., kfc.com). Update Row in Google Sheets** — Writes the found domain back into the corresponding company row. Wait Node – Delay Between API Calls** — Adds a small pause to avoid hitting rate limits. Stage 2: Domain to Top 10 KDMs 👥 Goal: Fetch key decision-makers (KDMs) from each company using Apollo.io. Nodes & Flow Schedule Trigger** — Runs on a weekly cadence to check for companies with a domain but no KDMs. Get Rows from Google Sheets** — Pulls company records ready for enrichment. IF Node (Check for Missing KDMs)** — Ensures only companies without people data are processed. Loop Over Items** — Processes one company at a time. HTTP Request – Find KDMs* — Searches Apollo.io People API for top roles such as *Founder, CEO, Head of Retail, etc. Update Row in Google Sheets** — Saves the top 10 names and their LinkedIn profiles into your sheet. Wait Node** — Adds a delay to manage rate limits safely. Stage 3: KDM Profile to Email Enricher 📧 Goal: Find and store verified corporate email addresses for each KDM. Nodes & Flow Schedule Trigger** — Weekly automation trigger. Get Rows from Google Sheets** — Pulls KDMs that have LinkedIn profiles but no email yet. IF Node (Check for Missing Emails)** — Ensures only valid records are processed. Code Node – Prepare Data** — Organizes LinkedIn profile and domain information. HTTP Request – Find Email** — Queries Apollo.io’s email enrichment endpoint using the LinkedIn URL and domain. Code Node – Format Response** — Cleans and formats the email result. Wait Node** — Adds delay to avoid request bursts. Update Row in Google Sheets** — Writes the verified email address back to the corresponding KDM entry and marks it as “Updated – email search.” 🎉 🧰 Setup Instructions 1. Connect APIs & Credentials Add your Apollo.io API Key under HTTP Request credentials. Connect your Google Sheets account (OAuth2). 2. Customize Sheet Structure Add columns for: CompanyName, Domain, KDMs, LinkedInProfile, Email, Status 3. Set Schedule Frequency Each Schedule Trigger can be configured separately (e.g., Stage 1 every Monday, Stage 2 every Wednesday). 4. Optional: AI Extraction Node Use an AI model (like OpenAI or Gemini) to extract company name and location from LinkedIn post text before enrichment. 🧰 Custom Node Names (Recommended for Clarity) | Node Type | Recommended Name | Description | |------------|------------------|-------------| | HTTP Request (Company) | Find Company Domain (Apollo.io) | Searches for the company’s official domain | | HTTP Request (People) | Find Key Decision Makers (Apollo.io) | Retrieves top company contacts | | HTTP Request (Emails) | Find Corporate Emails (Apollo.io) | Gets verified email addresses for each contact | | Wait Node | API Delay (Rate Limit Buffer) | Adds delay to avoid hitting API rate limits | | Code Node | Prepare KDM Data | Organizes input data for API calls | ⚙️ Customization Tips Multiple Campaigns:** Duplicate the workflow for different industries or store categories, updating parameters as needed. Batch Size:** Adjust API request limits (e.g., 100 per batch) based on your Apollo.io plan. Filtering:** Add IF conditions to skip records already marked as “Completed.” Dashboards:* Build visual analytics directly in Google Sheets or connect to *Looker Studio**. Enrichment:* Combine with CRM systems (like *HubSpot* or *Close**) using company domain or lead email as the linking key. 🔐 Security and Publishing Notes 🔒 Never hardcode API keys in workflow exports. Use n8n credentials or environment variables instead. 🚫 Replace sensitive values (like API keys or Sheet IDs) with placeholders before sharing. 🔐 Keep your Google Sheet private unless intentionally shared. 🧩 Troubleshooting No Data in Sheets:** Check API response for data[] and verify Split Out configuration. Duplicate Rows:** Ensure the “Matching Column” in Google Sheets is correctly set (e.g., CompanyName or LinkedInProfile). Rate Limits:* Add *Wait Nodes** or reduce batch size. Mapping Errors:** Confirm Google Sheet headers exactly match node field mappings. Timezone Adjustments:** Apollo.io timestamps are in UTC — convert to local time if needed. 🎯 Example Use Case Every week, this workflow scans new LinkedIn store-opening posts. It extracts company names (like KFC India), finds their domains and top executives through Apollo.io, retrieves their emails, and logs everything in a Google Sheet — ready for your sales team to reach out. Tags: LinkedIn Apollo Automation LeadGeneration GoogleSheets MarketingOps DataEnrichment. An n8n automation workflow template by Rahi Uppal.

By Kai S. Huxmann

Objective This template helps you create clean, structured, and visually understandable workflows that are easy to read, present to clients, and collaborate on with teams. Whether you're onboarding a client, building reusable automations, or working across a team, this template gives you a solid foundation for workflow visual design and communication. ✨ What’s inside? ✅ Visual layout structure suggestion ✅ Clear segmentation into basic functional parts ✅ Color Coding suggestion to define meaning of colors 🎨 Color-coded nodes (with a built-in legend): 🟩 Green → Operational and stable 🟨 Yellow → Work in progress 🟥 Red → Failing / error 🟧 Orange → Needs review or improvement 🟦 Blue → User input required ⬛ Dark grey → Deprecated or paused 👥 Who is this for? This template is ideal for: 🔧 Freelancers or agencies delivering workflows to clients 👥 Teams working together on large-scale automations 🧱 Anyone creating reusable templates or internal standards 🧑‍🎓 Beginners who want to learn clean visual patterns supporting easy to maintain code base 📸 Why use this? > “A workflow should explain itself visually – this template helps it do just that.” Better team collaboration Easier onboarding of new developers Faster understanding** for clients, even non-technical ones Reduces maintenance time in the long run 📌 How to use Clone this template and start from it when creating new workflows Keep color conventions consistent (especially in early project stages) Use it to build a visual standard across your team or organization 🚧 Reminder This is a non-functional template — it contains structure, patterns, and documentation examples only. Replace the example nodes with your own logic. An n8n automation workflow template by Kai S. Huxmann.

By Fahmi Fahreza

Quick overview This workflow intelligently qualifies new Jotform leads and sends the perfect welcome email every time. It detects whether a lead is using a business or personal email address and tailors the outreach accordingly—either with deep company research for B2B leads or a warm, direct welcome for B2C leads. How it works The workflow starts automatically whenever a new lead submission is received from your configured Jotform form. An IF node checks whether the submitted email belongs to a work domain or a personal provider such as Gmail or Yahoo. For work emails, Perplexity AI researches the lead's company, and OpenAI drafts a deeply personalized email referencing specific company details. For personal emails, the research step is skipped and OpenAI drafts a warm, friendly welcome email using only the available lead information. The appropriate context-aware email is sent to the new lead automatically via Gmail based on which path was taken. Setup Connect your Jotform credentials and select your lead capture form. Ensure the form contains fields named exactly name and email for the workflow to map correctly. Connect your Perplexity AI, OpenAI, and Gmail credentials in the n8n Credential Manager before activating the workflow. Activate the workflow — it will now trigger automatically on every new Jotform submission and route each lead through the appropriate email path. Requirements An n8n account. A Jotform account. A Perplexity AI account with API access. An OpenAI account with API access. A Gmail account. Customization Filter Logic: Add more personal email domains (e.g., icloud.com) to the list in the Check if Email is Work or Personal node to improve filtering. Prompts: Customize the prompts in both the AI Agent nodes to match your brand’s voice and tone. Additional info Published by Fahmi Fahreza, Indonesia’s first official n8n Brand Ambassador and founder of WithMi Automation, built from real client implementations, not tutorials. → Let us build it for you: withmiautomation.com → Learn to build it yourself: academy.withmiautomation.com → Bring Fahmi to your team (training, workshop, talkshow): fahmiiireza.com. An n8n automation workflow template by Fahmi Fahreza.

By Paul Roussel

Who's it for This workflow is perfect for app developers, SaaS founders, and mobile growth teams who need constant UGC-style video ads without hiring creators or agencies. If you're spending $500+ per creator and waiting weeks for videos, this automates the entire process for $2-5 per video in 8 minutes. How it works Upload an app screen recording, and this n8n workflow handles everything: Gemini AI analyzes the recording and generates a UGC ad structure (hook, problem, solution, CTA with word limits). It describes the ideal actor, emotional journey, and visual style. Sora 2 then generates a hyper-realistic AI actor delivering the script naturally. VideoBGRemover removes the actor's background and composites them picture-in-picture over your screen recording with audio mixing. The result is a scroll-stopping UGC ad ready for TikTok, Instagram, and Facebook. Set up steps Setup takes ~10 minutes and requires 3 API keys: Get your Gemini API key from Google AI Studio Get your FAL AI key for Sora 2 access Get your VideoBGRemover API key at https://videobgremover.com/n8n Add all three keys to n8n environment variables Connect Google Drive for output storage Test with the included sample screen recording The workflow includes 7 detailed sticky notes explaining each section (Gemini analysis, Sora generation, VideoBGRemover composition, output handling). Requirements Google Gemini API key (for video analysis) FAL AI API key (for Sora 2 access) VideoBGRemover API key Google Drive account (for final video storage) App screen recordings in vertical format (9:16 recommended, 4-12 seconds) How to customize Modify the Gemini prompt to adjust ad tone, script word limits, or actor descriptions. Change composition settings in the VideoBGRemover node (position, size, audio mix). Add your own post-processing nodes for branding, captions, or multi-platform exports. An n8n automation workflow template by Paul Roussel.

By Paul Roussel

How it works • Upload foreground video (AI actors, product demos, webcam footage) • Provide custom background video URL • API removes video background with videobgremover.com • Composites foreground onto background • Downloads and uploads to Google Drive • Returns shareable link Set up steps • Get API key at https://videobgremover.com/n8n (2 min) • Import workflow (1 min) • Add API key to n8n variables as VIDEOBGREMOVER_KEY (1 min) • Connect Google Drive (2 min) • Test with manual trigger (1 min) • Total: 7 minutes What you'll need • VideoBGRemover API key ($0.50-$2.00 per minute) • Google Drive account • Publicly accessible video URLs • n8n instance Perfect for • AI UGC ad creators using HeyGen, Synthesia, Arcads • Marketing agencies creating ad variations • E-commerce product demos on custom backgrounds • Social media content with branded scenes • Video editors removing backgrounds at scale Key features • Video composition with custom templates • Audio mixing with adjustable volumes • 20-second polling for status • Google Drive integration • Webhook automation support • 3-5 minute processing time per minutes of input video. An n8n automation workflow template by Paul Roussel.

By Roshan Ramani

Duplicate Submission Detection & Auto Response for Jotform Who's it for Form managers, SaaS platforms, event organizers, recruitment teams, and any organization using Jotform who need automatic duplicate prevention with intelligent, personalized email responses without manual intervention. What it does This workflow automatically detects duplicate form submissions by email address, prevents duplicate entries in your database, and triggers intelligent email responses. When a new submission arrives, the system checks against all previous submissions. If a match is found, it deletes the duplicate and sends a friendly notification. If it's a new submission, it sends a professional welcome confirmation. The entire process happens in seconds with no manual work required. AI-generated emails adapt to your form type and industry, making responses feel personalized and relevant. 👉 Get the JotForm from here How it works Step-by-step: Form submission triggers the workflow System extracts email and contact information Fetches all previous submissions from Jotform Filters for active submissions matching the email Counts matching submissions to determine if duplicate If duplicate: Deletes the submission, generates rejection email, sends to submitter If new: Generates welcome confirmation email, sends to submitter Requirements Jotform form and account Jotform API Key n8n instance (self-hosted or cloud) Google Gemini API (for email generation) Gmail account with OAuth2 setup Basic form field mapping knowledge How to set up Complete setup instructions are included in the workflow sticky notes: Get your Jotform API Key from Account Settings Enable Google Gemini API in Google Cloud Console Configure Gmail OAuth2 authentication Add all credentials to n8n Import workflow and map your form fields Test with a sample submission Activate and deploy Detailed step-by-step guide is in the workflow documentation. How to customize the workflow Personalize emails for your industry: Edit the AI prompts in both "Generate Welcome Email" and "Compose Rejection Email" nodes to match your business type, tone, and specific requirements. The AI will adapt responses based on your instructions. Map your form fields: Update field IDs in filtering nodes to match your actual Jotform structure. Different forms may have email in different field positions. Add admin notifications: Duplicate the email nodes to send alerts to your team whenever duplicates are detected. Modify approval workflow: Change next steps timeline, add additional verification requirements, or customize follow-up sequences based on your business process. Template features Instant duplicate detection by email Automatic duplicate removal AI-powered, personalized email responses Token-efficient prompts for cost savings Professional HTML email formatting Mobile-responsive designs Works with any form type or industry Fully customizable for your use case Complete setup documentation included. An n8n automation workflow template by Roshan Ramani.

By Yves Tkaczyk

Automated image processing for e-commerce product catalog Use cases Monitor a Google Drive folder, process each image based on the prompt defined in Workflow Configuration and save the new image to the specified output Google Drive folder. Maintain a processing log in Google Sheets. 👍 This use case can be extended to any scenario requiring batch image processing, for example, unifying the look and feel of team photos on a company website. How it works Trigger: Watches a Google Drive folder for new or updated files. Downloads the image, processes it using Google Gemini (Nano Banana), and uploads the new image to the specified output folder. How to use Google Drive and Google Sheets nodes: Create Google credentials with access to Google Drive and Google Sheets. Read more about Google Credentials. Update all Google Drive and Google Sheets nodes (6 nodes total) to use these credentials Gemini AI node: Create Google Gemini(PaLM) Api credentials. Read more about Google Gemini(PaLM) credentials. Update the Edit Image node to use the Gemini Api credentials. Create a Google Sheets spreadsheet following the steps in Google Sheets Configuration (see right ➡️). Ensure the spreadsheet can be accessed as Editor by the account used for the Google Credentials. Create input and output directories in Google Drive. Ensure these directories are accessible by the account used for the credentials. Update the File Created, File Updated and Workflow Configuration node following the steps in the green Notes (see right ➡️). Requirements Google account with Google API access Google AI Studio account with ability to create a Google Gemini API key. Basic n8n knowledge: understanding of triggers, expressions, and credential management Who’s it for Anyone wanting to batch process images for product catalog. Other use cases are applicable. Please reach out reach out if you need help customizing this workflow. 🔒 Security All credentials are stored securely using n8n's credential system. The only potentially sensitive information stored in the workflow is the Google Drive folder and Sheet IDs. These should be secured according to your organization’s needs. Need Help? Reach out on LinkedIn or Ask in the Forum!. An n8n automation workflow template by Yves Tkaczyk.

By Anirudh Aeran

This workflow is a powerful reputation management tool designed to proactively filter customer reviews. It helps you encourage positive reviews on Google while capturing negative feedback privately before it impacts your public rating. By using an incentive, it maximizes the number of customers who enter this review funnel, giving you control over your online reputation. Who’s it for? This template is essential for any business where Google Reviews are critical: restaurants, clinics, retail stores, local services, and more. If you want to improve your Google star rating by systematically encouraging happy customers to post public reviews and addressing unhappy customers privately, this is the perfect solution. How it works / What it does The main job of this workflow is to send customers to a special review landing page. On this page, only reviews of 4 stars or more are directed to your Google Review page, while lower-rated feedback is captured in a private form. Trigger: A customer scans a QR code (e.g., in your store) and sends a message to your Telegram bot. Incentivize: The bot checks if the user is new. If so, it sends them a small discount or offer as a thank-you for their business and to encourage them to provide feedback. Send to Filter Page: After a short delay, the workflow sends a message with a link to your review filtering webpage. Track & Follow Up: The workflow tracks whether the link has been clicked (updating the status in a Google Sheet). If a user doesn't click the link after 23 hours, an automated reminder is sent to maximize engagement. How to set up Crucial Prerequisite: This workflow sends users to a review-filtering webpage. You must have this webpage already built. The page should have logic to send 4+ star reviewers to Google and capture other feedback internally. code Create a Telegram Bot: Use the BotFather on Telegram to create a bot and get your API token. Google Sheet: Create a Google Sheet with columns like: ID, First Name, Status, Feedback Message, Timestamp. Credentials: Add your Google Sheets API and Telegram Bot API credentials to n8n. Configure Nodes: In all Google Sheets nodes, select your credential and paste your Sheet ID. In all Telegram nodes, select your Telegram credential. In the "Send Review Page Link" and "Send Review Link Reminder" nodes, update the URL to point to your review filtering page. Create a QR Code: Generate a QR code for your bot's link (e.g., https://t.me/YOUR_BOT_USERNAME) and display it for your customers. Activate Workflow: Save and activate the workflow. Requirements A pre-built review filtering webpage. code An active n8n instance. Google Sheets API credentials. A Telegram Bot and its API token. An n8n automation workflow template by Anirudh Aeran.

By Malik Hashir

Purpose & Audience Perfect for marketing teams, agencies, solopreneurs, and e-commerce brands who need fast, professional-quality ad creatives — without hiring designers or using Canva. This workflow automates image generation for Facebook, Instagram, and Pinterest using Google’s Imagen 3.0 (via Gemini API). What It Does Presents a user-friendly form to collect: Business context Offer/message Brand colors Target platform (FB/IG/Pinterest) Desired ad dimensions (7 formats supported) Uses Google Gemini’s Imagen 3.0 model to generate platform-optimized images Delivers each image directly to your Telegram chat with clear captions ✅ Supports 7 ad formats: Facebook Feed (1200×630) Facebook Story (1080×1920) Instagram Feed (1080×1080) Instagram Story & Reel (1080×1920) Pinterest Pin (1000×1500) Pinterest Story (1080×1920) How to Set Up Get a Google Gemini API key at ai.google.dev (enable Imagen API) Create a Telegram bot via @BotFather and note your Bot Token + Chat ID In n8n: Import this workflow Add Google Gemini credentials (use your API key) Add Telegram credentials (use your Bot Token) Replace ={{ $json.telegramChatId }} in Telegram nodes with your actual numeric Chat ID Activate the workflow and share the Form Trigger URL with your team! 💡 Pro Tip: Enhance prompts in Gemini nodes with style keywords (e.g., “minimalist”, “vibrant”, “corporate”) for better results. ✨ 100% free to use — only pay for Google Imagen API usage. Telegram delivery is free forever. An n8n automation workflow template by Malik Hashir.

By Joseph

Transform meeting transcripts into fully customized, AI-powered presentations automatically. This comprehensive 5-workflow automation system analyzes client conversations and generates professional slide decks complete with personalized content and AI-generated illustrations. 🎯 What This Automation Does This end-to-end solution takes a meeting transcript (Google Docs) and client information as input, then automatically: Creates a presentation from your custom template Generates a strategic presentation plan tailored to the client's needs Creates custom illustrations using AI image generation Populates slides with personalized text content Inserts generated images into the appropriate slides Delivers a client-ready presentation Perfect for sales teams, consultants, agencies, and anyone who needs to create customized presentations at scale. 🔧 How It Works The automation is split into 5 interconnected workflows: Workflow 1: Clone Presentation & Database Setup Form trigger captures client name, transcript URL, and submission time Clones your presentation template via Google Slides API Saves presentation details to Google Sheets for tracking Workflow 2: AI Presentation Plan Generation Analyzes meeting transcript to understand client pain points Generates comprehensive presentation structure and content strategy Saves plan to Google Docs for review and tracking Uses company profile (customizable) to match solutions to client needs Workflow 3: AI Illustration Generation AI agent creates image prompts based on presentation plan Generates illustrations using Flux model via OpenRouter (nanobanana) Uploads images to Google Drive for slide insertion Tracks all generated assets in database Workflow 4: Text Content Population AI agent generates final presentation text from the plan Replaces template placeholders with personalized content Uses Object IDs to target specific text elements in slides Updates slides using native n8n Google Slides node Workflow 5: Image Insertion Retrieves image Object IDs from presentation structure Downloads illustrations from Google Drive Converts images for ImgBB hosting (resolves Google Drive URL limitations) Updates slide images via Google Slides API 📋 Prerequisites Required Accounts & API Keys: Google Workspace (Drive, Slides, Docs) OpenAI API (for AI agents) OpenRouter API (for Flux image generation) ImgBB API (free tier available) Gemini API (optional, for additional AI tasks) Setup Requirements: Google Sheets database (template provided in article and inside the workflow) Google Slides presentation template with standard Object IDs Meeting transcript in Google Docs format 🎨 Customization Options This automation is designed to be flexible: Template Flexibility**: Use any slide template structure Company Profile**: Customize the business context for your use case AI Models**: Swap OpenAI/Gemini agents for your preferred LLM Image Generation**: Replace Flux with DALL-E, Midjourney API, or other models Slide Logic**: Extend to dynamically select slides based on content needs 💡 Key Technical Insights Structured Output Handling**: Uses JavaScript for reliable JSON parsing when AI output structure is complex Object ID System**: Template placeholders use unique IDs for precise element targeting Image Hosting Workaround**: ImgBB resolves Google Drive direct URL limitations in API calls HTTP Request Nodes**: Used for API operations not covered by native n8n nodes (copying presentations, image updates) 🔗 Full Documentation For a detailed breakdown of each workflow, configuration steps, and best practices, read the complete guide on this Medium article 🚀 Use Cases Sales Teams**: Auto-generate pitch decks from discovery calls Consulting Firms**: Create client proposals from needs assessments Marketing Agencies**: Build campaign presentations from strategy sessions Product Teams**: Transform user research into stakeholder presentations Training & Education**: Convert session notes into learning materials ⚠️ Important Notes Template must use consistent Object IDs for automation to work Google Drive images require ImgBB hosting for reliable URL access AI agent output structure is complex; JavaScript parsing recommended Rate limits apply for API services (especially image generation) 📦 Resources & Templates API Services (Get Your Keys Here) OpenRouter** - For Flux (nanobanana) AI image generation ImgBB API** - Free image hosting service OpenAI API** - For AI agents and text generation Google Cloud Console** - Enable Google Slides, Drive, and Docs APIs Google AI Studio** - For Gemini API key Templates & Examples Meeting Transcript Sample** - Example transcript structure Google Sheets Database Template** - Copy this to track your presentations Presentation Template** - Base slide deck with Object IDs 💡 Tip: Make copies of all templates before using them in your workflows! Have questions or improvements? Connect with me: X (Twitter): @juppfy Email: joseph@uppfy.com P.S: I'd love to hear how you adapt this for your workflow!. An n8n automation workflow template by Joseph.

By Nima Salimi

Overview This n8n workflow automatically retrieves Brevo contact reports and inserts summarized engagement data into NocoDB. It groups campaign activity by email, creating a clean, unified record that includes sent, delivered, opened, clicked, and blacklisted events. This setup keeps your CRM or marketing database synchronized with the latest Brevo email performance data. ✅ Tasks ⏰ Runs automatically on schedule or manually 🌐 Fetches contact activity data from Brevo API 🧩 Groups all campaign activity per email 💾 Inserts summarized data into NocoDB ⚙️ Keeps engagement metrics synced between Brevo and NocoDB 🛠 How to Use 🧱 Prepare your NocoDB table Create a table with fields for: email, messagesSent, delivered, opened, clicked, done, and blacklisted. 🔑 Connect your Brevo credentials Add your Brevo API Key in the HTTP Request node to fetch contact data securely. 🧮 Review the Code Nodes These nodes group contact activity by email and prepare a single dataset for insertion. 🚀 Run or schedule the workflow Execute it manually or use a Schedule Trigger to automate the data sync process. 📌 Notes 🗂 Make sure the field names in NocoDB match those used in the workflow. 🔐 Keep your Brevo API Key secure and private. ⚙️ The workflow can be expanded to include additional fields or filters. 📊 Use the data for engagement analytics, segmentation, or campaign performance tracking. An n8n automation workflow template by Nima Salimi.

By Juan Cristóbal Andrews

Who's it for This template is designed for filmmakers, content creators, social media managers, and AI developers who want to harness OpenAI's Sora 2 for creating physically accurate, cinematic videos with synchronized audio. Whether you're generating realistic scenes from text prompts or reference images with proper physics simulation, creating multi-shot sequences with persistent world state, or producing content with integrated dialogue and sound effects, this workflow streamlines the entire video generation process from prompt to preview and Google Drive upload. What it does This workflow: Accepts a text prompt, optional reference image, OpenAI API key, and generation settings via form submission Validates reference image format (jpg, png, or webp only) Sends the prompt and optional reference to the Sora 2 API endpoint to request video generation Continuously polls the video rendering status (queued → in progress → completed) Waits 30 seconds between status checks to avoid rate limiting Handles common generation errors with descriptive error messages Automatically fetches the generated video once rendering is complete Downloads the final .mp4 file Uploads the resulting video to your Google Drive Displays the download link and video preview/screenshot upon completion How to set up 1. Get Your OpenAI API Key You'll need an OpenAI API key to use this workflow. Here's the general process: Create an OpenAI account at https://platform.openai.com Set up billing - Add payment information to enable API access Generate your API key through the API keys section in your OpenAI dashboard Copy and save your key immediately - you won't be able to view it again! ⚠️ Important: Your API key will start with sk- and should be kept secure. If you lose it, you'll need to generate a new one. 2. Connect Google Drive Add your Google Drive OAuth2 credential to n8n Grant necessary permissions for file uploads 3. Import and Run Import this workflow into n8n Execute the workflow via the form trigger Enter your API key, prompt, and desired settings in the form Optionally upload a reference image** to guide the video generation All generation settings are configured through the form, including: Model**: Choose between sora-2 or sora-2-pro Duration**: 4, 8, or 12 seconds Resolution**: Portrait or Landscape options Reference Image** (optional): Upload jpg, png, or webp matching your target resolution ⚠️ Sora 2 Pricing The workflow supports two Sora models which have the following API pricing: Sora 2 - $0.10/sec Portrait: 720x1280 Landscape: 1280x720 Sora 2 Pro - $0.30/sec (720p) or $0.50/sec (1080p) 720p - Portrait: 720x1280, Landscape: 1280x720 1080p - Portrait: 1024x1792, Landscape: 1792x1024 Duration options: 4, 8, 12 seconds (default: 4) Example costs: 4-second video with Sora 2: $0.40 12-second video with Sora 2 Pro (1080p): $6.00 Requirements Valid OpenAI API key (starting with sk-) Google Drive OAuth2 credential connected to n8n Reference image** (optional): jpg, png, or webp format - should match your selected video resolution for best results How to customize the workflow Modify generation parameters Edit the form fields to include additional options: Style presets (cinematic, anime, realistic) Camera movement preferences Audio generation options Image reference strength/influence settings It's recommended to visit the official documentation on prompting for a detailed Sora 2 guide. Adjust polling behavior Change the Wait node duration (default: 30 seconds) Modify the Check Status polling frequency based on typical generation times Add timeout logic for very long renders Customize error handling Extend error messages for additional failure scenarios Add retry logic for transient errors Configure notification webhooks for error alerts Alternative upload destinations Replace the Google Drive node with: Dropbox AWS S3 Azure Blob Storage YouTube direct upload Slack/Discord notification with video attachment Enhance result display Customize the completion form to show additional metadata Add video thumbnail generation Include generation parameters in the results page Enable direct playback in the completion form Workflow Architecture Step-by-step flow: Form Submission → User inputs text prompt, optional reference image, API key, and generation settings Create Video → Sends request to Sora 2 API endpoint with all parameters and reference image (if provided) Check Status → Polls the API for video generation status Status Decision → Routes based on status: Queued → Wait 30 seconds → Check Status again In Progress → Wait 30 seconds → Check Status again Completed → Proceed to download Failed → Display descriptive error message Wait → 30-second delay between status checks Download → Fetches the generated video file Google Drive → Uploads .mp4 to your Drive Completion Form → Displays download link and video preview/screenshot If you have any questions, just contact me on Linkedin Ready to create cinematic AI videos with physics-accurate motion, synchronized audio, and optional image references? Import this workflow and start generating! 🎬✨. An n8n automation workflow template by Juan Cristóbal Andrews.

By Nima Salimi

Overview This n8n workflow automatically fetches the Forex Factory calendar for yesterday using Rapid API, then saves the data to a connected Google Sheet and sends Telegram alerts for high and medium impact events. It runs daily on schedule, collecting key fields such as currency, time, impact, and market indicators, and organizes them for easy tracking and analysis. Perfect for forex traders and analysts who need quick access to reliable market data from the previous day’s events. ✅ Tasks ⏰ Runs automatically every day 🌐 Fetches yesterday’s Forex Factory calendar via Rapid API 🧾 Collects key data fields: year, date, time, currency, impact, actual, forecast, previous 📊 Saves all records to Google Sheets for tracking and analysis 🚨 Sends Telegram alerts for high and medium impact events ⚙️ Keeps your market data updated and organized with no manual work required 🛠 How to Use 📄 Create a Google Spreadsheet Create a new spreadsheet in Google Sheets and add two sheets: High Impact and Low Impact. Connect it to your Google Sheets nodes in n8n. 🌐 Find the API on Rapid API Go to Rapid API and search for Forex Factory Scraper. Subscribe to the API to get your access key. 🔑 Connect Rapid API to n8n In your HTTP Request node, add the header below to authenticate your request: 💬 Add Your Telegram Chat ID In the Telegram node, paste your Chat ID to receive daily alerts for high-impact news. 🕒 Activate the Workflow Enable the Schedule Trigger to run daily. The workflow will automatically fetch yesterday’s Forex Factory calendar, save it to Google Sheets, and send Telegram notifications. An n8n automation workflow template by Nima Salimi.

By Amirul Hakimi

🚀 Enrich CRM Leads with LinkedIn Company Data Using AI Who's it for Sales teams, marketers, and business development professionals who need to automatically enrich their CRM records with detailed company information from LinkedIn profiles. Perfect for anyone doing B2B outreach who wants to personalize their messaging at scale. What it does This workflow transforms bare-bones lead records into rich, personalized prospect profiles by: Automatically scraping LinkedIn company profiles Using AI (GPT-4) to extract key business intelligence Generating 15+ email-ready personalization variables Updating your CRM with structured, actionable data The workflow pulls company overviews, products/services, funding information, recent posts, and converts everything into natural-language variables that can be dropped directly into your outreach templates. How it works Trigger: Workflow starts when a new lead is added to Airtable (or on schedule) Fetch: Retrieves the lead record containing the LinkedIn company URL Scrape: Pulls the raw HTML from the company's LinkedIn profile Clean: Strips HTML tags and formats content for AI processing Analyze: GPT-4 extracts structured company intelligence (overview, products, market presence, recent posts) Transform: Converts analysis into 15+ email-ready variables with natural phrasing Update: Writes enriched data back to your CRM Setup Requirements Airtable account** (free tier works fine) OpenAI API key** (GPT-4o-mini recommended for cost-effectiveness) LinkedIn company URLs** stored in your CRM 5 minutes** for initial configuration How to set up Configure Airtable Connection Replace YOUR_AIRTABLE_BASE_ID with your base ID Replace YOUR_TABLE_ID with your leads table ID Ensure your table has a "LinkedIn Organization URL" field Add your Airtable API credentials Add OpenAI Credentials Click on both OpenAI nodes Add your OpenAI API key GPT-4o-mini is recommended (cost-effective and fast) Set Up Trigger Add a trigger node (Schedule, Webhook, or Airtable trigger) Configure to run when new leads are added or on a daily schedule Test the Workflow Add a test lead with a LinkedIn company URL Execute. An n8n automation workflow template by Amirul Hakimi.

By Ruth Olatunji

This n8n is a daily analytics automation that calculates which lead sources generate actual revenue, not just leads. Provides ROI data, conversion rates, and budget allocation recommendations. Use Case: automates marketing ROI tracking by linking closed deals to their lead sources in Airtable, calculating revenue and ROI per channel, and sending daily insights to Slack. What It Does Runs nightly to analyze closed deals from last 30 days Matches deals to their original lead sources Calculates total revenue per source Computes ROI (revenue vs. cost per lead) Determines conversion rates by source Updates Lead Sources table with metrics Sends weekly reports to team How It Works Step 1: Schedule Trigger Runs daily at midnight Step 2: Fetch Closed Won Deals Gets all deals where: Stage = "Closed Won" Actual Close Date in last 30 days Step 3: Fetch Lead Sources Gets cost and lead count data from Lead Sources table Step 4: Calculate ROI (JavaScript) For each source: Total revenue = Sum of all deals from that source Total cost = Cost per lead × Total leads ROI = ((Revenue - Cost) / Cost) × 100 Conversion rate = Deals closed / Total leads × 100 Average deal size = Revenue / Deal count Step 5: Update Lead Sources Writes calculated metrics back to Airtable Step 6: Send Report Slack message with top 3 performing sources Business Impact Marketing ROI:** Know exactly which channels generate revenue Budget optimization:** Allocate spend to highest-ROI sources Data-driven decisions:** Stop guessing, start knowing Cost reduction:** Cut low-performing channels Revenue growth:** Double down on what works Technical Requirements n8n (self-hosted or cloud) Airtable (uses existing tables) Slack (for reports) Gmail for reminder incase CEO missed the report in the Slack channel (optional). An n8n automation workflow template by Ruth Olatunji.

By Xavier Tai

AI Lead Qualifier & Router An intelligent lead management system that automatically captures incoming leads via webhook, uses AI to analyze and score each prospect, then routes them to the appropriate team or campaign based on qualification score—delivering hot leads to sales instantly while nurturing others on autopilot. What It Does This workflow eliminates the manual process of: • Daily lead review and qualification • Manual scoring and prioritization • Lead assignment and routing decisions • Follow-up email composition • CRM data entry and updates • Sales team notifications for hot prospects Instead, it delivers qualified, routed leads with AI insights in under 30 seconds—complete with structured scoring, personalized responses, and organized data storage for tracking. Key Features • Webhook Lead Capture - Accepts leads from any source (forms, landing pages, APIs) • AI-Powered Qualification - Analyzes budget, timeline, message quality, and fit using OpenAI • Structured Scoring - Generates 0-100 scores with reasoning, strengths, and concerns • Intelligent Routing - Automatically directs hot leads (70+) to sales, others to nurture • Instant Notifications - Slack alerts for high-priority prospects with full context • Dual Email Flows - Personalized responses based on lead quality and urgency • Airtable Storage - Organized tracking with qualification data and timestamps. An n8n automation workflow template by Xavier Tai.

By Yaron Been

This workflow automates the entire text-to-video generation process using OpenAI's SORA-2 model via Replicate API. Simply provide a seed image, text prompt describing your desired scene, and video duration (4, 8, or 12 seconds), and the workflow handles the video creation, status monitoring, and delivery of your AI-generated content - typically ready in 2-5 minutes. Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Powers the OpenAI SORA-2 AI model for text-to-video generation OpenAI API**: Required for SORA-2 model authentication Status Monitoring**: Automated checking system with intelligent retry logic Error Handling**: Built-in resilience with comprehensive error management Batch Processing**: Optional bulk generation for multiple videos How to Install Import the Workflow: Download the .json file and import it into your n8n instance Get API Keys: Sign up at replicate.com and openai.com for your API tokens Configure API Tokens: Replace placeholders in the "Set API Token" node with your keys Add Seed Image: Update the image URL in the "Add Seed Image, Prompt and amount of seconds" node (1280x720 recommended) Write Your Prompt: Describe your desired video scene and set duration, then run the workflow Use Cases Ad Agencies**: Generate multiple video variations for A/B testing campaigns E-commerce Brands**: Create product demonstration videos from a single photo Content Creators**: Produce unique video content without filming equipment Marketing Teams**: Rapidly iterate on video ad concepts for social media Startups**: Create professional video content without expensive production costs Social Media Managers**: Generate platform-specific video content at scale Connect with Me Email**: Yaron@nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ ROASPIG**: Check out ROASPIG.com for scalable media generation and automation solutions #n8n #automation #ai #sora2 #texttovideo #openai #replicate #contentcreation #videomarketing #adcreatives. An n8n automation workflow template by Yaron Been.

By Joy Sutradhar

Instagram & Facebook Video/Reels Downloader Bot (Telegram bot) Once set up, simply send any Instagram Reel or Facebook video link to your Telegram bot, and it will automatically: Check if the shared link is valid. Detect whether it’s an Instagram or Facebook link. Fetch the video using API and scraping methods. Download the video directly from the source. Send the downloaded video (or a message if it’s invalid) right back to your Telegram chat — instantly! How It Works (Node Flow) Telegram Trigger:** Listens for new messages (video/reel links) from users. Regex Node:** Extracts and validates the Instagram/Facebook link format. Conditional Node (If):** Determines whether the link is for Facebook or Instagram. Link Validation Node:** Ensures the provided link is valid and reachable. Instagram Node:** Fetches video metadata via API. Decodes and downloads the Reel. Sends the downloaded video and confirmation message via Telegram. Facebook Node:** Uses scraping/API to get the video source. Generates the downloadable link. Downloads and sends the Facebook video back to Telegram. Error Handling Node:** Sends a custom error message if the link is invalid. Features ✅ Works with both Instagram and Facebook links ✅ Automatically detects the platform and processes accordingly ✅ Delivers the downloaded video directly to your Telegram chat ✅ Handles invalid or broken links gracefully ✅ Clean and modular structure — easy to extend or customize Use Case Perfect for social media managers, content creators, and automation enthusiasts who want a simple Telegram bot to fetch and download Reels or videos without using third-party apps or websites. An n8n automation workflow template by Joy Sutradhar.

By Adrian

This workflow fetches NASA’s Astronomical Picture of the Day (APOD), prepares a caption combining the title and explanation, publishes the image to Instagram and sends you a Telegram notification with the result. It runs on a schedule so you can share inspiring space images without manual effort. Who is it for? Designed for science communicators, educators, astronomy fans and social media managers who want to share the APOD each day without searching for content. It’s also helpful for anyone looking to automate daily posts while receiving clear success or failure notifications. How it works A Schedule Trigger fires every day at 18:00 (adjustable) to start the workflow. The Get APOD HTTP request node calls https://api.nasa.gov/planetary/apod using your NASA API key and retrieves the image URL, title and explanation. The Prepare Caption node builds a caption by concatenating the title and explanation, and extracts the image URL. Prepare IG Post node sends a POST request to https://graph.facebook.com/v23.0/{YOUR_APP_ID}/media with the image URL and caption to create a media container on Instagram. A Wait node pauses the workflow while Instagram processes the media. The Get Status for Publish request checks the status of the media; the If node proceeds only when the status_code equals FINISHED. When ready, the Publish Post node calls to https://graph.facebook.com/v23.0/{YOUR_APP_ID}/media_publish endpoint with the creation_id to publish the photo on Instagram. On success, a Telegram node sends a message such as “PUBLISH STATUS: FINISHED” to your chat; on failure, another Telegram node notifies you that the upload failed and the workflow stops with an error. Setup steps ++Node Get APOD:++ Configure Query Auth with your own Nasa credential. ++Node: Prepare IG Post:++ Create a Facebook app and generate an access token with instagram_basic and pages_manage_posts permissions; Configure the url with you ID from you Meta Graph {YOUR_APP_ID}. Configure Facebook Graph API Credential Type with your token, you can generate in your API Graph Explorer ++Node Get Status For Publish:++ Configure your Facebook Graph API token like before. ++Node Publish Post:++ Configure your Facebook Graph API token like before and configure the url with you ID from you Meta Graph {YOUR_APP_ID}. ++Node Send Finish Message:++ Configure your token from Telegram API and your Telegram Chat ID {YOUR_CHAT_ID}. ++Node Send Fail Message:++ Configure your token from Telegram API and your Telegram Chat ID {YOUR_CHAT_ID}. Test the workflow to ensure the image posts correctly and that the Telegram notifications reflect the status. Requirements · NASA APOD API key from api.nasa.gov. · Instagram account linked to a Facebook page and a valid Facebook Graph API token with the appropriate permissions. · Telegram bot token and chat ID. How to customise it You can change the posting time or frequency, edit the caption template to include hashtags or links, or send success/failure notifications via email or Slack instead of Telegram. You might also save the images to cloud storage or cross‑post to other platforms, and adjust the error handling logic based on your needs. An n8n automation workflow template by Adrian.

By Florent

Random Process Scheduler Turn predictable automations into human-like activity with random scheduling across easily customisable time slots. Perfect for content publishing with organic scheduling patterns, social media automation, API systems that need to avoid rate limiting, or any automation requiring randomised timing control across multiple periods. All times are configured in local timezone with automatic UTC conversion for technical operations. Features easy slot management with chronological ordering, gap support, and 24-hour window scheduling. How to use Set schedulerExecutionTime in Init node (match it to Schedule Trigger cron) Define time slots with start/end hours and probability values (see below) Configure Execute sub-process with your own workflow ID Configure SMTP credentials, local time zone and optionally project paths Step by Step Configuration Two variables to set in the Init node's "Custom Configuration" section: 1. When the scheduler runs daily: const schedulerExecutionTime = 1; // 1am (24h clock; must match Schedule Trigger node) 2. Your execution slots: const subprocessTimeSlots = { morning: { start: 6, end: 12, probability: 0.85 }, afternoon: { start: 12, end: 18, probability: 0.85 }, evening: { start: 18, end: 24, probability: 0.5 } }; That's it. Three slots, three probabilities. Add or remove slots, adjust times - it just works. Real-world example with gaps: const subprocessTimeSlots = { night: { start: 0, end: 2, probability: 0.1 }, // Optional late activity morning: { start: 6, end: 10, probability: 0.85 }, // Gap from 2-6am (no execution) noon: { start: 12, end: 14, probability: 0.85 }, // Gap from 10am-12pm afternoon: { start: 16, end: 18, probability: 0.85 }, // Gap from 2-4pm evening: { start: 20, end: 24, probability: 0.5 } // Gap from 6-8pm }; 3. Configure Execute sub-process with your workflow ID Your sub-workflow MUST start with a Wait node and be configured with {{ $json.executions.relativeDelaySeconds }} as “Wait Amount”. 4. Additional Configuration SMTP credential Time zone (Init node): const LOCAL_TIMEZONE = $env.GENERIC_TIMEZONE || 'Europe/Paris'; by default Project paths (Init node): // ⚠️ Your email here • const N8N_ADMIN_EMAIL = $env.N8N_ADMIN_EMAIL || 'yourmail@world.com'; // ⚠️ Your projects’ ROOT folder on your mapped server here • const N8N_PROJECTS_DIR = $env.N8N_PROJECTS_DIR || '/files/n8n-projects-data'; // ⚠️ Your project’s folder name here for logging • const PROJECT_FOLDER_NAME = "RPS"; Requirements n8n instance running in Docker with file system access Volume mapping for persistent storage (e.g., /local-files:/files) De-activate** Read/Write nodes & Email sends if you do not want to use logging features (file system access optional) SMTP server for notifications n8n API credentials for error handling Target sub-workflow* with *Wait** node to handle relativeDelaySeconds IMPORTANT: Your sub-workflow MUST start with a Wait node and be configured with {{ $json.executions.relativeDelaySeconds }} as “Wait Amount”. How it works 24-Hour Window Algorithm**: Schedules executions from current time until next scheduler run, handling timezone conversions and cross-midnight scenarios Automatic Validation**: Checks for overlaps, invalid time ranges, and probability values on every run Chronological Processing**: Processes slots in order regardless of how you define them Inclusive/Exclusive Boundaries**: 6-12 slot runs from 6:00:00 to 11:59:59 (start inclusive, end exclusive) Chained Execution**: Each subprocess receives a relativeDelaySeconds value for sequential execution with calculated intervals Comprehensive Monitoring**: Tracks planned vs actual execution times with delay calculations and detailed logging Configuration Rules No Overlap**: Slots cannot overlap (6-10 and 9-12 is invalid) Valid Ranges**: Start 0-23, end 0-24, start < end Valid Probability**: 0 to 1 (0.85 = 85% chance) Gaps Allowed**: Skip hours completely (e.g., no execution 2-6am) Emoji Support**: Use "night", "morning", "noon", "evening" keywords in slot names for visual logs Use Cases: Content publishing with organic scheduling patterns Social media automation with human-like posting intervals API systems avoiding rate limits through unpredictable timing Business hours automation with precise timing control. An n8n automation workflow template by Florent.

By Stéphane Bordas

How it Works This workflow lets you build a Messenger AI Agent capable of understanding text, images, and voice notes, and replying intelligently in real time. It starts by receiving messages from a Facebook Page via a Webhook, detects the message type (text, image, or audio), and routes it through the right branch. Each input is then prepared as a prompt and sent to an AI Agent that can respond using text generation, perform quick calculations, or fetch information from Wikipedia. Finally, the answer is formatted and sent back to Messenger via the Graph API, creating a smooth, fully automated chat experience. Set Up Steps Connect credentials Add your OpenAI API key and Facebook Page Access Token in n8n credentials. Plug the webhook Copy the Messenger webhook URL from your workflow and paste it into your Facebook Page Developer settings (Webhook → Messages → Subscribe). Customize the agent Edit the System Message of the AI Agent to define tone, temperature, and purpose (e.g. “customer support”, “math assistant”). Enable memory & tools Turn on Simple Memory to keep conversation context and activate tools like Calculator or Wikipedia. Test & deploy Switch to production mode, test text, image, and voice messages directly from Messenger. Benefits 💬 Multi-modal Understanding — Handles text, images, and audio messages seamlessly. ⚙️ Full Automation — End-to-end workflow from Messenger to AI and back. 🧠 Smart Replies — Uses OpenAI + Wikipedia + Calculator for context-aware answers. 🚀 No-Code Setup — Build your first Messenger AI in less than 30 minutes. 🔗 Extensible — Easily connect more tools or APIs like Airtable, Google Sheets, or Notion. An n8n automation workflow template by Stéphane Bordas.

By Rahul Joshi

Description Automatically analyze incoming lead replies from Google Sheets using Azure OpenAI GPT-4, classify their intent (Demo Request, Pricing, Objection, etc.), and create actionable follow-up tasks in ClickUp — all without manual intervention. Streamline your sales response workflow and never miss a lead again. 🤖📩📈 What This Template Does Triggers every 15 minutes to check for new lead replies in Google Sheets. ⏰ Prepares lead data for AI analysis by standardizing input fields. 🧩 Uses Azure OpenAI GPT-4 to classify lead intent (Demo Request, Pricing Inquiry, Objection, etc.). 🧠 Routes leads based on intent to the corresponding follow-up handler. 🔀 Creates new ClickUp tasks with calculated due dates, descriptions, and pipeline stages. 🗂️ Adds structured checklists to each task for consistent sales follow-ups. ✅ Loops through multiple tasks while respecting ClickUp API rate limits. 🔁 Key Benefits ✅ Saves hours of manual lead qualification and task creation. ✅ Ensures no lead reply is ignored or delayed. ✅ Standardizes intent-based follow-ups for sales teams. ✅ Enhances productivity with AI-driven decision logic. ✅ Maintains clear visibility across CRM and task systems. Features 15-minute recurring trigger to monitor new replies. AI-powered intent classification using Azure OpenAI GPT-4. Multi-category routing logic for personalized next steps. Seamless ClickUp integration for automated task generation. Smart checklist creation for follow-up management. Batch loop processing to avoid rate-limit errors. Requirements n8n instance (cloud or self-hosted). Google Sheets OAuth2 credentials with read access. Azure OpenAI GPT-4 API credentials. ClickUp API token with workspace permissions. Target Audience Sales and marketing teams managing inbound leads. 💼 Agencies automating client qualification workflows. 🏢 Startups improving lead follow-up efficiency. 🚀 Teams integrating AI-driven insights into CRM processes. 🌐 Step-by-Step Setup Instructions Connect Google Sheets with your lead replies document. 📊 Add Azure OpenAI GPT-4 API credentials for intent analysis. 🧠 Configure ClickUp workspace details — team, space, folder, and list IDs. ⚙️ Set your preferred trigger interval (default: every 15 minutes). ⏰ Run a test with sample data to confirm intent mapping and task creation. ✅ Activate the workflow to automatically classify leads and create ClickUp tasks. 🚀. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Stop losing warm leads in the noise. This automation analyzes your lead engagement data, calculates priority scores based on activity and last contact date, and automatically queues your top 10 leads for follow-up in ClickUp — complete with suggested send times based on timezone. ⚡ What This Template Does Pulls lead data from Google Sheets (e.g., name, engagement, last contact date, timezone). 📄 Calculates days since last contact to measure lead freshness. ⏰ Combines engagement score and recency into a weighted priority score. 📊 Sorts and filters top 10 leads for immediate follow-up. 🔝 Suggests best time to reach out based on each lead’s timezone. 🌍 Creates corresponding ClickUp tasks with lead details. 🗂️ Updates the Google Sheet to mark leads as queued. ✅ Key Benefits Automatically identify high-priority leads daily. 🎯 Increase conversion rates with timely, personalized follow-ups. ⏱️ Eliminate manual sorting and spreadsheet filtering. 🚫 Keep sales teams organized with ClickUp task automation. 💼 Works perfectly for SDRs, account managers, and B2B teams. 🤝 Features Google Sheets integration for real-time lead updates. 📊 Smart recency calculator (days since last contact). ⏰ Weighted priority formula (70% engagement, 30% recency). 🧮 ClickUp task creation for seamless team coordination. 🔗 Timezone-based follow-up time suggestion. 🌐 Configurable limit (Top 10 leads — adjustable). ⚙️ Automatic sheet update with queue status tracking. 📋 Requirements n8n instance (cloud or self-hosted). 🧰 Google Sheet with columns: Lead Name, Engagement_Score, Last_Contact_Date, Timezone, Email. 📑 Connected Google Sheets and ClickUp credentials in n8n. 🔐 Active ClickUp workspace with accessible list or space ID. 🧭 Target Audience Sales and marketing teams managing large lead lists. 📈 B2B organizations using ClickUp for pipeline tracking. 🧩 SDRs who need to prioritize outreach daily. 🗓️ Agencies managing multiple clients and follow-up cadences. 🤝 Step-by-Step Setup Instructions (Concise) Create or connect a Google Sheet with all required headers. 📋 Update node credentials for Google Sheets and ClickUp. 🔑 Adjust weightage logic or maxItems count if needed. ⚙️ Test workflow using the manual trigger. ▶️ (Optional) Schedule it to run daily for auto-prioritization. ⏰ Review ClickUp tasks and follow up with top leads. 📨 Security Best Practices Share the Google Sheet only with the n8n Google account (Editor). 🔒 Keep ClickUp API credentials encrypted within n8n. 🛡️ Review ClickUp task creation permissions before activation. ✅ Regularly clean archived leads from the Google Sheet. 🧹. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Automatically generate polished, n8n-ready template descriptions from your saved JSON workflows in Google Drive. This AI-powered automation processes workflow files, drafts compliant descriptions, and delivers Markdown and HTML outputs directly to your inbox. 🚀💌📊💬 What This Template Does Manually triggers the workflow to start processing. Searches a specified Google Drive folder for JSON workflow files. Iterates through each JSON file found in that folder. Downloads each file and prepares it for data extraction. Parses workflow data from the downloaded JSON content. Uses Azure OpenAI GPT-4 to generate concise titles and detailed descriptions. Converts the AI output into structured Markdown for n8n template publishing. Creates an HTML version of the description for email delivery. Logs generated details into a Google Sheet for record-keeping. Sends an email containing the Markdown and HTML descriptions to the target recipient. Key Benefits ✅ Fully automates n8n template description creation. ✅ Ensures consistency with official n8n publishing guidelines. ✅ Saves time while eliminating human writing errors. ✅ Provides dual Markdown + HTML outputs for flexibility. ✅ Centralizes workflow metadata in Google Sheets. ✅ Simplifies collaboration and version tracking via email delivery. Features Manual workflow trigger for controlled execution. Integration with Google Drive for locating and downloading JSON files. Intelligent parsing of workflow data from JSON structure. GPT-4-powered AI for title and description generation. Automatic Markdown + HTML formatting for n8n publishing. Google Sheets integration for persistent record-keeping. Automated Gmail delivery of generated documentation. Requirements n8n instance (cloud or self-hosted). Google Drive OAuth2 credentials with file read permissions. Google Sheets OAuth2 credentials with edit permissions. Azure OpenAI GPT-4 API key for AI text generation. Gmail OAuth2 credentials for email sending. Target Audience n8n content creators documenting workflows. 👩‍💼 Automation teams handling multiple template deployments. 🔄 Agencies and freelancers managing workflow documentation. 🏢 Developers leveraging AI for faster template creation. 🌐 Technical writers ensuring polished, standardized outputs. 📊 Step-by-Step Setup Instructions Connect your Google Drive account and specify the folder containing JSON workflows. 🔑 Authorize Google Sheets and confirm access to the tracking spreadsheet. ⚙️ Add Azure OpenAI GPT-4 API credentials for AI-powered text generation. 🧠 Connect Gmail credentials for automated email delivery. 📧 Run the workflow manually using a test JSON file to validate all nodes. ✅ Enable the workflow to automatically generate and send descriptions as needed. 🚀. An n8n automation workflow template by Rahul Joshi.

By WeblineIndia

iOS App Store Review Monitor & Notifier – Automated User Feedback Tracking This workflow runs on a scheduled basis (default: every 6 hours, customizable) and monitors new App Store reviews for your iOS apps. It fetches reviews via Apple’s iTunes RSS API, filters only new reviews since the last run and sends real-time notifications to your team via email, Slack, Telegram or other channels. Never miss important user feedback again. Who’s it for iOS developers** tracking user sentiment and bug reports. Product managers monitoring customer satisfaction and feature requests. Customer support teams responding quickly to complaints and issues. Marketing teams collecting testimonials and case studies from positive reviews. DevOps teams automating review monitoring as part of release processes. How it works Schedule Trigger** runs every 6 hours (cron configurable). App Configuration:** Define monitored apps with {appId, country, lang}. Fetch Reviews:** Call Apple’s iTunes RSS API for latest customer reviews. Extract & Parse:** Convert JSON into structured review data (rating, content, author, date, version). Filter New Reviews:** Compare with last run using timestamps → only new reviews pass. Format Notifications:** Build rich messages with review details. Send Alerts:** Deliver via Email, Slack, Telegram, Teams, etc. Track State:** Last check time to prevent duplicates. How to set up Find your App Store ID Go to your app’s App Store page. Example URL: https://apps.apple.com/us/app/app-name/id123456789 The number after id is the App Store ID (123456789). Configure App Settings In the App Config node set: appId = App Store ID country = Country code (us, gb, de, etc.) lang = Language code (en, es, fr, etc.) Set Up Notifications Choose your notification method: Email: configure Gmail/SMTP credentials Slack: add Slack webhook URL Telegram: set up bot token + chat ID Teams: configure Teams webhook Customize Schedule In the Schedule Trigger node: Every 6 hours → 0 */6 * * * Daily at 9 AM → 0 9 * * * Every 2 hours → 0 */2 * * * Test the Workflow Use a known App ID (e.g., WhatsApp: 310633997) for testing. Run manually to verify notifications are formatted correctly. Requirements n8n (cloud or self-hosted) with HTTP Request + notification nodes. App Store ID** for each monitored app. Notification credentials (Email, Slack, Telegram, etc.). Internet access to query Apple’s iTunes API. How to customize the workflow Multiple Apps** Monitor multiple apps by extending config:** [ {appId: "310633997", country: "us", lang: "en"}, {appId: "389801252", country: "gb", lang: "en"}, {appId: "544007664", country: "de", lang: "de"} ] Notification Templates** Add-ons to level up Sentiment Analysis:** AI-based scoring per review. Auto-Reply Integration:** Respond via App Store Connect API. Analytics Dashboard:** Store in Sheets/Airtable for trends. Competitor Monitoring:** Track rival app reviews. Translation:** Auto-translate to English. Escalation Rules:** Different alerts by rating severity. Common Troubleshooting No reviews returned** → app may not have recent reviews, try other country codes. JSON parsing errors** → check App Store ID validity. Duplicate notifications** → confirm time filtering works correctly. API rate limits** → Apple may throttle, add delays. Missing metadata** → some apps don’t return all fields. Need Help? If you’d like to customize this automation flow to suit your needs, write to our n8n automation team at WeblineIndia and we’ll adapt the template to your exact use case. An n8n automation workflow template by WeblineIndia.

By Anshul Chauhan

🤖 Automated YouTube Script Generator (Shorts & Long-Form) This workflow is a content multiplier. Provide a single video topic via a form, and it automatically researches, outlines, and writes two separate scripts: one for a YouTube Shorts and another for a Long-form video, saving both directly to Google Docs. ✨ Key Features Dual-Format Output:** Creates tailored scripts for both Shorts and long-form videos from one idea. AI-Powered Writing:* Uses *Google Gemini** for all creative steps, from building a structured outline to writing the final scripts. Up-to-Date Research:* Integrates *Tavily AI** to pull fresh, relevant information from the web. Fully Automated:** An end-to-end process that takes a form submission and delivers final documents to your Google Drive with no manual steps. ⚙️ How It Works After a topic is submitted, the workflow splits into two parallel branches: The Shorts Branch: This path is built for speed. It performs a quick web search and immediately uses an AI agent to write a short, punchy script. The Long-Form Branch: This path focuses on structure. It conducts a web search, uses an AI agent to first create a detailed outline, and then uses another AI agent to write a comprehensive script based on that outline. 🔑 Prerequisites An active n8n instance. A form to submit your video topic. API keys for Tavily AI and Google Gemini. Google Account credentials (OAuth2) configured in n8n for Google Docs. 🛠️ Setup Guide On form submission Trigger: Configure your form to accept a field for your video topic (e.g., a field named topic). Tavily Nodes: In both Tavily nodes, select or create your Tavily API credential and paste in your API key. Google Gemini Chat Model: In the nodes labeled AI Agent and Create Outline, select your Google AI credential linked to your Gemini API key. Google Docs Nodes: For all four Google Docs nodes (Create Doc, Update Doc, etc.), select your Google OAuth2 credential. Activate the Workflow: Once all credentials are in place, save and activate the workflow. 🚀 How to Use Activate the workflow. Submit your topic via the connected form. Check your Google Drive a few moments later for your the new script!. An n8n automation workflow template by Anshul Chauhan.

By Barbora Svobodova

Telegram AI Voice & Email Assistant: Manage, Draft & Discuss Emails via Voice Who’s it for This workflow is perfect for professionals and teams who want to manage email communications hands-free directly from Telegram. Simply send a voice message to your bot and seamlessly check your recent emails, draft or send a reply, and discuss email threads—all powered by OpenAI’s transcription and chat capabilities, with no third-party voice agent required. How it works / What it does Sends voice messages to a Telegram bot, which are then transcribed via OpenAI. Retrieves recent emails, drafts, or sends replies based on your commands. Engages the user in conversational discussion about email content using OpenAI chat. Responds in text or synthesized voice (OpenAI), creating a natural interactive experience. Automates email management from Telegram, keeping you efficient on the go. How to set up Create a Telegram bot via @BotFather and obtain your API token. Add the OpenAI API key and Gmail OAuth credentials to n8n. Assign your credentials to the Telegram, OpenAI, and Gmail nodes (Draft/Send/Get Email). Deploy and activate the workflow. Interact with your Telegram bot: just send voice messages and let the assistant manage your emails! Requirements Telegram Bot Token OpenAI API Key Gmail OAuth Credentials How to customize the workflow Adjust the Switch node to route and handle new message types or responses. Integrate additional services such as Slack, Notion, or custom tools as needed. Fine-tune prompts or the OpenAI transcription settings for your specific use case. Modify email templates and memory/session nodes for advanced conversation flows. Embed video guides or extra sticky notes for enhanced onboarding and usability. An n8n automation workflow template by Barbora Svobodova.

By panyanyany

Overview This workflow utilizes the Defapi API with Sora 2 AI model to generate stunning viral videos with creative AI-generated motion, effects, and storytelling. Simply provide a creative prompt describing your desired video scene, and optionally upload an image as a reference. The AI generates professional-quality video content perfect for tiktok, youtube, marketing campaigns, and creative projects. Input: Creative prompt (required) + optional image Output: AI-generated viral video ready for social media and content marketing Users can interact through a simple form, providing a text prompt describing the desired video scene and optionally uploading an image for context. The system automatically submits the request to the Defapi Sora 2 API, monitors the generation status in real time, and retrieves the final video output. This solution is ideal for content creators, social media marketers, video producers, and businesses who want to quickly generate engaging video content with minimal setup. Prerequisites A Defapi account and API key: Sign up at Defapi.org to obtain your API key for Sora 2 access. An active n8n instance (cloud or self-hosted) with HTTP Request and form submission capabilities. Basic knowledge of AI prompts for video generation to achieve optimal results. Example prompt: A pack of dogs driving tiny cars in a high-speed chase through a city, wearing sunglasses and honking their horns, with dramatic action music and slow-motion jumps over fire hydrants. For 15-second HD videos, prefix your prompt with (15s,hd). (Optional) An image to use as a reference or starting point for video generation. Image Restrictions: Avoid uploading images with real people or highly realistic human faces, as they will be rejected during content review. Important Notes**: The API requires proper authentication via Bearer token for all requests. Content undergoes multi-stage moderation. Avoid violence, adult content, copyrighted material, and living celebrities in both prompts and images. Setup Instructions Obtain API Key: Register at Defapi.org and generate your API key with Sora 2 access. Store it securely—do not share it publicly. Configure Credentials: In n8n, create HTTP Bearer Auth credentials named "Defapi account" with your API key. Configure the Form: In the "Upload Image" form trigger node, ensure the following fields are set up: Prompt (text field, required) - Describe the video scene you want to generate Image (file upload, optional) - Optionally upload .jpg, .png, or .webp image files as reference Test the Workflow: Click "Execute Workflow" in n8n to activate the form trigger. Access the generated form URL and enter your creative video prompt. Optionally upload an image for additional context. The workflow will process any uploaded image through the "Convert to JSON" node, converting it to base64 format. The request is sent to the Sora 2 API endpoint at Defapi.org. The system will wait 10 seconds and then poll the API status until video generation is complete. Handle Outputs: The final "Format and Display Results" node formats and displays the generated video URL for download or embedding. Workflow Structure The workflow consists of the following nodes: Upload Image (Form Trigger) - Collects user input: creative prompt (required) and optional image file Convert to JSON (Code Node) - Converts any uploaded image to base64 data URI and formats prompt Send Sora 2 Generation Request to Defapi.org API (HTTP Request) - Submits video generation request to Sora 2 API Wait for Processing Completion (Wait Node) - Waits 10 seconds before checking status Obtain the generated status (HTTP Request) - Polls API task query endpoint for completion status Check if Image Generation is Complete (IF Node) - Checks if status equals 'success' Format and Display Results (Set Node) - Extracts and formats final video URL output Technical Details API Endpoint**: https://api.defapi.org/api/sora2/gen (POST request) Model Used**: Sora 2 AI video generation model Video Capabilities**: Supports 15-second videos and high-definition (HD) output Status Check Endpoint**: https://api.defapi.org/api/task/query (GET request) Wait Time**: 10 seconds between status checks Image Processing**: If an image is uploaded, it is converted to base64 data URI format (data:image/[type];base64,[data]) for API submission Authentication**: Bearer token authentication using the configured Defapi account credentials Request Body Format**: { "prompt": "Your video description here", "images": ["data:image/jpeg;base64,..."] } Note: The images array can contain an image or be empty if no image is provided Response Format**: The API returns a task_id which is used to poll for completion status. Final result contains data.result.video with the video URL. Accepted Image Formats**: .jpg, .png, .webp Specialized For**: Viral video content, social media videos, creative video marketing Customization Tips Enhance Prompts**: Include specifics like: Scene description and action sequences Character behaviors and emotions Camera movements and angles (e.g., slow-motion, dramatic zoom) Audio/music style (e.g., dramatic, upbeat, cinematic) Visual effects and atmosphere Timing and pacing details Enable 15s and HD Output**: To generate 15-second high-definition videos, start your prompt with (15s,hd). For example: (15s,hd) A pack of dogs driving tiny cars in a high-speed chase through a city... Content Moderation The API implements a three-stage content review process: Image Review: Rejects images with real people or highly realistic human faces Prompt Filtering: Checks for violence, adult content, copyrighted material, and living celebrities Output Review: Final check after generation (often causes failures at 90%+ completion) Best Practices: Avoid real human photos; use illustrations or cartoons instead Keep prompts generic; avoid brand names and celebrity names You can reference verified Sora accounts (e.g., "let @sama dance") If generation fails at 90%+, simplify your prompt and try again Example Prompts "A pack of dogs driving tiny cars in a high-speed chase through a city, wearing sunglasses and honking their horns, with dramatic action music and slow-motion jumps over fire hydrants." "(15s,hd) Animated fantasy landscape with floating islands, waterfalls cascading into clouds, magical creatures flying, golden sunset lighting, epic orchestral music." "(15s,hd) Product showcase with 360-degree rotation, dramatic lighting changes, particle effects, modern electronic background music." Use Cases Social Media Content**: Generate eye-catching videos for Instagram Reels, TikTok, and YouTube Shorts Marketing Campaigns**: Create unique promotional videos from product images Creative Projects**: Transform static images into dynamic storytelling videos Content Marketing**: Produce engaging video content without expensive production costs Viral Content Creation**: Generate shareable, attention-grabbing videos for maximum engagement. An n8n automation workflow template by panyanyany.

By Atik

Automate video transcription and Q&A with async VLM processing that scales from short clips to long recordings. What this workflow does Monitors Google Drive for new files in a specific folder and grabs the file ID on create Automatically downloads the binary to hand off for processing Sends the video to VLM Run for async transcription with a callback URL that posts results back to n8n Receives the transcript JSON via Webhook and appends a row in Google Sheets with the video identifier and transcript data Enables chat Q&A through the Chat Trigger + AI Agent. The agent fetches relevant rows from Sheets and answers only from those segments using the connected chat model Setup Prerequisites: Google Drive and Google Sheets accounts, VLM Run API credentials, OpenAI (or another supported) chat model credentials, n8n instance. Install the verified VLM Run node by searching for VLM Run in the nodes list, then click Install. You can also confirm on npm if needed. After install, it integrates directly for robust async transcription. Quick Setup: Google Drive folder watch Add Google Drive Trigger and choose Specific folder. Set polling to every minute, event to File Created. Connect Drive OAuth2. Download the new file Add Google Drive node with Download. Map {{$json.id}} and save the binary as data. Async transcription with VLM Run Add VLM Run node. Operation: video. Domain: video.transcription. Enable Process Asynchronously and set Callback URL to your Webhook path (for example /transcript-video). Add your VLM Run API key. Webhook to receive results Add Webhook node with method POST and path /transcript-video. This is the endpoint VLM Run calls when the job completes. Use When Last Node Finishes or respond via a Respond node if you prefer. Append to Google Sheets Add Google Sheets node with Append. Point to your spreadsheet and sheet. Map: Video Name → the video identifier from the webhook payload Data → the transcript text or JSON from the webhook payload Connect Google Sheets OAuth2. Chat entry point and Agent Add Chat Trigger to receive user questions. Add AI Agent and connect: a Chat Model (for example OpenAI Chat Model) the Google Sheets Tool to read relevant rows In the Agent system message, instruct: Use the Sheets tool to fetch transcript rows matching the question Answer only from those rows Cite or reference row context as needed Test and activate Upload a sample video to the watched Drive folder. Wait for the callback to populate your sheet. Ask a question through the Chat Trigger and confirm the agent quotes only from the retrieved rows. Activate your template and let it automate the task. How to take this further Team memory:** Ask “What did we decide on pricing last week?” and get the exact clip and answer. Study helper:** Drop classes in, then ask for key points or formulas by topic. Customer FAQ builder:** Turn real support calls into answers your team can reuse. Podcast highlights:** Find quotes, tips, and standout moments from each episode. Meeting catch-up:** Get decisions and action items from any recording, fast. Marketing snippets:** Pull short, social-ready lines from long demos or webinars. Team learning hub:** Grow a searchable video brain that remembers everything. This workflow uses the VLM Run node for scalable, async video transcription and the AI Agent for grounded Q&A from Sheets, giving you a durable pipeline from upload to searchable answers with minimal upkeep. An n8n automation workflow template by Atik.

By iamvaar

Workflow Execution Video: https://youtu.be/VV4D2aiFXsY Prerequisites & Setup Before you begin, you need to gather a few key pieces of information: N2YO API Key: Go to https://www.n2yo.com/login/register/ and create a free account. Once registered, find and copy your API key. This key is used to request satellite data. Replace the enter-longitude, enter-latitude, enter-your-api-key in http node URL. Telegram Bot Credentials: You need a Telegram bot. You can create one by talking to the BotFather on Telegram. Bot Token: BotFather will give you a unique authorization token. This is like a password for your bot. Chat ID: You need the ID of the chat where the bot will send messages. You can get this by sending a message to your bot and then visiting https://api.telegram.org/bot<YourBOTToken>/getUpdates. Look for the chat -> id value in the response. Your Location Coordinates: Visit https://www.maps.ie/coordinates.html. Find your location on the map. Copy your Latitude and Longitude values. Node-by-Node Explanation This workflow is composed of five nodes that execute in a sequence. 1. Schedule Trigger Node Node Name:** Schedule Trigger Purpose:** This is the starting point of the workflow. It's designed to run automatically at a specific, recurring interval. Configuration:* The node is set to trigger *every 30 minutes**. This means the entire sequence of actions will be initiated twice every hour. 2. HTTP Request Node Node Name:** HTTP Request Purpose:** This node is responsible for fetching data from an external source on the internet. Configuration:** It sends a request to the N2YO API URL: https://api.n2yo.com/rest/v1/satellite/visualpasses/25544/... The numbers 25544 represent the NORAD ID for the International Space Station (ISS). You must replace enter-longitude, enter-latitude, and enter-your-api-key with the actual coordinates and API key you gathered during the setup. The result of this request is a block of data (in JSON format) containing information about upcoming satellite passes. 3. Code Node Node Name:** Readable Purpose:** This node uses JavaScript to process and reformat the raw data received from the HTTP Request node. Configuration:** The JavaScript code performs several actions: It extracts the details of the next upcoming satellite pass. It contains functions to convert timestamp numbers into human-readable dates and times (e.g., "10th October 2025, 14:30 UTC"). It calculates the time remaining until the pass begins (e.g., "in 2h 15m"). Finally, it constructs a formatted text message (alert) and calculates the number of minutes until the pass begins (timeinminutes), passing both pieces of information to the next node. 4. If Node Node Name:** If Purpose:** This node acts as a gatekeeper. It checks if a specific condition is met before allowing the workflow to continue. Configuration:** It checks the timeinminutes value that was calculated in the previous Code node. The condition is: Is timeinminutes less than or equal to 600? If the condition is true (the pass is 600 minutes or less away), the data is passed to the next node through the "true" output. If the condition is false, the workflow stops. 5. Telegram Node Node Name:** Send a text message Purpose:** This node sends a message to your specified Telegram chat. Configuration:** It is configured with your Telegram bot's credentials. The Chat ID is set to the specific chat you want the message to appear in. The content of the text message is taken directly from the alert variable created by the Code node. This means it will send the fully formatted message about the upcoming ISS pass. An n8n automation workflow template by iamvaar.