Browse 12,955 Workflows

By Christian Moises

Gmail AI Email Classifier & Notifier Since Gmail inboxes can quickly become cluttered, this workflow provides an automated AI-based email classification system. It listens for new emails, categorizes them using an AI classifier, applies Gmail labels, and sends you a Telegram notification with a quick summary. If you often miss urgent client messages or struggle with sorting work vs. promotions, this workflow ensures you never overlook important emails. Use case: Especially useful for professionals who receive a high volume of mixed emails (clients, work, promotions). The workflow automatically labels and notifies you of new emails based on their category. How It Works Trigger Input The workflow starts with the Gmail Trigger node, which listens for new incoming emails. By default, it polls every minute, but you can adjust the polling frequency. Email metadata (from, subject, body) is passed downstream. Example JSON input: { "from": "client@example.com", "subject": "Urgent project deadline", "text": "Please review the attached contract ASAP" } Classify Email (AI) The Classification Agent (powered by OpenAI via LangChain) receives the email data. It sorts the email into one of four categories: High Priority – urgent, time-sensitive Work Related – general work emails Promotions – newsletters, offers, sales Other – uncategorized emails The classifier uses a system prompt to ensure output is returned in JSON format for downstream processing. Apply Gmail Labels Based on classification, the workflow applies the corresponding Gmail label: High Priority → “Important + Starred” Work Related → “Work” (custom Gmail label) Promotions → “Promotions” (custom Gmail label) Each label must already exist in Gmail for the operation to work. Generate Notification The AI Agent (notification assistant) takes the classified email and rewrites it into a short, casual notification. Example notification: [High Priority] New email from client@example.com Subject: Urgent project deadline "Please review the attached contract ASAP" Send to Telegram The Telegram node sends the generated notification to your personal chat ID. Requires a Telegram bot created with @BotFather and your chat ID configured. How to Use Import this workflow into n8n. Set up Gmail OAuth2 credentials and connect your Gmail account. Create Gmail labels: High Priority, Work Related, Promotions. Set up a Telegram bot in @BotFather and copy your chatId into the node. Run the workflow — every new email will now be classified, labeled, and notified. Requirements n8n Gmail Trigger** with Gmail OAuth2 credentials OpenAI API key** configured for LangChain nodes Telegram bot** created via @BotFather with your chat ID Existing Gmail labels (Work, Promotions, etc.) Customizing This Workflow You can extend it by: Adding more categories** – e.g., “Finance,” “Personal,” or “Spam.” Changing the notification channel** – send to Slack, Discord, or SMS instead of Telegram. Adjusting classification rules** – edit the system prompt for finer-grained AI sorting. Changing polling frequency** – set Gmail Trigger to every 5 minutes instead of every minute. Expanding extracted fields** – include attachments, links, or CC addresses in the notification. An n8n automation workflow template by Christian Moises.

By Matheus Pedrosa

Workflow Overview Keeping API documentation updated is a challenge, especially when your endpoints are powerful n8n webhooks. This project solves that problem by turning your n8n instance into a self-documenting API platform. This workflow acts as a central engine that scans your entire n8n instance for designated webhooks and automatically generates a single, beautiful, and interactive HTML documentation page. By simply adding a standard Set node with specific metadata to any of your webhook workflows, you can make it instantly appear in your live documentation portal, complete with code examples and response schemas. The final output is a single, callable URL that serves a professional, dark-themed, and easy-to-navigate documentation page for all your automated webhook endpoints. Key Features: Automatic Discovery:** Scans all active workflows on your instance to find endpoints designated for documentation. Simple Configuration via a Set Node:** No custom nodes needed! Just add a Set node named API_DOCS to any workflow you want to document and fill in a simple JSON structure. Rich HTML Output:** Dynamically generates a single, responsive, dark-mode HTML page that looks professional right out of the box. Interactive UI:** Uses Bootstrap accordions, allowing users to expand and collapse each endpoint to keep the view clean and organized. Developer-Friendly:** Automatically generates a ready-to-use cURL command for each endpoint, making testing and integration incredibly fast. Zero Dependencies:** The entire solution runs within n8n. No need to set up or maintain external documentation tools like Swagger UI or Redoc. Setup Instructions: This solution has two parts: configuring the workflows you want to document, and setting up this generator workflow. Part 1: In Each Workflow You Want to Document Next to your Webhook trigger node, add a Set node. Change its name to API_DOCS. Create a single variable named jsonOutput (or docsData) and set its type to JSON. Paste the following JSON structure into the value field and customize it with your endpoint's details: { "expose": true, "webhookPath": "PASTE_YOUR_WEBHOOK_PATH_HERE", "method": "POST", "summary": "Your Endpoint Summary", "description": "A clear description of what this webhook does.", "tags": [ "Sales", "Automation" ], "requestBody": { "exampleKey": "exampleValue" }, "successCode": 200, "successResponse": { "status": "success", "message": "Webhook processed correctly." }, "errorCode": 400, "errorResponse": { "status": "error", "message": "Invalid input." } } Part 2: In This Generator Workflow n8n API Node: Configure the GetWorkflows node with your n8n API credentials. It needs permission to read workflows. Configs Node: Customize the main settings for your documentation page, like the title (name_doc), version, and a short description. Webhook Trigger: The Webhook node at the start (default path is /api-doc) provides the final URL for your documentation page. Copy this URL and open it in your browser. Required Credentials: n8n API Credentials: To allow this workflow to read your other workflows. An n8n automation workflow template by Matheus Pedrosa.

By Muhammad Bello

Description This n8n template demonstrates how to turn raw YouTube comments into research-backed content ideas complete with hooks and outlines. Use cases include: Quickly mining a competitor’s audience for video ideas. Generating hooks and outlines for your own channel’s comments. Validating content opportunities with live audience feedback. Good to know Apify is used to scrape YouTube comments (requires an API token). GPT-4.1-mini is used for both filtering and content generation. Tavily provides fresh research to ground the AI’s responses. All outputs are stored in Google Sheets, making it easy to manage and track ideas. How it works Trigger – Paste a YouTube URL into the chat trigger. Scrape Comments – Apify fetches all comments and metadata. Filter – GPT-4.1-mini decides if each comment could inspire a content idea. Store – Comments and “Yes/No” decisions are appended to Google Sheets. Research & Enrich – For “Yes” comments, Tavily provides context, and GPT generates a topic, hook, and outline. Update Sheet – The same row in Google Sheets is updated with enriched fields. Google Sheets Setup Your Google Sheet should include these columns (in this order): id | text | author | likes | isIdea | topic | research | hook | outline id** – unique identifier for each comment text** – the full YouTube comment author** – commenter’s name/handle likes** – number of likes on the comment isIdea** – “Yes” or “No” depending on GPT filter topic** – extracted video topic research** – 300–500 word background from Tavily hook** – engaging opening sentence for a video outline** – structured video outline Setup Steps Connect your Apify, OpenAI, Tavily, and Google Sheets credentials in n8n. Point the Google Sheets nodes to your own document and ensure the above headers exist. Replace sample API keys with your own stored in n8n Credentials. Time to set up: \~15–25 minutes for a first-time n8n user (less if you already have credentials handy). Customizing this workflow Filter logic** – Loosen the GPT filter to allow borderline ideas, or tighten it to only accept the best ones. Research depth** – Change Tavily’s search depth (e.g., depth: basic vs depth: advanced) to control how detailed the background research is. Notification channels* – Send new “Yes” ideas directly to *Slack* (#content-ideas), *Notion* (your content board), or *Email** (notify the content manager instantly). Alternative outputs** – Instead of hooks/outlines, generate: A script draft for YouTube Shorts. Blog post angles based on the same audience comments. A poll question for community engagement. An n8n automation workflow template by Muhammad Bello.

By Louis

📬 What this workflow does Every morning → fetch 3 French economy RSS feeds → keep fresh items → AI rewrites into short summaries → send a nice HTML email newsletter. 🔄 Flow (high level) ⏰ Trigger at 07:00 📰 Fetch RSS (Le Monde, Usine Nouvelle, Le Figaro) ⛔ Filter → keep only recent items 🔢 Sort newest first ✂️ Limit 2 per source ➕ Merge 🤖 AI summary (title + paragraph) 🏷 Normalize fields (title, source, link…) 📦 Aggregate arrays 📧 Send via Outlook (HTML template) 🧩 Node notes Trigger** → 07:00 daily (check timezone). RSS Read** → feeds OK, but UsineNouvelle is http (redirects fine). If** nodes → ❗ currently after $today → keeps only future dates. Fix: For today only: after $today.startOf('day') For last 24h: after $now.minus({ hours: 24 }) Sort + Limit** → newest 2 per feed. Merge** → combine up to 6 items. AI agent** → prompt uses ` … needs closing ` ✅ Edit Fields** → maps source domains → nice labels (“Le Monde” etc). Aggregate** → arrays for email template. Outlook email** → HTML newsletter (mobile-friendly). ⚡ Quick wins 🕒 Fix the date filter logic (today/24h). 📝 Fix closing tag in AI prompt (``). 🌍 Add User-Agent header in RSS nodes (avoid 403). 🔁 Remove duplicates on link. ⏳ Mind the server timezone vs your audience. An n8n automation workflow template by Louis.

By WeblineIndia

🗓 Preventive Maintenance Scheduler via ICS Email (n8n | Google Sheets | Gmail) This workflow automatically reads your daily preventive maintenance schedule from Google Sheets and sends each assigned team member a personalized calendar invite (.ICS) as an email attachment. No more manual reminders or copying events — your operations and field teams will always be on schedule with clear, actionable reminders! Who’s it For Maintenance teams at plants, renewable sites, factories. Facility and operations managers. Any field crew, service team or org using Google Sheets and email for coordination. Businesses wanting reliable, zero-touch preventive maintenance notifications. How it Works Daily Trigger: Workflow runs automatically every morning at 7:00 AM. Read Maintenance Tasks: Pulls all scheduled maintenance for today from Google Sheets. Generate ICS Data: Prepares universal calendar event details: summary, location, time, assignee, etc. Create ICS File: Converts event data into a standard .ics calendar invite file with correct timings and description. Send Calendar Invite Email: Sends a personalized email to each assignee, with the .ics file attached — ready to add to Outlook, Gmail or mobile calendar. How to Set Up Import the workflow JSON into your n8n instance. Set up connections in n8n: Authenticate Google Sheets (read access) and Gmail (send access). Format your Google Sheet with headers: date, asset, task, location, email Activate the workflow. It runs daily on schedule. You can test it manually for validation. Each day: Team members with tasks scheduled for that date are sent their personalized event invite. Requirements | Tool | Purpose | |-----------------|---------------------------------------| | n8n Instance | Run and schedule the automation | | Google Sheets | Source of maintenance schedule/tasks | | Gmail (or SMTP) | Email platform to send calendar files | How to Customize | Customization | How | |----------------------------------------|------------------------------------------------------------| | Change calendar invite/event wording | Edit title or description in the "Create ICS File" node | | Adjust event start/end times | Modify time logic in "Generate ICS Data" node | | Change daily send time | Tweak time in "Daily Trigger" node | | Use a different email provider (SMTP) | Swap Gmail node for SMTP node; link correct credentials | | Add extra notifications (SMS/Slack) | Add appropriate node after or before Send Email node | Add‑ons | Add-on | Description | |-------------------------|----------------------------------------------| | Recurring Tasks | Automate repeated tasks via your sheet/setup | | Email Logging | Log sent invites in another sheet/db | | WhatsApp/SMS Alerts | Add Twilio or WhatsApp for instant alerts | | Manager Summary | Send daily reports or dashboards to leads | | Pre-alerts | Add reminder emails 1hr / 1 day before event | Use Case Examples Wind turbine engineers receive daily calendar invites for inspections. Solar O&M operators are automatically reminded for inverter cleaning via calendar sync. Facility staff gets scheduled reminders for HVAC or safety checks without manual admin. Managers have a clear audit trail of which reminders were sent on time. Common Troubleshooting | Issue | Possible Cause | Solution | |-------------------------------------|---------------------------------------|-------------------------------------------------------| | No email received | Gmail/SMTP misconfigured | Check node credentials, token or SMTP settings | | Calendar file comes as .txt | Wrong file type/extension/MIME | Ensure "Create ICS File" outputs .ics and text/calendar | | No invites sent for today | No matching rows in Google Sheet | Check date/value format; add sample data for today | | Google Sheets returns error | Wrong Sheet ID/tab, access issue | Confirm correct Google Sheet is linked and shared | | Event time/zone is incorrect | Code node’s time logic not matching | Adjust start/end time settings in the code node | Need Help? Want guided setup, advanced reporting, Outlook synchronization or a full preventive maintenance dashboard? 👉 Contact WeblineIndia — Your n8n Automation partner for smart preventive maintenance and calendar-driven ops!. An n8n automation workflow template by WeblineIndia.

By WeblineIndia

Send daily applicant digest by role from Gmail to hiring managers with Google Gemini This workflow automatically collects all new job application emails from your Gmail labeled as applicants in the last 24 hours. Every day at 6:00 PM (Asia/Kolkata), it extracts structured details (name, email, phone, role, experience, skills, location, notice, summary) from each applicant (using Gemini AI or OpenAI). It then groups applicants by role and manager, compiles a neat HTML table digest for each manager and emails them a single summary — so hiring managers get everything they need, at a glance, in one place. Who’s It For Recruiters and hiring managers tired of digging through multiple application threads. Small HR teams / agencies not yet on a full applicant tracking system. Anyone wanting a consolidated, role-targeted applicant update each day. Teams that want to automate candidate triage using Google Workspace and AI. How It Works Schedule Trigger (6PM IST): Runs automatically at 18:00 India time. Fetch Applicant Emails: Reads Gmail for emails labeled 'applicants' from the past 24 hours. Prepare Email Text: Converts email content to plain text for reliable AI extraction. Extract Applicant Details: Gemini/OpenAI extracts applicant’s info in structured JSON. Assign Manager Emails: Routes each applicant to the correct manager via role→email mapping or fallback. Group & Build HTML Tables: Organizes applicants by manager and role, builds summary tables. Send Digest to Managers: Sends each manager one HTML summary email for their new applicants. How to Set Up Create/verify Gmail label applicants and set up filters to route job emails there. Import the workflow: Use your Google/Gmail and Gemini/OpenAI accounts as credentials. Configure connections: Gmail with OAuth2 (IMAP not required, uses Gmail API) Gemini or OpenAI API key for extraction Set role→manager mapping in the “Assign Manager Emails” node (just edit the map!). Adjust time / defaults: Edit schedule and fallback email if you wish. Test it: Send yourself a test application, label it, check workflow logs. Requirements Gmail account (with OAuth2 enabled and 'applicants' label set up) Gemini or OpenAI API key for structured AI extraction n8n instance (self-hosted or cloud) SMTP credentials (if using direct email instead of Gmail node) At least one valid hiring manager email mapped to a role How to Customize the Workflow Centralize config with a Set node (label name, fallback/manager email, model name, schedule). Add attachment-to-text conversion for applications with resume attachments. Normalize role names in the mapping code for more robust routing. Enable additional delivery: Slack, Teams, Google Sheets log, extra Cron for mid-day urgents. Refine AI extraction prompt for specific fields (add portfolio URL, etc.). Change schedule for daily, weekly or per-role timing. Add‑Ons / Extensions Resume Text Extraction:** Add PDF/DOCX to text parsing for attachment-only applications. ChatOps:** Send the summary to Slack or Teams channels along with/instead of email. Applicant Logging:** Auto-log every applicant/action into Google Sheets, Notion or Airtable. Multi-timezone:** Duplicate/modify the Cron trigger for different manager regions or urgency levels. Use Case Examples Tech Hiring:** Java, Python, Frontend candidates are automatically routed to their respective leads. Small Agency:** All applications summarized for reviewers, with per-role breakdowns. HR Operations:** Daily rollups sent before hiring sync, facilitating fast decision-making. Common Troubleshooting | Issue | Possible Cause | Solution | |-----------------------------------------|----------------------------------------------------------|-------------------------------------------------------------| | No emails processed | No 'applicants' label or wrong time window | Check Gmail filters and adjust search query in fetch node | | All digests go to fallback manager | Incorrect or missing role → manager mapping | Normalize role text in assignment node, expand map | | AI Extraction returns bad/missing JSON | Wrong prompt, high temperature or missing field names | Tighten prompt, lower temperature, check example response | | Duplicate/Old Emails appear | Date filter not correct | Use 'newer_than:1d' and keep 'mark as read' in email node | | SMTP/Gmail Send errors | Auth problem, quota or app password missing | Use OAuth2, check daily send caps and app password settings | | Blank or partially filled summary table | AI unable to parse poorly formatted/empty email | Improve sender email consistency, add fallback handling | | Attachments not processed | No attachment extraction node | Add attachment-to-text parsing before AI node | Need Help? If you get stuck, need help customizing a mapping or adding nodes or want to integrate extra steps (e.g., resume text, Slack), just ask! We're happy to guide you step by step, review your workflow, or help you troubleshoot any errors. Contact WeblineIndia — Your n8n Automation partner!. An n8n automation workflow template by WeblineIndia.

By Evoort Solutions

📊 GST Data Analytics Automation Flow with Google Docs Reporting Description: Streamline GST data collection, analysis, and automated reporting using the GST Insights API and Google Docs integration. This workflow allows businesses to automate the extraction of GST data and directly generate formatted reports in Google Docs, making compliance easier. ⚙️ Node-by-Node Explanation On form submission Triggers the automation whenever a user submits the GST-related data (like GSTIN) via a web form. It collects all necessary input for further processing in the workflow. Fetch GST Data Using GST Insights API Sends a request to the GST Insights API to fetch GST data based on the user's input. This is done via a POST request that includes the required authentication and the inputted GSTIN. Data Reformatting This node processes and structures the raw GST data received from the API. The reformatting ensures only the essential information (e.g., tax summaries, payment status, etc.) is extracted for reporting. Google Docs Reporting Generates a Google Docs document and auto-populates it with the reformatted GST data. The report is structured in a clean format, ready for sharing or downloading. 💡 Use Cases Tax Consultants & Agencies:** Automate the GST insights and reporting process for clients by extracting key metrics directly from the GST Insights API. Accountants & Auditors:** Streamline GST compliance by generating automated reports based on the most current data from the API. E-commerce Platforms:** Automatically track GST payments, returns, and summaries for each sale and consolidate them into structured reports. SMEs and Startups:** Track your GST status and compliance without the need for manual intervention. Generate reports directly within Google Docs for easy access. 🎯 Benefits of this Workflow Automated GST Data Collection:* Fetch GST insights directly using the *GST Insights API** without manually searching through different resources. Google Docs Integration:** Automatically generate customized Google Docs reports with detailed GST data, making the reporting process efficient. Error-Free Data Analysis:** Automates data extraction and reporting, significantly reducing the risk of human errors. Customizable Reporting:** Customize the flow for various GST-related data such as payments, returns, and summaries. Centralized Document Storage:** All GST reports are saved and managed within Google Docs, ensuring easy collaboration and access. Quick Note: The GST Insights API provides detailed GST data analysis for Indian businesses. It can extract crucial data like returns, payments, and summaries directly from the GST system, which you can then use for compliance and reporting. Would you like to explore the API further or need help with other integrations? 🔑 How to Get Your API Key for GST Insights API Visit the API Page: Go to the GST Insights API on RapidAPI. Sign Up/Login: Create an account or log in if you already have one. Subscribe to the API: Click "Subscribe to Test" and choose a plan (free or paid). Copy Your API Key: After subscribing, your API Key will be available in the "X-RapidAPI-Key" section under "Endpoints". Use the Key: Include the key in your API requests like this: -H "X-RapidAPI-Key: YOUR_API_KEY". An n8n automation workflow template by Evoort Solutions.

By Khairul Muhtadin

Turn rough ideas into polished system prompts. The System Prompt Generator takes human input through an n8n webhook, runs it through a small Set/Prepare pipeline and Unli.dev chat completions, and returns a complete, repeatable system prompt blueprint with persona, mission, rules, output format, and designer notes. Less arguing about wording, more shipping features. And consistent LLM behavior across all your apps. Last updated: September 2026. Why Use System Prompt Generator? Fix the pain of inconsistency.** One blueprint, same behavior everywhere. Improve outcomes measurably.** Structured prompts beat improvised ones. Competitive advantage:** Standardize AI behavior with enforceable rules and templates, so product voice and constraints stay consistent across teams. Perfect For Prompt Engineers:** Systematize prompt design and handoffs. Product Managers:** Lock down expected AI behaviors before launch. Developers & AI Ops:** Automate prompt generation for testing and deployments. How It Works Trigger: Incoming HTTP POST to the webhook path systempromptgenerator kicks everything off. Process: Webhook → Set Prompt/Model (map incoming fields) → Prepare API Body (compose messages) → Unli.Dev (Chat Completions) → Extract Answer → Respond to Webhook. Smart Logic: Unli.dev (chat completions) runs a single-turn generation using the embedded system-template that builds persona, operational protocol, rules, output format, and designer notes automatically. Output: The generated system prompt (with Designer's Notes) is returned in the webhook response for immediate use in your app or CI pipeline. Security Note: Swap in your Unli.dev API key under the HTTP header auth credential. Don't share keys in Slack. Seriously. Requirements Active n8n instances Unli.dev API key / account HTTP Header Auth credential configured in n8n Optional: Postman or curl for testing Level Up Ideas Add a lightweight front-end form** to let non-technical PMs generate prompts and preview outputs Add validation rules** or automated tests that run generated system prompts against sample user queries to catch unwanted behavior early Quick Answers How do I call it? Send an HTTP POST to the systempromptgenerator webhook path with your idea and model fields. What comes back? A complete system prompt with Designer's Notes, right in the webhook response. What do I need? An Unli.dev API key stored as an HTTP Header Auth credential. Made by: khmuhtadin Category: System Prompt, Unli.dev Need custom work? Contact me Additional info Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/. An n8n automation workflow template by Khairul Muhtadin.

By Sankalp Dev

This automation workflow transforms Meta advertising data into executive ready presentation decks, eliminating manual report creation while ensuring stakeholders receive consistent performance insights. It generates professional Google Slides presentations from your ad campaigns and delivers them automatically via email to designated recipients. By combining scheduled data extraction with AI-powered analysis and automated presentation building, you'll receive polished, actionable reports that facilitate strategic advertising decisions and client communication Key Features: Scheduled automated summary deck generation (daily, weekly, or monthly) AI powered data analysis using advanced language models Intelligent presentation generation with actionable recommendations Direct email delivery of formatted summary decks Prerequisites: GoMarble MCP account and API access Anthropic account Google Slides, Google Drive & Gmail accounts n8n instance (cloud or self-hosted) Configuration Time: ~15-20 minutes Step By Step Setup: 1. Connect GoMarble MCP to n8n Follow the integration guide: GoMarble MCP Setup Configure your Meta Ads account credentials in GoMarble platform 2. Configure the Schedule Trigger 3.Customize the Ad Account Settings. Update the account name to match your ad account name. 4. Customise the Report Prompt (Although the workflow includes a pre configured template report prompt) Define specific metrics and KPIs to track Set analysis parameters and report format preferences 5. Set up AI Agent Configuration Configure Anthropic Claude model with your API credentials Connect the GoMarble MCP tools for Meta advertising data 6. Configure Google Services Integration Set up Google Slides OAuth2 API for presentation creation Configure Google Drive OAuth2 API for file management Link Gmail OAuth2 for automated email delivery 7. Customize Email Delivery Set recipient email addresses for stakeholders Customize email subject line and message content Advanced Configuration Modify report prompt to include specific metrics and KPIs Adjust slide content structure (5-slide format: Executive Snapshot, Channel KPIs, Top Campaigns, Under-performers, Action Recommendations) What You'll Get Automated Presentation Creation: Weekly Google Slides decks generated without manual intervention Professional Ads Analysis: Executive-ready performance summaries with key metrics and insights Structured Intelligence: Consistent 5-slide format covering spend, ROAS, campaign performance, and strategic recommendations Direct Stakeholder Delivery: Presentations automatically emailed as attachments to specified recipients Data-Driven Insights: AI-powered analysis of campaign performance with actionable next steps Scalable Reporting: Easy to modify timing, recipients, or content structure as business needs evolve Perfect for marketing teams, agencies, and business owners who need regular Meta advertising performance updates delivered professionally without manual report creation. An n8n automation workflow template by Sankalp Dev.

By Mohammadreza azari

Google Search Console – Discover New Keywords (Last 7 Days) This n8n template demonstrates how to identify new queries in Google Search Console that had no impressions in the past but appeared for the first time in the last 7 days. It also segments them into two groups: queries with impressions but no clicks yet (Zero Click) and queries that already have clicks (Has Click). Use cases include: Finding emerging SEO opportunities. Identifying keywords where you already get impressions but need to optimize for clicks. Tracking newly discovered queries week over week. Good to know This workflow requires a connected Google Search Console account. You can adjust the date ranges in the Compare search analytics node to suit your needs. Works best when scheduled weekly, but in this template we start with manual execution for flexibility. How it works Manual Start – Run the workflow manually to fetch fresh data. Compare Search Analytics – Compares the last 7 days against a custom reference period in Google Search Console. Filter (No Past Impressions) – Keeps only queries that had zero impressions in the reference period. Zero Click – Filters queries with impressions but no clicks. Has Click – Filters queries with impressions and clicks. The final output is two clean data sets: Zero Click queries**: impressions but no clicks → improve meta descriptions, titles, or content relevance. Has Click queries**: new queries already generating clicks → consider creating supporting content and optimizing further. How to use Start with the Manual Start node. Add your Google Search Console credentials in the Compare search analytics node. Optionally, replace the Manual Start with a Schedule Trigger (e.g., weekly) to automate monitoring. Export results or connect them to Slack, Email, or Google Sheets for reporting. Requirements Google Search Console account** (with property access). n8n instance with the Google Search Console integration enabled. Customising this workflow Adjust the date ranges in the compare node (e.g., last 30 days vs. previous 30 days). Replace the output branches with integrations like Slack, Notion, or Google Sheets to automatically deliver keyword reports. Extend the workflow with additional filters, such as filtering by CTR, country, or device. An n8n automation workflow template by Mohammadreza azari.

By YungCEO

What It Does Are you drowning in daily operational chaos, desperately trying to juggle sales, projects, content, and client communication? Imagine an AI brain that handles it all, freeing you to lead your business, not just manage it. The Kingly Kreationz CEO Agent is your ultimate n8n automation, a sophisticated AI orchestrator that unifies your entire business, from lead nurturing to calendar scheduling, under one intelligent command center. Stop wasting precious hours on manual delegation and scattered data. This master workflow transforms your operations into a seamless, high-converting machine, ensuring unparalleled efficiency and growth. ⚙️ Key Features 👑 Master AI Orchestration: Centralized AI brain delegates tasks across CRM, projects, content, and social media. 🗣️ Voice & Text Command Input: Interact naturally via Telegram, eliminating manual data entry. 🔗 Seamless Multi-Platform Integration: Connects Notion, Gmail, Google Calendar, Apify, Supabase, and more. 📈 Intelligent Task Delegation: Automatically routes requests to specialized AI agents for maximum efficiency. 📊 Automated Operational Logging: Every action and outcome is recorded in Notion for complete oversight and accountability. 😩 Pain Points Solved Tired of managing a dozen different tools and platforms just to keep your business running? Struggling to delegate tasks efficiently and ensure follow-through across your team? Losing leads or missing opportunities due to fragmented communication and data? Buried under manual administrative work instead of focusing on strategic growth? Wishing you had a true AI co-pilot to streamline every facet of your operations? 📦 What’s Included 1 Kingly Kreationz CEO Agent N8N Workflow (JSON file) Comprehensive Step-by-Step Setup Guide 🚀 Call to Action Stop managing. Start leading. Empower your business with AI. Grab the Kingly Kreationz CEO Agent today! 🏷️ Optimized Tags ai agent, n8n automation, ceo assistant, business management, workflow automation, notion integration, crm automation, task delegation, ai orchestrator, digital product, telegram bot, productivity tool, google workspace automation. An n8n automation workflow template by YungCEO.

By Oneclick AI Squad

This automated n8n workflow monitors real-time cryptocurrency prices using CoinGecko API and sends smart alerts when price conditions are met. It supports multi-coin tracking, dynamic conditions, and instant notifications via Email, Telegram, and Discord. Good to Know Reads crypto watchlist data from Google Sheets. Monitors prices at defined intervals (24/7 monitoring). Handles upper and lower price limits with direction-based alerts (above, below, both). Implements cooldown logic to avoid duplicate alerts. Updates last alert price and timestamp in Google Sheets. Supports multiple alert channels: Email, Telegram, Discord. Uses CoinGecko API for price data (Free tier supported). How It Works 24/7 Crypto Trigger – Runs every minute (or custom interval) to check latest prices. Read Crypto Watchlist – Fetches symbols and conditions from Google Sheets. Parse Crypto Data – Converts Google Sheet data into structured JSON. Fetch Live Crypto Price – Uses CoinGecko API to get latest market price for each coin. Smart Crypto Alert Logic – Compares live price with upper/lower limits and evaluates conditions: Above – Trigger alert if price > upper\_limit. Below – Trigger alert if price < lower\_limit. Both – Trigger alert if either condition is met. Implements cooldown\_minutes to prevent repeated alerts. Check Crypto Alert Conditions – Validates alerts before sending notifications. Send Crypto Email Alert – Sends email alert if condition is true. Send Telegram Crypto Alert – Sends Telegram alert. Send Discord Crypto Alert – Sends Discord alert. Update Crypto Alert History – Updates last_alert_price and last_alert_time in Google Sheet. Crypto Alert Status Check – Ensures alert process completed successfully. Success Notification – Sends confirmation message on success. Error Notification – Sends an error alert if something fails. Google Sheet Columns (A-G) | Column | Description | | ------ | ---------------------------------- | | A | symbol (BTC, ETH, SOL, etc.) | | B | upper_limit (e.g., 45000) | | C | lower_limit (e.g., 40000) | | D | direction (both / above / below) | | E | cooldown_minutes (e.g., 10) | | F | last_alert_price (auto-updated) | | G | last_alert_time (auto-updated) | How to Use Import the workflow into n8n. Configure Google Sheets credentials and link your watchlist sheet. Add your CoinGecko API endpoint in the Fetch Price node (Free tier). Set up Email, Telegram, and Discord credentials for notifications. Test with sample data: Example: BTC, upper\_limit=45000, lower\_limit=40000, direction=both. Execute the workflow and monitor alerts. Requirements n8n environment with execution permissions. Google Sheets integration (with API credentials). CoinGecko API (Free tier supported). Notification channels: Email (SMTP settings in n8n). Telegram Bot Token. Discord Webhook URL. Customizing This Workflow Add more coins in Google Sheet. Modify alert conditions (e.g., percentage change, moving averages). Add SMS or WhatsApp notifications. Integrate with Slack or Microsoft Teams. Use AI-based price predictions for smarter alerts. An n8n automation workflow template by Oneclick AI Squad.

By Khairul Muhtadin

unli.dev + n8n + Telegram Image Analyzer turns images sent to your Telegram bot into clean, Markdown-formatted transaction text using unli.dev Vision API. Instead of typing numbers and dates manually, the workflow downloads the photo, converts it to base64, analyzes it via API, and replies in-chat with extracted details. Faster input, fewer errors. Last updated: September 2026. Why Use Image Analyzer? Save time:** Images processed in seconds, manual entry down by up to 90%. Solve pain points:** No more blurry screenshot frustration. Clean Markdown transactions back. Faster outcomes:** Per-image turnaround under 15s. Competitive edge:** Staff and customers get structured feedback instantly. Perfect For Small business owners:** Capture receipts and payments quickly. Accountants/bookkeepers:** Intake client receipts with fewer typos. Ops/support teams:** Turn messy screenshots into actionable records. How It Works Trigger: Telegram bot receives photo. Process: Convert to base64 & prepare request. Smart Logic: Call unli.dev Vision API for text extraction. Output: Send Markdown result back to Telegram. Optional: Save structured data to Google Sheets, Airtable, or DB. Quick Setup Import workflow JSON to your n8n instance. Add credentials: Telegram bot + unli.dev API key. Customize the system prompt (default: extract the transaction in Markdown). Test by sending a real photo to your bot. You’ll Need n8n instance Telegram bot token unli.dev Vision API key Optional: Google Sheets / Airtable for storage Quick Answers What do I send? Any photo with transaction details to your Telegram bot. What comes back? Clean Markdown-formatted transaction text, right in the chat. Can it store results? Yes. Optionally save structured data to Google Sheets, Airtable, or a database. Made by: khmuhtadin Category: Image Analysis Need custom work? Contact me Additional info Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/. An n8n automation workflow template by Khairul Muhtadin.

By Davide Boizza

This workflow automates the process of validating email addresses stored in a Google Sheets file by using the Anymail Finder API. Key Advantages ✅ Automated Lead Validation No need for manual copy-paste or bulk uploads emails are verified directly inside your existing Google Sheets. 🔎 Improved Data Quality Ensures your CRM or outreach campaigns only target valid and deliverable email addresses, reducing bounce rates. 🔄 Real-Time Updates Results are automatically updated in the spreadsheet, making it easy for your team to see which leads are safe to contact. 📈 Improves lead quality for outreach, reduces bounce rates Of course. Here is a description of the provided n8n workflow. Workflow Description: Verify Leads Email Address with Anymail Finder This workflow automates the process of checking the validity of email addresses from a Google Sheets list using the Anymail Finder API and writing the results back to the sheet. How It Works The workflow operates in a loop to process a list of leads from a Google Sheet one by one. Manual Trigger: The workflow is started manually by a user within n8n. Get Leads: The "Get Leads" node reads data from a specified Google Sheet. It is configured with a filter to only fetch rows where the "VERIFY" column is empty, ensuring it only processes new leads that haven't been checked yet. Loop Over Items: The "Split In Batches" node is used to iterate over each row (lead) retrieved from the Google Sheet. This sends each lead individually to the next node for processing. Check Email Status: For each lead, the "HTTP Request" node sends a POST request to the Anymail Finder API (/v5.1/verify-email). The email address from the current sheet row ($json["EMAIL "]) is sent in the request body. Update Email Status: The response from Anymail Finder (which contains the verification status) is received. The "Update email status" node then takes this result and writes it back to the "VERIFY" column of the original Google Sheet. It uses the row_number to identify the correct row to update, ensuring data is placed accurately. Set Up Steps To use this workflow, you need to configure the following credentials and nodes: Google Sheets Credentials: Create a credential named "Google Sheets account" of type OAuth2. Follow n8n's guide to authenticate with Google Sheets. This will give the workflow permission to read from and write to your spreadsheet. Anymail Finder Credentials: Create a credential named "Anymail Finder" of type HTTP Header Auth. In the "Name" field, enter Authorization (or the header name required by Anymail Finder's API documentation). In the "Value" field, enter your Anymail Finder API key (in the format YOUR_API_KEY). Configure Google Sheet: Ensure your Google Sheet has at least the following columns: COMPANY NAME, EMAIL (note the space), and VERIFY. The "VERIFY" column must be empty for rows you want to verify. The "Get Leads" node is filtered to only process rows where this column is blank. Activate and Execute: Once the credentials are set and the sheet ID is configured, activate the workflow. Click on the "Manual Trigger" node and execute the workflow. It will begin processing all leads with an empty "VERIFY" field. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Stéphane Heckel

Keep your Google Sheets contacts in sync with SeaTable Update or Insert records in SeaTable How it works Use a Google Sheet as your central contact list. For each contact in the sheet: Check if the record already exists in SeaTable (based on email). If it exists → update the record. If it doesn’t → insert the new contact. How to use Copy the Google Sheet Template Link. Get the Google Sheet ID (the string between d/ and /edit). In the workflow, set the Sheet ID in the settings node. In SeaTable, create or update a base with a Table1 containing these fields: email firstname lastname company Configure your Google Sheets and SeaTable credentials in n8n. Add your own contacts to the Google Sheet & run the workflow Requirements Google credentials (for Sheets access) SeaTable account (Cloud) n8n (tested on version 1.105.2, Ubuntu) Example use cases Maintain a central CRM-like database in SeaTable. Ensure consistent contact data when collecting leads in Google Sheets. Automate record deduplication (prevent duplicate entries). Need Help? Join the discussion here or contact me directly on LinkedIn. Ask the community in the n8n Forum. An n8n automation workflow template by Stéphane Heckel.

By Trung Tran

Automated SSL/TLS Certificate Expiry Report for AWS > Automatically generates a weekly report of all AWS ACM certificates, including status, expiry dates, and renewal eligibility. The workflow formats the data into both Markdown (for PDF export to Slack) and HTML (for email summary), helping teams stay on top of certificate compliance and expiration risks. Who’s it for This workflow is designed for DevOps engineers, cloud administrators, and compliance teams who manage AWS infrastructure and need automated weekly visibility into the status of their SSL/TLS certificates in AWS Certificate Manager (ACM). It's ideal for teams that want to reduce the risk of expired certs, track renewal eligibility, and maintain reporting for audit or operational purposes. How it works / What it does This n8n workflow performs the following actions on a weekly schedule: Trigger: Automatically runs once a week using the Weekly schedule trigger. Fetch Certificates: Uses Get many certificates action from AWS Certificate Manager to retrieve all certificate records. Parse Data: Processes and reformats certificate data (dates, booleans, SANs, etc.) into a clean JSON object. Generate Reports: 📄 Markdown Report: Uses the Certificate Summary Markdown Agent (OpenAI) to generate a Markdown report for PDF export. 🌐 HTML Report: Uses the Certificate Summary HTML Agent to generate a styled HTML report for email. Deliver Reports: Converts Markdown to PDF and sends it to Slack as a file. Sends HTML content as a formatted email. How to set up Configure AWS Credentials in n8n to allow access to AWS ACM. Create a new workflow and use the following nodes in sequence: Schedule Trigger: Weekly (e.g., every Monday at 08:00 UTC) AWS ACM → Get many certificates Function Node → Parse ACM Data: Converts and summarizes certificate metadata OpenAI Chat Node (Markdown Agent) with a system/user prompt to generate Markdown Configure Metadata → Define file name and MIME type (.md) Create document file → Converts Markdown to document stream Convert to PDF Slack Node → Upload the PDF to a channel (Optional) Add a second OpenAI Chat Node for generating HTML and sending it via email Connect Output: Markdown report → Slack file upload HTML report → Email node with embedded HTML Requirements 🟩 n8n instance (self-hosted or cloud) 🟦 AWS account with access to ACM 🟨 OpenAI API key (for ChatGPT Agent) 🟥 Slack webhook or OAuth credentials (for file upload) 📧 Email integration (e.g., SMTP or SendGrid) 📝 Permissions to write documents (Google Drive / file node) How to customize the workflow Change report frequency**: Adjust the Weekly schedule trigger to daily or monthly as needed. Filter certificates**: Modify the function node to only include EXPIRED, IN_USE, or INELIGIBLE certs. Add tags or domains to include/exclude. Add visuals**: Enhance the HTML version with colored rows, icons, or company branding. Change delivery channels**: Replace Slack with Microsoft Teams, Discord, or Telegram. Send Markdown as email attachment instead of PDF. Integrate ticketing**: Create a JIRA/GitHub issue for each certificate that is EXPIRED or INELIGIBLE. An n8n automation workflow template by Trung Tran.

By Shohani

Send daily inspirational quotes with AI translation to Telegram subscribers This n8n workflow creates an automated daily quote bot that fetches inspirational quotes, translates them using AI, adds emoji "stickers," and sends them to registered Telegram subscribers. Perfect for content creators, coaches, or anyone wanting to share daily motivation with their audience. Who's it for Content creators and social media managers Life coaches and motivational speakers Community managers running Telegram channels Anyone wanting to automate daily inspirational content Developers learning n8n automation with AI integration How it works The workflow operates on two main flows: Daily Quote Distribution: Schedule Trigger runs daily to fetch a random inspirational quote HTTP Request fetches quotes from the ZenQuotes API (free service) Google Gemini AI translates the quote to your target language and adds relevant emoji "stickers" Google Sheets retrieves the list of registered subscribers Telegram sends the formatted quote (original + translated + emojis) to all subscribers User Registration: Telegram Trigger listens for new messages to your bot Google Sheets automatically registers new users who interact with the bot Requirements Telegram Bot Token** - Create a bot via @BotFather on Telegram Google Gemini API** - For AI translation and emoji enhancement Google Sheets** - To store subscriber list (free Google account) ZenQuotes API** - Free, no API key required How to set up Create Telegram Bot: Message @BotFather on Telegram, create a new bot, and save the token Set up Google Sheets: Create a spreadsheet with columns: registered_users, date Configure Gemini API: Get your API key from Google AI Studio Update the Set Fields node: Configure your target language and bot preferences Test the workflow: Send a message to your bot to register, then manually trigger the quote sending How to customize the workflow Change target language**: Modify the AI prompt in the LLM Chain node to translate to any language Adjust sending schedule**: Update the Schedule Trigger to send quotes at your preferred time/frequency Customize quote sources**: Replace the HTTP Request with other quote APIs or your own content Add quote categories**: Enhance the AI prompt to categorize quotes (motivational, business, life, etc.) Include user preferences**: Expand Google Sheets to store user language preferences for personalized translations Good to know The workflow automatically handles new subscriber registration Supports MarkdownV2 formatting for rich text in Telegram Uses emoji "stickerization" to make quotes more engaging and visual Demo bot working with this workflow is @sgsbot on Telegram. An n8n automation workflow template by Shohani.

By Evoort Solutions

Automated SEO Website Audit with n8n, Google Docs & RapidAPI's SEO Analyzer Description: Use n8n to automate SEO audits with the Website SEO Analyzer and Audit AI from RapidAPI. Capture a URL, run a full audit, and export a structured SEO report to Google Docs — all without manual steps. ⚙️ Node-by-Node Explanation 🟢 formTrigger — On Form Submission Starts the workflow when a user submits a URL through a form. Collects the website to be analyzed. 🌐 httpRequest — Website Audit Sends the submitted URL to the Website SEO Analyzer and Audit AI via a POST request. Fetches detailed SEO data, including meta tags, keyword usage, and technical performance. 🧠 code — Reformat Transforms raw JSON from the Website SEO Analyzer and Audit AI into a structured Markdown summary. Organizes insights into sections like Metadata, Keyword Density, Page Performance, and Security. 📄 googleDocs — Add Data In Google Docs Automatically inserts the formatted SEO audit report into a pre-connected Google Docs file. Allows audit data to be easily shared, tracked, or archived. 🌟 Benefits ✅ Powered by **Website SEO Analyzer and Audit AI:** Leverage a reliable, cloud-based SEO tool via RapidAPI. 🔁 End-to-End SEO Workflow: Fully automates input, audit, formatting, and export to documentation. 📊 Human-Readable Reports: Translates raw API output into structured, insightful summaries. 📂 Centralized Documentation: Stores SEO audits in Google Docs for easy reference and historical tracking. 🚀 Use Cases 📈 SEO Agencies: Generate fast and consistent SEO audits using the Website SEO Analyzer and Audit AI — ideal for client reporting. 🏢 In-House Web Teams: Regularly audit corporate websites and track performance in a document-based SEO log. 🧲 Lead Generation for SEO Services: Offer real-time audits through a public form to attract and qualify leads. 📅 Monthly SEO Health Checks: Automate recurring site audits and log results using n8n and RapidAPI. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!. An n8n automation workflow template by Evoort Solutions.

By Intuz

This n8n template from Intuz provides a complete solution to automate the syncing of new subscribers from Google Sheets to MailerLite. It intelligently identifies and adds only new contacts, preventing duplicates and ensuring your email lists are clean and accurate. Who's this workflow for? Marketing Teams Email Marketers Small Business Owners Community Managers How it works 1. Read from Google Sheets: The workflow begins by reading all contact rows from your designated Google Sheet. 2. Check for Existing Subscribers: For each contact, it performs a search in MailerLite to check if a subscriber with that email address already exists. 3. Handle Duplicates: If the subscriber is found in MailerLite, the workflow stops processing that specific contact, preventing any duplicates from being created. 4. Create New Subscribers: If the contact is not found, the workflow proceeds to create a new subscriber in MailerLite, using all the details from the Google Sheet (like name, company, and country) and assigns them to the specified group. Setup Instructions 1. Google Sheets Setup: Connect your Google Sheets account to n8n. Create a sheet with the required columns: Email, first_name, last_name, Company, Country, and group_id. In the Get row(s) in sheet node, select your credentials and specify the Document ID and Sheet Name. 2. MailerLite Setup: Connect your MailerLite account to n8n using your API key. In both the Get a subscriber and Create subscriber... nodes, select your MailerLite credentials. Make sure the group_id values in your Google Sheet correspond to valid Group IDs in your MailerLite account. 3. Activate Workflow: Save the workflow and click "Execute workflow" to run the sync whenever you need to update your subscriber list. 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 Worflow Automation Click here- Get Started. An n8n automation workflow template by Intuz.

By Avkash Kakdiya

How it works This workflow automates the handling of new lead responses received in Gmail. It captures emails with a specific label, analyzes the message using AI to determine sentiment, intent, urgency, next action, and priority, and then decides whether follow-up is needed. If required, it creates tasks in HubSpot, notifies the sales team via Slack, and logs all details into Google Sheets for tracking. Step-by-step Trigger on New Lead Email Workflow starts whenever a new email with a defined Gmail label arrives. Captures the sender’s email, subject, message snippet, and timestamp. Normalize Email Data Standardizes Gmail fields into structured values: leadEmail (sender’s address) subject (email subject) message (email content snippet) source (Gmail) receivedAt (timestamp) AI-Powered Lead Analysis Uses OpenAI to analyze the lead’s message. Extracts: Sentiment (Positive / Neutral / Negative) Intent (Interested, Not Interested, Needs Info, Ready to Buy, Objection) Urgency (High / Medium / Low) Next Action (Call, Email, Demo, Quote, No Action) Summary (1–2 sentence description) Priority (Hot / Warm / Cold) Parsed results are merged with the original email data. Flags are added: needsFollowUp (true/false) isHighPriority (true/false) Decision: Needs Follow-Up? If AI suggests a follow-up action, the workflow continues. Otherwise, the process stops here. Create HubSpot Task Automatically creates a HubSpot CRM task for the sales team. Task includes email subject, body, and lead details. Notify Sales Team on Slack Sends a formatted message to Slack with key lead insights: Summary Lead email Priority Urgency Date of analysis Log Lead Data to Google Sheets Appends structured data to Google Sheets for record-keeping. Stores all fields: Email, Date, Subject, Message, Sentiment, Intent, Urgency, Next Action, Summary, and Priority. Why use this? Automates lead triage directly from Gmail. Saves time by using AI-powered analysis instead of manual review. Ensures no potential lead is missed by logging into Google Sheets. Provides instant sales team alerts on high-priority leads. Integrates seamlessly with HubSpot CRM for structured follow-up. Keeps your sales pipeline efficient, organized, and proactive. An n8n automation workflow template by Avkash Kakdiya.

By Automate With Marc

AI Agent MCP for Email & News Research Build a chat-first MCP-powered research and outreach agent. This workflow lets you ask questions in an n8n chat, then the agent researches news (via Tavily + Perplexity through an MCP server) and drafts emails (via Gmail through a separate MCP server). It uses OpenAI for reasoning and short-term memory for coherent, multi‑turn conversations. Watch build along videos for workflows like these on: www.youtube.com/@automatewithmarc What this template does Chat-native trigger: Start a conversation and ask for research or an email draft. MCP client tools: The agent talks to two MCP servers — one for Email work, one for News research. News research stack: Uses Tavily (search) and Perplexity (LLM retrieval/answers) behind a News MCP server. Email stack: Uses Gmail Tool to generate and send messages via an Email MCP server. Reasoning + memory: OpenAI Chat Model + Simple Memory for context-aware, multi-step outputs. How it works (node map) When chat message received → collects your prompt and routes it to the agent. AI Agent (system prompt = “helpful email assistant”) → orchestrates tools via MCP Clients. OpenAI Chat Model → reasoning/planning for research or email drafting. Simple Memory → keeps recent chat context for follow-ups. News MCP Server exposes: Tavily Tool (Search) and Perplexity Tool (Ask) for up-to-date findings. Email MCP Server exposes: Gmail Tool (To, Subject, Message via AI fields) to send or draft emails. The MCP Clients (News/Email) plug into the Agent, so your single chat prompt can research and then draft/send emails in one flow. Requirements n8n (Cloud or self‑hosted) OpenAI API key for the Chat Model (set on the node) Tavily, Perplexity, and Gmail credentials (connected on their respective tool nodes) Publicly reachable MCP Server endpoints (provided in the MCP Client nodes) Setup (quick start) Import the template and open it in the editor. Connect credentials on: OpenAI, Tavily, Perplexity, and Gmail tool nodes. Confirm MCP endpoints in both MCP Client nodes (News/Email) and leave transport as httpStreamable unless you have special requirements. Run the workflow. In chat, try: “Find today’s top stories on Kubernetes security and draft an intro email to Acme.” “Summarize the latest AI infra trends and email a 3‑bullet update to my team.” Inputs & outputs Input: Natural-language prompt via chat trigger. Tools used: News MCP (Tavily + Perplexity), Email MCP (Gmail). Output: A researched summary and/or a drafted/sent email, returned in the chat and executed via Gmail when requested. Why teams will love it One prompt → research + outreach: No tab‑hopping between tools. Up-to-date answers: Pulls current info through Tavily/Perplexity. Email finalization: Converts findings into send-ready drafts via Gmail. Context-aware: Memory keeps threads coherent across follow-ups. Pro tips Use clear verbs in your prompt: “Research X, then email Y with Z takeaways.” For safer runs, point Gmail to a test inbox first (or disable send and only draft). Add guardrails in the Agent’s system message to match your voice/tone. An n8n automation workflow template by Automate With Marc.

By Budi SJ

Automatically Import Research Papers using DOI URL from Telegram to Zotero This workflow allows you to automatically import research papers into your Zotero library by simply sending a DOI link through Telegram. It fetches metadata from reliable sources such as Crossref, DataCite, and Unpaywall, enriches the bibliographic details, attaches the best available full-text PDF when possible, and generates a concise summary of the abstract using an LLM before sending it back to Telegram. ✨ Key Features Telegram Integration** – Send a DOI link via Telegram bot to trigger the workflow. DOI Parsing** – Automatically detects and extracts DOI or arXiv identifiers from user messages. Metadata Fetching* – Retrieves bibliographic information from *Crossref, **DataCite, and Unpaywall. Smart PDF Finder** – Locates the best available PDF (publisher link, open access, or arXiv). Zotero Integration** – Creates a Zotero parent item with complete metadata and attaches the PDF link when available. Abstract Summarization** – Uses a basic LLM chain to generate a short and clear summary of the abstract. Telegram Feedback** – Sends the title, URL, and abstract summary back to the user in Telegram. 🔑 Required Credentials Telegram API** – To connect the workflow with your Telegram bot. Zotero API Key** – To create and update items in your Zotero library. OpenRouter API Key** – To enable the LLM for generating abstract summaries. (Optional) Email for Unpaywall API requests (recommended for stable access). 💡 Benefits Save time by automating manual research paper imports. Ensure high-quality metadata by combining multiple sources (Crossref, DataCite, Unpaywall). Get instant summaries of abstracts directly in Telegram for quick understanding. Keep your Zotero library organized with accurate titles, abstracts, authors, and tags. Quickly attach available full-text PDFs without manual searching. Improve your academic workflow by managing references and summaries directly from Telegram. An n8n automation workflow template by Budi SJ.

By Anna Bui

Automatically analyze n8n workflow errors with AI, create support tickets, and send detailed Slack notifications Perfect for development teams and businesses that need intelligent error handling with automated support workflows. Never miss critical workflow failures again! How it works Error Trigger captures any workflow failure in your n8n instance AI Debugger analyzes the error using structured reasoning to identify root causes Clean Data transforms AI analysis into organized, actionable information Create Support Ticket automatically generates a detailed ticket in FreshDesk Merge combines ticket data with AI analysis for comprehensive reporting Generate Slack Alert creates rich, formatted notifications with all context Send to Team delivers instant alerts to your designated Slack channel How to use Replace FreshDesk credentials with your helpdesk system API Configure Slack channel for your team notifications Customize AI analysis prompts for your specific error types Set up as global error handler for all your critical workflows Requirements FreshDesk account (or compatible ticketing system) Slack workspace with bot permissions OpenAI API access for AI analysis n8n Cloud or self-hosted with AI nodes enabled Good to know OpenAI API calls cost approximately $0.01-0.03 per error analysis Works with any ticketing system that supports REST API Can be triggered by webhooks from external monitoring tools Slack messages use rich formatting for mobile-friendly alerts Need Help? Join the Discord or ask in the Forum! Happy Monitoring!. An n8n automation workflow template by Anna Bui.

By Robert Breen

Chat with a Slack channel using AI. This workflow fetches the channel’s message history and lets you ask natural-language questions (“what were the decisions?”, “who’s blocked?”, “summarize yesterday”). The assistant only answers from the channel’s actual messages—no guessing. ⚙️ Setup Instructions 1️⃣ Set Up OpenAI Connection Go to OpenAI Platform Navigate to OpenAI Billing Add funds to your billing account Copy your API key into the OpenAI credentials in n8n 2️⃣ Connect Slack API Create an app → <https://api.slack.com/apps> OAuth & Permissions → add scopes you need to read channel history (typical: channels:history, groups:history, im:history, mpim:history, plus channels:read, groups:read, users:read. Add chat:write if you want the bot to reply in Slack.) Install the app to your workspace → copy the Bot User OAuth Token In n8n → Credentials → New → Slack OAuth2 API → paste token and save In the Slack History node, select your Slack credential and the Channel ID to read 🗣️ Example Questions You Can Ask “Give me a 5-bullet summary of the last 24 hours.” “What action items were assigned, and to whom?” “List open questions that haven’t been answered yet.” “Who was mentioned most this week?” “Summarize decisions from the last sprint planning.” “Show messages with the word ‘blocker’ from the past 2 days.” “What files/links were shared today?” 📬 Contact Need help customizing this or adding auto-replies back into Slack? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com. An n8n automation workflow template by Robert Breen.

By Michael Muenzer

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Fetch Instagram profile information with Apify and generate personalized DMs in Google Sheets. This is great for creator outreach, customer interviews, partnership prospecting, and streamlining your social Direct Messaging workflow. Saving hours per campaign or research study. How it works We read a list of Instagram accounts from a Google Sheet We trigger the Apify Instagram Post Scraper task to fetch the latest post data per account We pull the image URL of the newest post and analyze it with OpenAI Vision We use the analysis plus account metadata to generate a personalized DM We write the message back to the Google Sheet for easy sending and tracking Note: Both Apify and OpenAI provide free credits that can cover initial runs of this workflow (20.08.2025). Set up steps Copy Google Sheet template and add it in all Google Sheet nodes Make sure that n8n has read & write permissions for your Google sheet. Add your list of Instagram accounts in the first column in the Google sheet Add Apify credentials (e.g. API key) Create task for Instagram Post Scraper on Apify Add OpenAI API credentials What you can achieve How do I scale creator outreach while keeping messages personal? This workflow pulls each profile’s latest post and bio, then generates a DM that references those specifics. One consistent prompt, fresh data per profile. Personal at scale. How do I craft partnership or affiliate pitches that feel tailored to the creator’s audience? This n8n workflow spots niche, recent themes, and milestones, then inserts a targeted value prop like an affiliate code or UTM so the pitch mirrors their content and audience. How can I personalize interview invites using details from a recent post or bio? This workflow opens with a concrete reference from the newest post or bio, states your interview topic, and adds a short CTA. If there’s no recent post, it switches to a bio-based hook. How do I personalize at scale for thousands of profiles without duplicating outreach? This n8n workflow processes each handle once, logs status in Google Sheets, and skips already‑messaged rows, so you get unique, data-backed DMs across hundreds of profiles without repeats. An n8n automation workflow template by Michael Muenzer.

By Joe Swink

This template has a two part setup: Ingest PDF files from S3, extract text, chunk, embed with OpenAI embeddings, and index into a Qdrant collection with metadata. Provide a chat entry point that uses an Agent with OpenAI to retrieve from the same Qdrant collection as a tool and answer proposal knowledge questions. What it does Lists objects in an S3 bucket, loops through keys, downloads each file, and extracts text from PDFs. Chunks text and loads it into Qdrant with metadata for retrieval. Exposes a chat trigger wired to an Agent using an OpenAI chat model. Adds a retrieve as tool Qdrant node so the Agent can ground answers in the indexed corpus. Why it is useful Simple pattern for building a proposal or knowledge base from PDFs stored in S3. End to end path from ingestion to retrieval augmented answers. Easy to swap models or collections, and to extend with more tools. Setup notes Attach your own AWS credentials to the two S3 nodes and set your bucket name. Attach your Qdrant credentials to both Qdrant nodes and set your collection. Attach your OpenAI credentials to the embedding and chat nodes. The sanitized template uses placeholders for bucket and collection names. An n8n automation workflow template by Joe Swink.

By Ruslan Elishev

🤖 Telegram Bot with Dynamic Menus & Rating System What It Does This n8n workflow creates an interactive Telegram bot with: Dynamic inline keyboards that respond to user clicks 5-star rating system for collecting feedback Personalized responses using the user's actual name Multi-level menu navigation (Main → Settings → Profile, etc.) Real-time message updates when buttons are clicked How It Works Receives messages via Telegram webhook trigger node Extracts user data (name, ID, message type) Builds dynamic menus based on user actions Sends/updates messages with inline keyboards Handles button clicks without page refresh 🚀 Setup Instructions Get Your Bot Credentials Configure Workflow Open "Set Bot Token" node Replace token with yours Save and activate workflow (Active) Test Your Bot Message your bot on Telegram Click the buttons to navigate menus Try the rating system on Feature 1 🎨 Customization Guide Add New Menu Items In the "Prepare Response" Function node, add new cases: case 'your_feature': responseText = 'Your feature description'; keyboard = [ [{ text: '🎯 Button 1', callback_data: 'action1' }], [{ text: '🔙 Back', callback_data: 'main' }] ]; break; Modify Rating Options Change star buttons to numbers or emojis: // Current: ⭐⭐⭐ // Alternative: 1️⃣ 2️⃣ 3️⃣ or 👎 👍 Change Bot Responses Edit responseText for message content Modify keyboard arrays for button layout Add HTML formatting: bold, italic 💡 ++Key Features Demonstrated++ HTTP Request workaround for dynamic keyboards (n8n Telegram node limitation) Callback query handling to prevent loading animations Message editing vs sending new messages User data extraction from Telegram API Switch-case menu routing for scalable navigation ⚠️ ++Important Notes++ Limitation: n8n's native Telegram node doesn't support dynamic inline keyboards, this is why need to use HTTP nodes. Solution demonstrated: Use HTTP Request node with Telegram Bot API directly. An n8n automation workflow template by Ruslan Elishev.

By Joe Swink

This workflow is a simple example of using n8n as an AI chat interface into Appian. It connects a local LLM, persistent memory, and API tools to demonstrate how an agent can interact with Appian tasks. What this workflow does Chat interface: Accepts user input through a webhook or chat trigger Local LLM (Ollama): Runs on qwen2.5:7b with an 8k context window Conversation memory: Stores chat history in Postgres, keyed by sessionId AI Agent node: Handles reasoning, follows system rules (helpful assistant persona, date formatting, iteration limits), and decides when to call tools Appian integration tools: List Tasks: Fetches a user’s tasks from Appian Create Task: Submits data for a new task in Appian (title, description, hours, cost) How it works A user sends a chat message The workflow normalizes fields such as text, username, and sessionId The AI Agent processes the message using Ollama and Postgres memory If the user asks about tasks, the agent calls the Appian APIs The result, either a task list or confirmation of a new task, is returned through the webhook Why this is useful Demonstrates how to build a basic Appian connector in n8n with an AI chat front end Shows how an LLM can decide when to call Appian APIs to list or create tasks Provides a pattern that can be extended with more Appian endpoints, different models, or custom system prompts. An n8n automation workflow template by Joe Swink.

By Abdullah Alshiekh

🧩 Problem Solved Eliminates the slow, inconsistent, and error-prone process of manually replying to Facebook comments by automating it with AI, ensuring fast, accurate, and on-brand customer engagement 24/7. 📝 Description This workflow automatically monitors your latest Facebook post for new comments. For each new comment, an AI agent instantly generates a friendly, personalized reply in Egyptian Arabic, using your Notion knowledge base to ensure all product info is accurate. It prevents spam by never replying to the same comment twice. Simple Flow: New Comment → Duplicate Check → AI Analysis → Post Reply → Log Action. 🎯 Key Benefits 24/7 Instant Replies: Engage customers immediately, anytime. Perfect Brand Voice: Consistent, empathetic, natural Egyptian Arabic tone in every reply. Always Accurate: Pulls facts directly from your knowledge base; never invents details. No Duplicate Replies: Robust checks ensure each comment gets only one response. Huge Time Saver: Frees your team from constantly monitoring comments. 🛠️ Core Features Facebook API Integration (Read & Reply) Notion Database Integration (Knowledge Base & Logging) AI Response Generation (Google Gemini) Duplicate Comment Prevention Automated Workflow Logic 🔧 Requirements Facebook Access Token with pages_read_engagement and pages_manage_posts permissions. Two Notion Databases: One for your product knowledge, one to log processed comments. Google Gemini API Key for AI. n8n Credentials for Facebook, Notion, and Gemini. ⚙️ Quick Customization Tone & Style: Edit the prompt in the Generate Customer Reply node. Product Info: Add fields to your Notion Knowledge Base database. Escalation: Add a step to flag angry comments for a human agent. 🧠 Perfect For E-commerce: Answering product questions on promo posts. Healthcare: Providing accurate drug info with compassion. Local Businesses: Replying to queries about hours/menu items. Any Business that wants fast, professional customer engagement on social media. Need help? Connect on LinkedIn. An n8n automation workflow template by Abdullah Alshiekh.

By John Pranay Kumar Reddy

🧩 Short Summary Proactively alert to service endpoint changes and pod/container issues (Pending, Not Ready, Restart spikes) using Prometheus metrics, formatted and sent to Slack. 🗂️ Category DevOps / Monitoring & Observability 🏷️ Tags kubernetes, prometheus, slack, alerting, sre, ops, kube-state-metrics ✅ Prerequisites Prometheus scraping kube-state-metrics v2.x. Slack App or Incoming Webhook (channel access). n8n instance with outbound access to Prometheus & Slack. 🔑 Required Credentials in n8n Slack: Bot OAuth (chat:write) or Incoming Webhook URL. (Optional) Prometheus Basic Auth (if your Prometheus needs it). 🧠 What This Template Does Detects pods stuck in Pending (scheduling problems like taints/affinity/capacity). Detects containers Not Ready (readiness probe failures). Detects container restart spikes over a sliding window (default 5 minutes). Detects service discovery changes (endpoint count diffs current vs previous snapshot). Sends clean, emoji-enhanced Slack alerts with pod/namespace/service context. Outputs a 5-minute summary block to reduce noise. 📣 Slack Message Style (examples). An n8n automation workflow template by John Pranay Kumar Reddy.

By Abdellah Homrani

Automate the complete client onboarding process for AI automation services using n8n, Asana, Slack, Google Drive, and Gmail. This workflow ensures a consistent, professional, and scalable onboarding experience for every new client. 📌 Purpose This workflow is designed to: Eliminate manual setup tasks during client onboarding Automatically create client-specific resources (folders, projects, channels) Ensure smooth communication between your team and the client Deliver instant confirmation and welcome emails to the client ⚡ Trigger The workflow is triggered by an n8n Form submission (Client Onboarding Form) where clients provide: Name** Email** Company Name** Website** Proposal/Scope Document (PDF)** 🛠️ Actions Performed Once the form is submitted, the workflow executes the following steps: Extract Proposal/Scope Document Reads the uploaded PDF and extracts key information. Rename & Store Project Data Standardizes project information for downstream steps. Google Drive Setup Creates a client folder in Drive Stores the uploaded document Saves folder ID for references Asana Setup Creates a new Asana Project from a template Uses AI (OpenAI GPT-4o-mini) to parse the proposal and generate 20–30 detailed onboarding tasks Populates Asana with automatically assigned tasks and due dates Slack Setup Creates a dedicated client Slack channel (named dynamically using the company name) Posts a welcome message with next steps and checklist Welcome Email Sends a personalized email to the client, including: Google Drive folder link Asana project access Slack channel invite Onboarding call scheduler link 🔧 Configuration Notes Before using this workflow, configure: 1. Google Drive Set up OAuth2 credentials Ensure the account has folder creation permissions 2. Asana Set up OAuth2 credentials Verify workspace permissions Ensure the correct project template is available 3. Slack Create a Slack App with bot permissions Add OAuth scopes: channels:write chat:write users:read.email 4. Email (SMTP or Gmail OAuth2) Configure SMTP/Gmail credentials for internal notifications Update recipient email address 📬 Example Outputs ✅ Slack Channel Creation ✅ Welcome Email ✅ Asana Tasks 🚦 Suggested Triggers While currently triggered by an n8n Form, you can adapt this workflow to start from: Payment received** (Stripe/PayPal integration) Contract signed** (DocuSign/HelloSign) CRM Opportunity Change** (HubSpot/Pipedrive/Salesforce) 🏷️ Tags onboarding · automation · asana · slack · google-drive · client-success 📢 Notes If due dates fall on weekends, they are rolled forward to the next business day. Task breakdown leverages AI to generate detailed, sequential, and actionable onboarding steps. This workflow is optimized for scalability, ensuring every new client receives the same structured onboarding experience. An n8n automation workflow template by Abdellah Homrani.

By Sergey Skorobogatov

GiggleGPTBot — Witty Telegram Bot with AI & Postgres 📝 Overview GiggleGPTBot is a witty Telegram bot built with n8n, OpenRouter, and Postgres. It delivers short jokes, motivational one-liners, and playful roasts, responds to mentions, and posts scheduled witty content. The workflow also tracks user activity and provides lightweight statistics and leaderboards. ✨ Features 🤖 AI-powered humor engine — replies with jokes, motivation, random witty lines, or sarcastic roasts. 💬 Command support — /joke, /inspire, /random, /roast, /help, /stats, /top. 🎯 Mention detection — replies when users tag @GiggleGPTBot. ⏰ Scheduled posts — morning jokes, daily motivation, and random wisdom at configured times. 📊 User analytics — counts messages, commands, reactions, and generates leaderboards. 🗄️ Postgres persistence — robust schema with tables for messages, responses, stats, and schedules. 🛠️ How It Works Triggers Telegram Trigger — receives all messages and commands from a chat. Schedule Trigger — runs hourly to check for planned posts. Processing Switch routes commands (/joke, /inspire, /random, /roast, /help, /stats, /top). Chat history fetches the latest context. Mention Analysis determines if the bot was mentioned. Generating an information response builds replies for /help, /stats, /top. AI nodes (AI response to command, AI response to mention, AI post generation) craft witty content via OpenRouter. Persistence Init Database ensures tables exist (user_messages, bot_responses, bot_commands, message_reactions, scheduled_posts, user_stats). Logging nodes update stats and store every bot/user interaction. Delivery Replies are sent back via Telegram Send nodes (Send AI response, Send info reply, Reply to Mention, Submit scheduled post). ⚙️ Setup Instructions Create a Telegram Bot with @BotFather and get your API token. Add credentials in n8n: Telegram API (your bot token) OpenRouter (API key from openrouter.ai) Postgres (use your DB, Supabase works well). Run the Init Database node once to create all required tables. (Optional) Seed schedule with the Adding a schedule node — it inserts: Morning joke at 06:00 Daily motivation at 09:00 Random wisdom at 17:00 (Adjust chat_id to your group/channel ID.) Activate workflow and connect Telegram Webhook or Polling. 📊 Database Schema user\_messages** — stores user chat messages. bot\_responses** — saves bot replies. bot\_commands** — logs command usage. message\_reactions** — tracks reactions. scheduled\_posts** — holds scheduled jokes/wisdom/motivation. user\_stats** — aggregates per-user message/command counts and activity. 🔑 Example Commands /joke → witty one-liner with light irony. /inspire → short motivational phrase. /random → unexpected witty remark. /roast → sarcastic roast (no offensive targeting). /stats → shows your personal stats. /top → displays leaderboard. /help → lists available commands. @GiggleGPTBot + message → bot replies in context. 🚀 Customization Ideas Add new command categories (/quote, /fact, /news). Expand analytics with reaction counts or streaks. Localize prompts into multiple languages. Adjust CRON schedules for posts. ✅ Requirements Telegram Bot token OpenRouter API key Postgres database 📦 Import this workflow, configure credentials, run the DB initializer — and your witty AI-powered Telegram companion is ready!. An n8n automation workflow template by Sergey Skorobogatov.

By Trung Tran

Beginner’s Tutorial: Manage Azure Storage Account Container & Blob with n8n > This beginner-friendly n8n workflow shows you how to generate AI images using OpenAI, store them in Azure Blob Storage, and manage blob containers, all with zero code. 👤 Who’s it for This workflow is perfect for: Beginners learning Azure + OpenAI integration** No-code developers** experimenting with image generation Cloud learners** who want hands-on Blob Storage use cases Anyone who wants to automate storing AI-generated content in the cloud ⚙️ How it works / What it does 🖱️ Trigger the workflow manually using the Execute Workflow node. ✏️ Use the Edit Fields node to input: containerName (e.g., demo-images) imageIdea (e.g., "a robot holding a coffee cup") 📦 Create a new Azure Blob container (Create container). 🤖 Use an OpenAI-powered Prompt Generation Agent to craft the perfect image prompt. 🎨 Generate an image using OpenAI’s DALL·E model. ☁️ Upload the generated image to Azure Blob Storage (Create Blob). 📂 List blobs in the container (Get many blobs). 🧹 Delete any blob as needed (Delete Blob). (Optional) 🗑️ Remove the entire container (Delete container). 🔧 How to set up 🧠 Set up OpenAI Create an OpenAI account and get your API key. In n8n, go to Credentials → OpenAI and paste your key. 🪣 Set up Azure Blob Storage Log in to your Azure Portal. Create a Storage Account (e.g., mystorageaccount). Go to Access Keys tab and copy: Storage Account Name Key1 In n8n, create a new Azure Blob Storage Credential using: Account Name = your storage account name Access Key = key1 value > 📝 This demo uses Access Key authentication. You can also configure Shared Access Signatures (SAS) or OAuth in production setups. Run the Workflow Enter your image idea and container name. Click “Execute Workflow” to test it. 📋 Requirements | Requirement | Description | |------------------------|--------------------------------------------------| | Azure Storage Account | With container-level read/write access | | OpenAI API Key | For image and prompt generation | | n8n Version | v1.0+ recommended | | Image Credits | OpenAI charges tokens for DALL·E image creation | 🛠️ How to customize the workflow 🧠 Adjust Prompt Generation Update the Prompt Agent to include: Specific style (3D, anime, cyberpunk) Brand elements Multiple language options 📁 Organize by Date/User Modify the containerName to auto-include: Date (e.g., images-2025-08-20) Username or session ID 📤 Send Image Output Add Slack, Telegram, or Email nodes to deliver the image Create public links using Azure’s blob permissions 🔁 Cleanup Logic Auto-delete blobs after X days Add versioning or backup logic. An n8n automation workflow template by Trung Tran.

By Vlad Arbatov

Summary Chat with your AI agent in Telegram. It remembers important facts about you in Airtable, can transcribe your voice messages, search the web, read and manage Google Calendar, fetch Gmail, and query Notion. Responses are grounded in your recent memories and tool outputs, then sent back to Telegram. What this workflow does Listens to your Telegram messages (text or voice) Maintains short-term chat memory per user and long-term memory in Airtable Decides when to save new facts about you (auto “Save Memory” without telling you) Uses tools on demand: Web search via SerpAPI Google Calendar: list/create/update/delete events Gmail: list and read messages Notion: fetch database info Transcribes Telegram voice notes with OpenAI and feeds them to the agent Combines live tool results + recent memories and replies in Telegram Apps and credentials Telegram Bot API: personal_bot xAI Grok: Grok-4 model for chat OpenAI: speech-to-text (transcribe audio) Airtable: store long-term memories Google Calendar: calendar actions Gmail: email actions Notion: knowledge and reading lists SerpAPI: web search Typical use cases Personal assistant that remembers preferences, decisions, and tasks Create/update meetings by chatting, and get upcoming events Ask “what did I say I’m reading?” or “what’s our plan from last week?” Voice-first capture: send a voice note → get a transcribed, actionable reply Fetch recent emails or look up info on the web without leaving Telegram Query a Notion database (e.g., “show me the Neurocracy entries”) How it works (node-by-node) Telegram Trigger Receives messages from your Telegram chat (text and optional voice). Text vs Message Router Routes based on message contents: Text path → goes directly to the Agent (AI). Voice path → downloads the file and transcribes before AI. Always also fetches recent Airtable memories for context. Get a file (Telegram) Downloads the voice file (voice.file_id) when present. Transcribe a recording (OpenAI) Converts audio to text so the agent can use it like a normal message. Get memories (Airtable) Searches your “Agent Memories” base/table, filtered by user, sorted by Created. Aggregate (Aggregate) Bundles recent memory records into a single array “Memories” with text + timestamp. Merge (Merge) Combines current input (text or transcript) with the memory bundle before the agent. Simple Memory (Agent memory window) Short-term session memory keyed by Telegram chat ID; keeps the recent 30 turns. Tools wired into the agent SerpAPI Google Calendar tools: Get many events in Google Calendar Create an event in Google Calendar Update an event in Google Calendar Delete an event in Google Calendar Gmail tools: Get many messages in Gmail Get a message in Gmail Notion tool: Get a database in Notion Airtable tool: Save Memory (stores distilled facts about the user) Agent System prompt defines role, tone, and rules: Be a friendly assistant. On each message, decide if it contains user info worth saving. If yes, call “Save Memory” to persist a short summary in Airtable. Don’t announce memory saves—just continue helping. Use tools when needed (web, calendar, Gmail, Notion). Think with the provided memory context block. Uses xAI Grok Chat Model for reasoning and tool-calling. Can call Save Memory, Calendar, Gmail, Notion, and SerpAPI tools as needed. Save Memory (Airtable) Persists Memory and User fields to “Agent Memories” base; auto timestamp by Airtable. Send a text message (Telegram) Sends the agent’s final answer back to the same Telegram chat ID. Node map | Node | Type | Purpose | |---|---|---| | Telegram Trigger | Trigger | Receive text/voice from Telegram | | Text vs voice router | Flow control | Route text vs voice; also trigger memories fetch | | Get a file | Telegram | Download voice audio | | Transcribe a recording | OpenAI | Speech-to-text for voice notes | | Get memories | Airtable | Load recent user memories | | Aggregate | Aggregate | Pack memory records into “Memories” array | | Merge | Merge | Combine input and memories before agent call | | Simple Memory | Agent memory | Short-term chat memory per chat ID | | xAI Grok Chat Model | LLM | Core reasoning model for the Agent | | Search Web with SerpAPI | Tool | Web search | | Google Calendar tools | Tool | List/create/update/delete events | | Gmail tools | Tool | Search and read email | | Notion tool | Tool | Query a Notion database | | Save Memory | Airtable Tool | Persist distilled user facts | | AI Agent | Agent | Orchestrates tools + memory, produces the answer | | Send a text message | Telegram | Reply to the user in Telegram | Before you start Create a Telegram bot and get your token (via @BotFather). Put your Telegram user ID into the Telegram Trigger node (chatIds). Connect credentials: xAI Grok (model: grok-4-0709) OpenAI (for audio transcription) Airtable (Agent Memories base and table) Google Calendar OAuth Gmail OAuth Notion API SerpAPI key Adjust the Airtable “User” value and the filterByFormula to match your name or account. Setup instructions 1) Telegram Telegram Trigger: additionalFields.chatIds = your_telegram_id download = true to allow voice handling Send a text message: chatId = {{ $('Telegram Trigger').item.json.message.chat.id }} 2) Memory Airtable base/table must exist with fields: Memory, User, Created (Created auto-managed). In Save Memory and Get memories nodes, align Base, Table, and filterByFormula with your setup. Simple Memory: sessionKey = {{ $('If').item.json.message.chat.id }} contextWindowLength = 30 (adjust as needed) 3) Tools Google Calendar: choose your calendar, test get/create/update/delete. Gmail: set “returnAll/simplify/messageId” via $fromAI or static defaults. Notion: set your databaseId. SerpAPI: ensure the key is valid. 4) Agent (AI node) SystemMessage: customize role, name, and any constraints. Text input: concatenates transcript or text into one prompt: {{ $json.text }}{{ $json.message.text }} How to use Send a text or voice message to your bot in Telegram. The agent replies in the same chat, optionally performing tool actions. New personal facts you mention are silently summarized and stored in Airtable for future context. Customization ideas Replace Grok with another LLM if desired. Add more tools: Google Drive, Slack, Jira, GitHub, etc. Expand memory schema (e.g., tags, categories, confidence). Add guardrails: profanity filters, domain limits, or cost control. Multi-user support: store chat-to-user mapping and separate memories by user. Add summaries: a daily recap message created from new memories. Limits and notes Tool latency: calls to Calendar, Gmail, Notion, and SerpAPI add response time. Audio size/format: OpenAI transcription works best with common formats and short clips. Memory growth: periodically archive old Airtable entries, or change Aggregate window. Timezone awareness: Calendar operations depend on your Google Calendar settings. Privacy and safety Sensitive info may be saved to Airtable; restrict access to the base. Tool actions operate under your connected accounts; review scopes and permissions. The agent may call external APIs (SerpAPI, OpenAI); ensure this aligns with your policies. Example interactions “Schedule a 30‑min catch‑up with Alex next Tuesday afternoon.” “What meetings do I have in the next 4 weeks?” “Summarize my latest emails from Product Updates.” “What did I say I’m reading?” (agent recalls from memories) Voice note: “Remind me to call the dentist this Friday morning.” → agent transcribes and creates an event. Tags telegram, agent, memory, grok, openai, airtable, google-calendar, gmail, notion, serpapi, voice, automation Changelog v1: First release with Telegram agent, short/long-term memory, voice transcription, and tool integrations for web, calendar, email, and Notion. An n8n automation workflow template by Vlad Arbatov.

By Alex

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This n8n template automatically parses bank transaction emails (HDFC, Indian Bank, Indian Overseas Bank, UPI apps like Google pay, Paytm, etc.) - The from email(bank name/UPI apps) is changable, classifies them using Gemini AI, and logs them into a structured Google Sheets budget tracker. It helps you consolidate expenses, compare against monthly budgets, and get real-time alerts when limits are exceeded. 📝 Problem Statement Tracking expenses manually from different bank emails and UPI apps is frustrating, time-consuming, and error-prone. Small transactions often slip through, making budget control difficult. This workflow solves that by: Automatically extracting financial data from Gmail. Categorizing expenses using AI parsing. Saving all data into Google Sheets in a structured way. Comparing with monthly budgets and raising alerts. Target Audience: Individuals who want personal budget automation. Families managing shared household spending. Small teams looking for a lightweight financial log. ⚙️ Setup Prerequisites An n8n instance (self-hosted or cloud). A Google account with Gmail + Google Sheets enabled. Pre-created Google Sheets file with 2 tabs: Expenses Budgets A configured Gemini API connection in n8n. 📊 Google Sheets Template Expenses Tab (columns in order): Timestamp | Date | Account | From | To | Type | Category | Description | Amount | Currency | Source | MessageId | Status Budget Tab (columns in order): Month | Category | Budget Amount | Notes | UpdatedAt Yearly Summary Tab (auto-calculated): Year | Month | Category | Total Expense | Budget | Variance | Alert Variance = Budget - Total Expense Alert = ⚠️ Over Budget when spending > budget 🚀 How It Works Gmail: Gmail Trigger captures new bank/UPI emails. Gemini AI Parser extracts structured details (date, amount, category, etc.). Filter Node ensures only valid financial transactions are logged. Information extractor will extract the information like Date, account, transaction type(Credit/Debit), description, currency, status, messageId, from email, to email, category -> checks if the transaction is 'Credit' or 'Debit' then appends the details to the respective google sheet Budget Validator checks against monthly allocations. If the expense is above the budget is raises an alert and will send a email to the connected account. For sending email I wrote a Google Sheet App script: var ss = SpreadsheetApp.getActiveSpreadsheet(); var monthly = ss.getSheetByName("MonthlySummary"); var yearly = ss.getSheetByName("YearlySummary"); // Get values from Monthly Summary var totalExpense = monthly.getRange("D2").getValue(); var budget = monthly.getRange("E2").getValue(); // Get current date info var now = new Date(); var month = Utilities.formatDate(now, "GMT+5:30", "MM"); var year = Utilities.formatDate(now, "GMT+5:30", "yyyy"); var status = (totalExpense > budget) ? "Alert" : ""; // Append to Yearly Summary yearly.appendRow([year, month, totalExpense, status]); // If budget exceeded, send alert email if (status === "Alert") { var emailAddress = "YOUR EMAIL"; var subject = "⚠️ Budget Exceeded - " + month + "/" + year; var body = "Your total expenses this month (" + totalExpense + ") have exceeded your budget of " + budget + ".\n\n" + "Please review your spending."; MailApp.sendEmail(emailAddress, subject, body); } // 🔄 Reset Monthly Summary var lastRow = monthly.getLastRow(); if (lastRow > 3) { // assuming headers in first 2-3 rows monthly.getRange("A4:C" + lastRow).clearContent(); } // Reset total in D2 monthly.getRange("D2").setValue(0); } Monthly summary auto-calculates the expense and updates the expense for every month and budgets(sum all budgets if there are more than 1 budgets). Yearly Summary auto-updates and raises over-budget alerts. Telegram: Takes input from a telegram bot which is connected to the n8n workflow telegram trigger. Gemini AI Parser extracts structured details (date, amount, category, etc.). Then it checks, whether the manually specified details is 'budget' or 'expense', then splits the data -> parse the data -> then again check whether it is 'Budget' or 'Expense' then appends the structured data to the respective google sheet. Monthly summary auto-calculates the expense and updates the expense for every month and budgets(sum all budgets if there are more than 1 budgets). Yearly Summary auto-updates and raises over-budget alerts. 🔧 Customization Add support for more banks/UPI apps by extending the parser schema. const senderEmail = $input.first().json.From || ""; // Account detection let account = ""; // you can modify the bank names and UPI names here if (/alerts@hdfcbank\.net/i.test(senderEmail)) account = "HDFC Bank"; // you can modify the bank names and UPI names here else if (/ealerts@iobnet\.co\.in/i.test(senderEmail)) account = "Indian Overseas Bank"; else if (/alerts@indianbank\.in/i.test(senderEmail)) account = "Indian Bank"; else if (/@upi|@okhdfcbank|@okaxis|@okicici/i.test(emailBody)) { if (/gpay|google pay/i.test(emailBody)) account = "Google Pay"; else if (/phonepe/i.test(emailBody)) account = "PhonePe"; else if (/paytm/i.test(emailBody)) account = "Paytm"; else account = "UPI"; } else { account = "Other"; } // If account is "Other", skip output if (account === "Other") { return []; } // Output return [{ account, from: senderEmail, // exact Gmail "From" metadata snippet: emailBody, messageId: $input.first().json.id || "" }]; Create custom categories (e.g., Travel, Groceries, Subscriptions). Send real-time alerts via Telegram/Slack/Email using n8n nodes. Share the Google Sheet with family or team for collaborative use. 📌 Usage The workflow runs automatically on every new Gmail transaction email and financial input on the telegram bot. At the end of each month, totals are calculated in the Yearly Summary tab. Users only need to maintain the Budget tab with updated monthly allocations. An n8n automation workflow template by Alex.

By Roshan Ramani

Who's it for Business owners, marketers, and web developers who want to instantly respond to website contact form submissions and maintain organized lead records without manual monitoring. What it does This workflow automatically processes contact form submissions from your website, sending immediate WhatsApp notifications with formatted lead details while simultaneously logging all data to Google Sheets for organized lead management and follow-up tracking. How it works When someone submits your website contact form, the webhook instantly receives the data, formats it into a professional WhatsApp message with emojis and structure, sends the notification to your phone, and logs all details (name, email, phone, service, message, timestamp) to a Google Sheets database for permanent storage and analysis. Requirements WhatsApp Business API credentials Google Sheets API access with a spreadsheet containing these columns: date (for timestamp) name (contact's full name) email (contact's email address) phone (contact's phone number) service (requested service/interest) message (contact's message/inquiry) Website contact form that can POST to webhook URL with fields: name, email, phone, service, message n8n instance (self-hosted or cloud) Google Sheets Setup Create a new Google Sheet with the following column headers in row 1: Column A: date Column B: name Column C: email Column D: phone Column E: service Column F: message The workflow will automatically populate these columns with each form submission and use the date column for duplicate checking. How to set up Credentials Setup: Configure WhatsApp Business API credentials in the WhatsApp node Set up Google Sheets API connection and grant necessary permissions Configuration: Update the recipient phone number in the WhatsApp node (format: +1234567890) Replace the Google Sheets document ID with your spreadsheet ID Ensure your Google Sheet has the required column structure mentioned above Integration: Copy the webhook URL from the Contact Form Trigger node Configure your website form to POST data to this endpoint with field names: name, email, phone, service, message Testing: Test the workflow by submitting a sample form entry Verify WhatsApp notification is received and data appears in Google Sheets How to customize the workflow Message Format:** Modify the WhatsApp message template in the Format Lead Data node Additional Fields:** Add more form fields by updating both the Code node and Google Sheets mapping Email Notifications:** Include email alerts by adding an Email node after the Format Lead Data node Conditional Logic:** Set up different notifications for high-priority services or VIP customers Data Validation:** Add filtering rules in the Code node to handle spam or invalid submissions Multiple Recipients:** Configure the WhatsApp node to send alerts to multiple team members. An n8n automation workflow template by Roshan Ramani.

By Davide Boizza

This workflow implements a Retrieval-Augmented Generation (RAG) system that integrates Google Drive and Qdrant. This setup creates a powerful, self-updating knowledge base that provides accurate, context-aware answers to user queries. Key Advantages Automated Knowledge Base Updates** No manual intervention is required—documents in Google Drive are automatically synchronized with Qdrant. Efficient Search and Retrieval** Vector embeddings enable fast and precise retrieval of relevant information. Scalable and Flexible** Works with multiple documents and supports continuous growth of your dataset. Seamless AI Integration** Combines OpenAI embeddings for vectorization and Google Gemini for high-quality natural language answers. Metadata-Enhanced Storage** Each document stores metadata (file ID and name), making it easy to manage and track document versions. End-to-End RAG Pipeline** From document ingestion to AI-powered Q\&A, everything is handled inside one n8n workflow. How It Works This workflow implements a Retrieval-Augmented Generation (RAG) system that automatically processes, stores, and retrieves document information for AI-powered question answering. Here’s how it functions: Document Processing & Vectorization: The system monitors a specified Google Drive folder for new or updated files. When a file is added or modified, it is downloaded and split into manageable chunks using a Recursive Character Text Splitter. Each chunk is converted into vector embeddings using OpenAI's embedding model. These vectors, along with metadata (file ID, file name), are stored in a Qdrant vector database. Automatic Updates: The workflow includes a mechanism to delete old vectors associated with an updated file before inserting the new ones, ensuring the knowledge base remains current. Query Handling & Response Generation: When a user sends a chat message (via a chat trigger), the system: Retrieves the most relevant document chunks from Qdrant based on the query's semantic similarity. Uses a Google Gemini language model to generate a context-aware answer grounded in the retrieved documents. This provides accurate, source-based responses instead of relying solely on the AI's internal knowledge. Initial Setup & Maintenance: The workflow can be triggered manually to create the Qdrant collection or clear all existing data. It processes all existing files in the Drive folder during initial setup, populating the vector store. Set Up Steps To configure this workflow, follow these steps: STEP 1: Create Qdrant Collection Replace QDRANTURL in the "Create collection" and "Clear collection" nodes with your Qdrant instance URL (e.g., http://your-qdrant-host:6333). Replace COLLECTION with your desired collection name. Ensure the Qdrant API credentials are correctly set in the respective HTTP Request nodes. STEP 2: Configure Google Drive Access Set up OAuth credentials for Google Drive to allow the workflow to: Read files from a specific folder . Download files for processing. Update the Folder ID in the "Search files" and "Update?" trigger nodes to point to your target Google Drive folder. STEP 3: Set Up AI Models Configure the OpenAI API credentials in the Embeddings nodes for generating text embeddings. Configure the Google Gemini (PaLM) API credentials in the Google Gemini Chat Model node for generating answers. STEP 4: Configure Metadata The system automatically attaches metadata (file_id, file_name) to each document chunk. This is set in the Default Data Loader nodes. This metadata is crucial for identifying the source of information and for the update mechanism. STEP 5: Test the RAG System The workflow includes a chat trigger ("When chat message received") for testing. Send a query to test the retrieval and answer generation process. 👉 Subscribe to my new YouTube channel. Here I’ll share videos and Shorts with practical tutorials and FREE templates for n8n. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Agent Circle

This n8n template automates real-time SEO keyword research, delivering comprehensive keyword insights, autocomplete suggestions, subtopics, SERP analysis, and more, straight into your Google Sheet. Use cases are many: This workflow is perfect for bloggers, SEO professionals, affiliate marketers, e-commerce teams, and content creators who need fresh, actionable keyword data for planning, optimization, and content expansion - without endless manual research. How It Works Phase 1: Set Google Sheet ID & Input Target Keywords In n8n, enter the Google Sheet ID in the Set Sheet ID node. In the connected Google Sheet, for the first tab Main Keyword, you manually add the main keywords that you want the tool to research and generate relevant keyword suggestions for. Trigger the process by clicking Test Workflow or Execute Workflow. The workflow automatically reads your main keywords from the Main Keyword tab in your linked Google Sheet, only those marked with the status Ready will be processed. Phase 2: Automated Research & Data Collection For your input main keyword (considering here you only set Ready for one main keyword in the connected Google Sheet), the workflow runs multiple automated queries in parallel: 1. Get Related Keywords: The workflow sends a POST request to the DataForSEO API endpoint to directly retrieve an array of related keywords. Then, the array of related keywords is parsed out, preparing each keyword as a separate record for further processing. It appends each extracted related keyword as a new row in the Related KW tab of your connected Google Sheet. The Main Keyword value from your input is included in Column A of the tab to maintain keyword context. Additionally, the workflow appends the related keywords - along with the associated main keyword - to the All Results tab in your Google Sheet for consolidated tracking and future reference. This ensures you have both a dedicated list of related keywords and a master log of all research results in one place. 2. Get Keyword Suggestions: The workflow sends a POST request to the DataForSEO API endpoint to directly retrieve an array of keyword suggestions related to your main keyword. This array of keyword suggestions is then parsed, splitting out each suggestion as an individual record for further processing. Each extracted keyword suggestion is appended as a new row in the KW Suggestion tab of your connected Google Sheet. The original Main Keyword value from your input is included in Column A of the tab to maintain clear context. Additionally, the workflow appends all keyword suggestions - along with the associated main keyword - to the All Results tab in your Google Sheet for consolidated tracking and future reference. This ensures you have both a dedicated list of keyword suggestions and a master log of all research results in one place. 3. Get Autocomplete Suggestions: The workflow sends a POST request to the DataForSEO API endpoint to retrieve Google autocomplete keyword suggestions for your main keyword. The array of autocomplete keyword suggestions is parsed out as an individual record for processing. Each extracted autocomplete keyword is appended as a new row in the Autocomplete Suggestion tab of your connected Google Sheet. The Main Keyword is included alongside each entry for proper tracking. Additionally, the workflow appends all autocomplete keywords - along with the associated main keyword - to the All Results tab in your Google Sheet for consolidated tracking and future reference. This ensures you have both a dedicated list of autocomplete keywords and a master log of all research results in one place. 4. Get Content Ideas: The workflow sends a POST request to the DataForSEO API endpoint to retrieve content ideas and fresh topic suggestions based on your main keyword. The array of content ideas is then parsed; each idea is extracted as a separate record for further use. Every content idea is then appended as a new row in the Content Idea tab of your connected Google Sheet, with the Main Keyword included to provide context. Additionally, the workflow appends all content ideas, along with their related main keyword, to the All Results tab in your sheet for consolidated tracking and easy access. This ensures you have both a dedicated list of content ideas for brainstorming and a central log of all keyword research outputs in one place. 5. Get SERPs: The workflow sends a POST request to the DataForSEO API endpoint, retrieving both the current Google SERP (Search Engine Results Page) data and People Also Ask (PAA) questions related to your main keyword. Then, the data is split into two streams: one for standard SERP results and one for PAA questions. For Standard SERPs: The workflow filters the SERP data to keep only the most relevant results. Each SERP entry is appended as a new row in the SERP tab of your connected Google Sheet, providing insights into top-ranking pages and their attributes. For PAA (People Also Ask): The PAA data is also filtered. Each PAA question is split out and added as a new row in the PAA tab in your connected Google Sheet for focused tracking. Additionally, all PAA questions are consolidated and appended, along with their related main keyword, to the All Results tab in your sheet for consolidated tracking and easy access. This ensures you have both a dedicated list of PAA questions for brainstorming and a central log of all research outputs in one place. Result Types Main Keyword: Your original list of main keywords with status tracking. All Results: A master log of all relevant keyword and idea research outputs for easy review. Related KW: Lists of related keywords for each main keyword. KW Suggestion: Suggested keyword ideas for broader targeting. Autocomplete Suggestion: Google autocomplete keyword suggestions to capture real user queries. Content Idea: Keyword-related content ideas to build out your content clusters. SERP: top-ranking pages, including their URLs, page titles, and descriptions - perfect for quick competitor and content analysis. PAA: People Also Ask questions for intent research and content expansion. How To Set Up Download the workflow package and import it into your n8n interface. Duplicate the Keyword Research Google Sheet template to your Google Sheets account. Set up necessary credentials for tools access and usability: For Google Sheets access, ensure each node is properly connected to the correct tab in your connected Google Sheet template: Node Get Main Keywords → connected to the Main Keyword tab Node Add Related KWs → connected to the Related KW tab Node Save Related KWs to All Results → connected to the All Results tab Node Add KW Suggestions → connected to the KW Suggestion tab Node Save KW Suggestions to All Results → connected to the All Results tab Node Add Autocomplete Suggestions → connected to the Autocomplete Suggestion tab Node Save Autocomplete Suggestions to All Results → connected to the All Results tab Node Add Content Ideas → connected to the Content Idea tab Node Save Content Ideas to All Results → connected to the All Results tab Node Add SERPs → connected to the SERP tab Node Add PAAs → connected to the PAA tab Node Save PAAs to All Results → connected to the All Results tab For DataForSEO access, set up API credentials (Basic Auth) along with correct POST URL for each query in the following node: Node Get Related KWs Node Get KW Suggestions Node Get Autocomplete Suggestions Node Get Content Ideas Node Get SERPs Enter your Google Sheet ID in the Set Sheet ID node to link the workflow to your connected Google Sheet. Add your target keywords to Column B in the Main Keyword tab in the connected Google Sheet and set their status to Ready Run the workflow by clicking Test Workflow or Execute Workflow in n8n. Review the results across all output tabs in your connected Google Sheet. Requirements n8n** instance (self-hosted or cloud). Basic setup in Google Cloud Console (OAuth or API Key method enabled) with enabled access to Google Sheets. DataForSEO** API credentials. How To Customize Add Extra Research Steps**: Expand the workflow by integrating additional research queries related to the main keywords - such as backlink analysis, competitor monitoring, or search trend tracking - to gather even more valuable insights alongside your keyword data. Automate Scheduling & Notifications**: Set up an automatic schedule in n8n so the workflow runs at your preferred intervals. Connect notification tools like Telegram, Slack, or a chatbox to receive alerts whenever the process finishes, keeping you instantly updated without manual checks. Personalize Data Mapping**: Tailor how the research results are saved to your Google Sheet by customizing column mapping and naming conventions. This lets you organize your data exactly how you want for easier analysis and reporting. Need Help? If you’d like this workflow customized to fit your tools and platforms availability, or if you’re looking to build a tailored AI Agent for your own business - please feel free to reach out to Agent Circle. We’re always here to support and help you to bring automation ideas to life. Join our community on different platforms for support, inspiration and tips from others. Website: https://www.agentcircle.ai/ Etsy: https://www.etsy.com/shop/AgentCircle Gumroad: http://agentcircle.gumroad.com/ Discord Global: https://discord.gg/d8SkCzKwnP FB Page Global: https://www.facebook.com/agentcircle/ FB Group Global: https://www.facebook.com/groups/aiagentcircle/ X: https://x.com/agent_circle YouTube: https://www.youtube.com/@agentcircle LinkedIn: https://www.linkedin.com/company/agentcircle. An n8n automation workflow template by Agent Circle.

By Yashraj singh sisodiya

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. ATS Resume Maker Workflow Explanation Aim The aim of the ATS Resume Maker according to JD workflow is to automate the creation of an ATS-friendly resume by tailoring a candidate’s resume to a specific job description (JD). It streamlines the process of aligning resume content with JD requirements, producing a professional, scannable PDF resume that can be stored in Google Drive. Goal The goal is to: Allow users to input their resume (text or PDF) and a JD (PDF) via a web form. Extract and merge the text from both inputs. Use AI to customize the resume, prioritizing JD keywords while maintaining the candidate’s truthful information. Generate a clean, ATS-optimized HTML resume and convert it to a downloadable PDF. Upload the final PDF to Google Drive for easy access. This ensures the resume is optimized for Applicant Tracking Systems (ATS), which are used by employers to screen resumes, by incorporating relevant keywords and maintaining a simple, scannable format. Requirements The workflow relies on specific components and configurations: n8n Platform**: The automation tool hosting the workflow. Node Requirements**: Form Trigger: A web form to collect user inputs (resume text/PDF, JD PDF). Process one binary file1: JavaScript to rename and organize PDF inputs. Extracting resume1: Extracts text from PDF files. Merge Resume + JD1: Combines resume and JD text into a single string. Customize resume1: Uses Perplexity AI to generate an ATS-friendly HTML resume. HTML format1: Cleans the HTML output by removing newlines. HTML3: Processes HTML for potential display or validation. HTML to PDF: Converts the HTML resume to a PDF file. Upload file: Saves the PDF to a specified Google Drive folder. Credentials**: CustomJS account for the HTML-to-PDF conversion API. Google Drive account for file uploads. Perplexity account for AI-driven resume customization. Input Requirements**: Resume (plain text or PDF). Job description (PDF). Output**: A tailored, ATS-friendly resume in PDF format, uploaded to Google Drive. API Usage The workflow integrates multiple APIs to achieve its functionality: Perplexity API*: Used in the *Customize resume1 node to leverage the sonar-reasoning model for generating an ATS-optimized HTML resume. The API processes the merged resume and JD text, aligning content with JD keywords while adhering to strict HTML and CSS guidelines (e.g., Arial font, no colors, single-column layout). [Ref: Workflow JSON] CustomJS API*: Used in the *HTML to PDF node to convert the cleaned HTML resume into a PDF file. This API ensures the resume is transformed into a downloadable format suitable for ATS systems. [Ref: Workflow JSON] Google Drive API*: Used in the *Upload file node to store the final PDF in a designated Google Drive folder (Resume folder in My Drive). This API handles secure file uploads using OAuth2 authentication. [Ref: Workflow JSON] These APIs are critical for AI-driven customization, PDF generation, and cloud storage, ensuring a seamless end-to-end process. HTML to PDF Conversion The HTML-to-PDF conversion is a key step in the workflow, handled by the HTML to PDF node: Process*: The node takes the cleaned HTML resume ($json.cleanedResponse) from the *HTML format1 node and uses the @custom-js/n8n-nodes-pdf-toolkit.html2Pdf node to convert it into a PDF. API*: Relies on the *CustomJS API for high-fidelity conversion, ensuring the PDF retains the ATS-friendly structure (e.g., no graphics, clear text hierarchy). Output*: A binary PDF file passed to the *Upload file node. Relevance**: This step ensures the resume is in a widely accessible format, suitable for downloading or sharing with employers. The use of a dedicated API aligns with industry practices for HTML-to-PDF conversion, as seen in services like PDFmyURL or PDFCrowd, which offer similar REST API capabilities for converting HTML to PDF with customizable layouts. Ref:,(https://pdfmyurl.com/) Download from Community Link The workflow does not explicitly include a community link for downloading the final PDF, but the Upload file node stores the PDF in Google Drive, making it accessible via a shared folder or link. To enable direct downloads: Workflow Summary The ATS Resume Maker according to JD workflow automates the creation of a tailored, ATS-friendly resume by: Collecting user inputs via a web form (Form Trigger). Processing and extracting text from PDFs (Process one binary file1, Extracting resume1). Merging and customizing the content using Perplexity AI (Merge Resume + JD1, Customize resume1). Formatting and converting the resume to PDF (HTML format1, HTML3, HTML to PDF). Uploading the PDF to Google Drive (Upload file). The workflow leverages APIs for AI processing, PDF conversion, and cloud storage, ensuring a professional output optimized for ATS systems. Community sharing can be enabled via Google Drive links or external platforms, as discussed in related web resources. Ref:,,(https://pdfmyurl.com/) Timestamp: 02:54 PM IST, Wednesday, August 20, 2025. An n8n automation workflow template by Yashraj singh sisodiya.

By Omer Fayyaz

This n8n template implements a Customer Support Chat Agent for Web Hosting Companies with Google Gemini, Google Sheets Knowledge base and WHMCS API to Check Domain Name Availability Who's it for This template is designed for web hosting companies, domain registrars, and IT service providers who want to automate their customer support with an AI-powered chatbot. It's perfect for businesses looking to provide 24/7 customer assistance for hosting plans, domain services, and technical support while maintaining a professional, human-like interaction experience. How it works / What it does This workflow creates an AI-powered customer support chatbot that provides comprehensive assistance for web hosting and domain services. The AI agent (named Matt) automatically: Receives customer queries through a webhook endpoint Captures customer information (name and email) at the start of each session Processes natural language requests using Google Gemini AI Accesses real-time information from multiple Google Sheets knowledge bases: Shared Hosting Plans (pricing, features, specifications) Domain Prices (registration, transfer, renewal costs) Hosting Features (technical capabilities and specifications) FAQs (common questions and answers) Payment Method Details (accepted payment options) Company Offerings (available products and services) Checks domain availability via WHMCS API integration Provides accurate, contextual responses based on the knowledge base Maintains conversation history with session-based memory Stores complete chat sessions in Google Sheets for analysis and follow-up The system ensures 100% accuracy by only providing information that exists in the knowledge base, eliminating guesswork and maintaining brand consistency. How to set up 1. Configure Google Sheets Knowledge Base Set up a Google Sheets document with the following sheets: Shared_Hosting_Plans: Hosting plan details, pricing, and specifications Domain_Prices: Domain registration and renewal pricing Hosting_Features: Technical features and capabilities FAQs: Frequently asked questions and answers Payment_Method_Details: Payment options and instructions Offerings: Available products and services Update the Google Sheets credentials in each tool node 2. Set up Google Gemini API Configure your Google Gemini API credentials in the Google Gemini Chat Model node Ensure you have sufficient API quota for your expected usage 3. Configure WHMCS API (Optional) Replace Your_WHMCS_Identifier with your actual WHMCS API identifier Replace Your_WHMCS_Secret with your actual WHMCS API secret Update https://your_whmcs_url.com/includes/api.php with your WHMCS domain This enables domain availability checking for customers 4. Set up Chat Storage Create a Google Sheet for storing chat inquiries Update the document ID and credentials in the Chat_Inquiries node This will automatically store all customer conversations for analysis 5. Deploy the Webhook The workflow creates a unique webhook endpoint for receiving customer queries Use this endpoint URL in your customer-facing application or chat interface Requirements Google Sheets account** with the knowledge base set up Google Gemini API account** with appropriate credentials n8n instance** (self-hosted or cloud) WHMCS installation** (optional, for domain availability checking) Web hosting or domain services business** How to customize the workflow Modify AI Agent Behavior Edit the system message in the AI Agent node to change the bot's personality and response style Adjust response length and tone to match your brand voice Customize the agent's name (currently "Matt") Enhance Knowledge Base Add more Google Sheets tools for additional information sources Include product catalogs, pricing tables, or technical documentation Add multi-language support for international customers Improve Customer Experience Add domain suggestion algorithms based on customer input Integrate with your existing customer database for personalized recommendations Add notification systems (email, Slack, SMS) for high-value inquiries Security Enhancements Implement API key rotation and monitoring Add request validation and sanitization Set up usage analytics and abuse prevention Key Features Real-time information access** from Google Sheets knowledge base AI-powered natural language processing** for customer queries Session-based memory** for contextual conversations Automatic domain availability checking** via WHMCS API Professional, customer-focused responses** that maintain brand standards Complete chat history storage** for analysis and follow-up Scalable webhook architecture** for high-volume usage Multi-tool integration** for comprehensive customer support Use Cases 24/7 customer support automation** for web hosting companies Sales team assistance** with real-time product information Customer self-service portals** with intelligent assistance Lead generation** through proactive service recommendations Customer retention** via improved support experience Support ticket reduction** by handling common queries automatically Chat Session Management The workflow automatically manages chat sessions with the following features: Unique Session IDs** for each customer conversation Automatic customer information capture** (name and email) Conversation history tracking** with chronological message storage Session persistence** across multiple interactions Data export** to Google Sheets for analysis and follow-up Example Customer Interactions The AI agent can handle various customer scenarios: Hosting Plan Inquiries**: Detailed information about shared hosting plans, features, and pricing Domain Services**: Domain availability checking, pricing, and registration guidance Technical Support**: Feature explanations, setup guidance, and troubleshooting Payment Information**: Accepted payment methods and transaction processes General Support**: Company information, service offerings, and FAQ responses This template transforms your web hosting business by providing instant, accurate customer support while maintaining the personal touch that customers expect from professional service providers. The AI agent becomes an extension of your support team, handling routine inquiries and allowing human agents to focus on complex technical issues. An n8n automation workflow template by Omer Fayyaz.

By DuyTran

Overview This n8n workflow automatically fetches the latest news articles from multiple RSS sources, filters for the last 24 hours, summarizes them into a concise ~400-word digest in Vietnamese, and then delivers the result directly to Zalo and Telegram. It’s designed for professionals who need a quick, AI-curated overview of daily news without manually browsing multiple websites. 🧩 Key Features ⏰ Triggers Schedule Trigger: Run at specific times (e.g., morning briefing). Zalo & Telegram Triggers: Start workflow when requested via chat. 🌐 News Collection Fetches news from 4 RSS sources (RSS.app, Google News, etc.). Extracts standardized fields (title, pubDate, content). 🔍 Filtering & Processing Keeps only news published in the last 24h. Limits to 20 most recent items. Aggregates multiple feeds into one dataset. 🧠 AI Summarization Uses OpenAI Assistant to generate 15–19 highlights (~400 words). Translates into Vietnamese, removes special symbols. Optionally calls Perplexity AI to refine content into a financial–economic–political style summary. Maintains short-term context with Memory Buffer for improved output. 📲 Delivery Channels Sends digest directly to Zalo (personal & group chat). Sends digest to Telegram bot. ⚙️ Workflow Steps Trigger – schedule or chat command (Zalo/Telegram). RSS Fetchers (4 feeds) – collect news. Edit Fields – normalize title, date, and content. Merge & Filter – unify feeds, keep only last 24h. Limit & Aggregate – select top 20 articles. AI Summarization – generate digest via OpenAI + Perplexity. Delivery – send results to Zalo & Telegram. 🔐 Requirements ✅ RSS source URLs (already set in workflow). 🔑 OpenAI API key. 🔑 Perplexity API key. 📲 Zalo User API + Telegram Bot API credentials. 📥 Example Use Case A financial analyst or business leader wants a daily briefing in Vietnamese. At 7 AM, they automatically receive a curated 400-word digest via Telegram and Zalo. Can also trigger the report on-demand from chat. 🛠 Customization Options Add/remove RSS sources. Adjust summary length (short/medium/long). Output to other channels (Email, Slack, Notion). Change language from Vietnamese → English. ⚠️ Limitations RSS feeds must be valid & accessible. Summaries depend on AI quality and may vary slightly. Perplexity API requires active subscription. 📌 SEO Tags n8n workflow, rss news summarizer, daily news digest, telegram news bot, zalo ai assistant, openai news summary, perplexity ai, financial political economic news More template: https://aitool.wiki/. An n8n automation workflow template by DuyTran.

By Avkash Kakdiya

How it works This workflow starts whenever a new domain is added to a Google Sheet. It cleans the domain, fetches traffic insights from SimilarWeb, extracts the most relevant metrics, and updates the sheet with enriched data. Optionally, it can also send this information to Airtable for further tracking or analysis. Step-by-step Trigger on New Domain Workflow starts when a new row is added in the Google Sheet. Captures the raw URL/domain entered by the user. Clean Domain URL Strips unnecessary parts like http://, https://, www., and trailing slashes. Stores a clean domain format (e.g., example.com) along with the row number. Fetch Website Analysis Uses the SimilarWeb API to pull traffic and engagement insights for the domain. Data includes global rank, country rank, category rank, total visits, bounce rate, and more. Extract Key Metrics Processes raw SimilarWeb data into a simplified structure. Extracted insights include: Ranks: Global, Country, and Category. Traffic Overview: Total Visits, Bounce Rate, Pages per Visit, Avg Visit Duration. Top Traffic Sources: Direct, Search, Social. Top Countries (Top 3): With traffic share percentages. Device Split: Mobile vs Desktop. Update Google Sheet Writes the cleaned and enriched domain data back into the same (or another) Google Sheet. Ensures each row is updated with the new traffic insights. Export to Airtable (Optional) Creates a new record in Airtable with the enriched traffic metrics. Useful if you want to manage or visualize company/domain data outside of Google Sheets. Why use this? Automatically enriches domain lists with live traffic data from SimilarWeb. Cleans messy URLs into a standard format. Saves hours of manual research on company traffic insights. Provides structured, comparable metrics for better decision-making. Flexible: update sheets, export to Airtable, or both. An n8n automation workflow template by Avkash Kakdiya.

By Trung Tran

SaaS Pricing Brief Generator (Decodo → LLM → Google Docs → PDF → Slack) 🚀 Try Decodo — Web Scraping & Data API (Coupon: TRUNG) Decodo is a powerful public data access platform offering managed web scraping APIs and proxy infrastructure to collect structured web data at scale. It handles proxies, anti-bot protection, JavaScript rendering, retries, and global IP rotation—so you can focus on data, not scraping complexity. Why Decodo Managed Web Scraping API with anti-bot bypass & high success rates Works with JS-heavy sites; outputs JSON/HTML/CSV Easy integration (Python, Node.js, cURL) for eCommerce, SERP, social & general web data 🎟️ Special Discount Use coupon TRUNG to get the Advanced Scraping API plan — 23,000 requests for $5. Who this workflow is for This workflow is designed for Presales, Product Managers, Business Analysts, and Sales teams who need to: Monitor competitor or SaaS pricing pages Convert unstructured pricing content into a structured, comparable format Quickly generate and share an internal pricing brief without manual copy/paste It is especially useful during launches, pricing updates, or quarterly reviews. What this workflow does At a high level, the workflow automates the full pricing intelligence pipeline: Scrapes a live SaaS pricing page using a real browser environment Cleans and normalizes the HTML for reliable parsing Uses an LLM agent to extract pricing plans into structured JSON Builds an executive-ready SaaS pricing brief Publishes the brief as a Google Doc and PDF Shares the final PDF directly to Slack The output is a consistent, repeatable pricing brief ready for internal distribution. How it works Manual Trigger The workflow is manually triggered to ensure intentional execution (ideal for known pricing updates). Configure Target Pricing Page Input the competitor pricing URL, device type, and report metadata. Decodo Pricing Scraper Renders the full pricing page using JS and device emulation so tier cards, modals, and dynamic content are captured correctly. HTML Normalization Custom code removes scripts, styles, and noise, leaving clean, readable text for the LLM. Plan Extraction Agent (LLM) The agent translates messy pricing text into a structured JSON schema including: Plan name Price and billing period Key features CTA / positioning notes Build SaaS Pricing Brief Transforms structured JSON into an executive-ready markdown brief with: Plan comparison table Key differentiators Observations and suggested next actions Publish Assets Creates a Google Doc in a predefined Drive folder and converts it to PDF for sharing. Share in Slack Uploads the PDF directly to a Slack channel (e.g. #pricing-intel) for instant visibility. Requirements Decodo node configured with a valid plan OpenAI / LLM credentials for the Plan Extraction Agent Google Drive API access Slack workspace and upload permissions Notes & best practices Manual trigger avoids unnecessary scraping and rate-limit issues Device emulation ensures accurate pricing capture Structured JSON output enables future extensions (trend tracking, diffing, dashboards) The workflow is modular and easy to adapt for other competitor intelligence use cases. An n8n automation workflow template by Trung Tran.

By InfyOm Technologies

✅ What problem does this workflow solve? Call centers often record conversations for quality control and training, but reviewing every transcript manually is tedious and inefficient. This workflow automates sentiment analysis for each call, providing structured feedback across multiple key categories, so managers can focus on improving performance and training. ⚙️ What does this workflow do? Accepts a Google Sheet containing: Call transcript Agent name Customer name Analyzes each call transcript across multiple sentiment dimensions: 👋 Greeting Sentiment 🧑‍💼 Agent Friendliness ❓ Problem-Solving Sentiment 🙂 Customer Sentiment 👋 Closing Sentiment ✅ Issue Resolved (Yes/No) Add Conversation Topics discussed in a call Calculates an overall call rating based on combined analysis. Updates the Google Sheet with: Individual sentiment scores Issue resolution status Final call rating 🔧 Setup Instructions 📄 Google Sheets Prepare a sheet with the following columns: Transcript Agent Name Customer Name The workflow will append results in new columns automatically: Greeting Sentiment Closing Sentiment Agent Friendliness Problem Solving Customer Sentiment Issue Resolved Overall Call Rating (out of 5 or 10) 🧠 OpenAI Setup Connect OpenAI API to perform NLP-based sentiment classification. For each transcript, use structured prompts to analyze individual components. 🧠 How it Works – Step-by-Step Sheet Scan – The workflow reads rows from the provided Google Sheet. Loop Through Calls – For each transcript, it: Sends prompts to OpenAI to analyze: Greeting tone (friendly/neutral/rude) Problem-solving quality (clear/confusing/helpful) Closing sentiment Agent attitude Customer satisfaction Whether the issue was resolved Calculates a composite rating from all factors. Update Sheet – All analyzed data is written back into the Google Sheet. 📊 Example Output https://docs.google.com/spreadsheets/d/1aWU28D_73nvkDMPfTkPkaV53kHgX7cg0W4NwLzGFEGU/edit?gid=0#gid=0 👤 Who can use this? This workflow is ideal for: ☎️ Call Centers 🎧 Customer Support Teams 🧠 Training & QA Departments 🏢 BPOs or Support Vendors If you want deeper insight into every customer interaction, this workflow delivers quantified, actionable sentiment metrics automatically. 🛠 Customization Ideas 📅 Add scheduled runs (daily/weekly) to auto-analyze new calls. 📝 Export flagged or low-rated calls into a review dashboard. 🧩 Integrate with Slack or email to send alerts for low-score calls. 🗂 Filter by agent, category, or score to track performance trends. 🚀 Ready to Use? Just connect: ✅ Google Sheets (with transcript data) ✅ OpenAI API …and this workflow will automatically turn your raw call transcripts into actionable sentiment insights. An n8n automation workflow template by InfyOm Technologies.

By Matt Chong | n8n Creator

Who is this for? If you’re overwhelmed with incoming emails but only want to be notified about the essentials, this workflow is for you. Perfect for busy professionals who want a short AI summary of new emails delivered directly to Slack. What does it solve? Reading every email wastes time. This workflow filters out the noise by: Automatically summarizing each unread Gmail email using AI Sending you just the sender and a short summary to Slack Helping you stay focused without missing key information How it works Every minute, the workflow checks Gmail for unread emails When it finds one, it: Extracts the email content Sends it to OpenAI’s GPT model for a 250-character summary Delivers the message directly to Slack How to setup? Connect your accounts: Gmail (OAuth2) OpenAI (API key or connected account) Slack (OAuth2) Edit the Slack node: Choose the Slack user/channel to send alerts to Optional: Adjust the AI prompt in the “AI Agent” node to modify the summary style Optional: Change polling frequency in the Gmail Trigger node How to customize this workflow to your needs Edit the AI prompt to: Highlight urgency Include specific keywords Extend or reduce summary length Modify the Slack message format (add emojis, tags, or links). An n8n automation workflow template by Matt Chong | n8n Creator.

By Eddy Medina

Update a Dialogflow Intent's Response via Telegram This template allows you to easily update the response of a Dialogflow intent by simply typing a keyword in Telegram. Ideal for those who need to edit responses without accessing the Dialogflow console. 🔧 What does this flow do? Listens for incoming messages from a Telegram bot using the Telegram Trigger node. Validates the user by ID through the User validation by ID node to ensure only authorized people can execute the action. Checks if the message contains the keyword update using the Keyword validation node. If both conditions are met: Executes an HTTP GET request using the HTTP Request GET node to fetch the full intent in JSON format from the Dialogflow API. The user copies that JSON, edits the response content, and pastes it into the HTTP Request UPDATE node (PATCH). Finally, the flow sends a confirmation message via Telegram using the Mensaje de confirmación node. If the user or keyword is invalid, the bot replies with an error message using the Invalid user message or Invalid keyword message nodes. 📌 Requirements A configured Google API credential (Service Account). Obtain the PROJECT_ID and INTENT_ID from the intent's URL in Dialogflow. Edit the jsonBody content in the HTTP Request UPDATE node, removing the outer curly braces {}. ✅ Use Cases Quickly modify responses in production without accessing Dialogflow. Allow non-technical users to update intents from Telegram. Foundation for more advanced flows that dynamically manage multiple intents. An n8n automation workflow template by Eddy Medina.

By Nalin

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Complete account-based outreach automation with Octave context engine Who is this for? Revenue teams, account-based marketing professionals, and growth operators who want a complete, automated pipeline from account identification to contextualized outreach. Built for teams ready to move beyond fragmented point solutions to an integrated, context-aware GTM engine. What problem does this solve? Most GTM teams are flying blind with disconnected tools that can't talk to each other. You qualify accounts in one system, find contacts in another, research context manually, then hope your email sequences land. Each step loses context, and by the time you're writing outreach, you've forgotten why the account was qualified in the first place. Octave centralizes all this typically fragmented context - your ICP definitions, personas, value propositions, and business logic - so every agent operation can act on the same unified understanding of your market. This workflow demonstrates how Octave's agents work together seamlessly because they all share the same context foundation. What this workflow does Complete Account-to-Outreach Pipeline: This workflow demonstrates the full power of Octave's context engine by connecting multiple agent operations in a seamless flow. Unlike traditional tools that lose context at each handoff, Octave centralizes your business context - ICP definitions, personas, value propositions, competitive positioning - so every agent operates from the same unified understanding of your market. External Context Research: Gathers real-time external data about target accounts (job postings, news, funding, etc.) Processes this information to create runtime context for later use in outreach Establishes the "why reach out now" foundation for the entire workflow Company-Level Qualification: Uses Octave's company qualification to assess account fit against your specific offering Leverages Product and Segment-level fit criteria defined in your Library Filters out accounts that don't meet your qualification thresholds Ensures only high-potential accounts proceed through the workflow Intelligent Contact Discovery: Runs Octave's prospector agent on qualified accounts Finds relevant stakeholders based on responsibilities and business context, not just job titles Discovers multiple contacts per account for comprehensive coverage Maintains qualification context when identifying the right people Runtime Context Integration: Takes the external context gathered at the beginning and injects it into sequence generation Creates truly dynamic, timely outreach that references current company events Generates sequences that feel impossibly relevant and well-researched Multi-Contact Sequence Generation: Splits discovered contacts into individual records for processing Generates contextualized email sequences for each contact Maintains account-level context while creating contact-specific messaging Produces sequences (1-7 emails) that feel unmistakably meant for each person Automated Campaign Deployment: Automatically adds all qualified contacts with their contextualized sequences to email campaigns Maps dynamic content to campaign variables for seamless execution Maintains the context chain from qualification through delivery Setup Required Credentials: Octave API key and workspace access External data source API (job boards, news APIs, enrichment services, etc.) Email platform API key (Instantly.ai configured, easily adaptable) Optional: LLM credentials if using the example external research agent Step-by-Step Configuration: Set up Account Input Source: Replace your-webhook-path-here with a unique, secure path Configure your account source (CRM, website visitors, target lists) to send company data Ensure account data includes company name and domain for processing Configure External Context Research: Replace the example AI agent with your preferred external data source Set up connections to job boards, news APIs, or enrichment services Configure context gathering to find timely, relevant information about target accounts Set up Company Qualification Agent: Add your Octave API credentials Replace your-octave-company-qualification-agent-id with your actual agent ID Configure qualification criteria at Product and Segment levels in your Octave Library Configure Prospector Agent: Replace your-octave-prospector-agent-id with your actual prospector agent ID Define target personas and stakeholder types in your Octave Library Set contact discovery parameters for optimal coverage Set up Sequence Agent: Replace your-octave-sequence-agent-id with your actual sequence agent ID Configure runtime context integration for dynamic content Test sequence quality with the external context integration Configure Email Campaign Platform: Add your email platform API credentials Replace your-campaign-id-here with your actual campaign ID Ensure campaign supports custom variables for dynamic content Required Webhook Payload Format: { "body": { "companyName": "InnovateTech Solutions", "companyDomain": "innovatetech.com" } } How to customize External Context Sources: Replace the example research with your data sources: Job Board APIs:** Reference current hiring and team expansion News APIs:** Mention funding, product launches, or market expansion Enrichment Services:** Pull technology adoption, market changes, or competitive moves Social Monitoring:** Reference recent company posts or industry discussions Company Qualification: Configure qualification in your Octave company qualification agent: Product Level:** Define "good fit" and "bad fit" questions for your core offering Segment Level:** Set criteria for different market segments or use cases Qualification Thresholds:** Adjust the filter score based on your standards Contact Discovery: Customize prospecting in your Octave prospector agent: Target Personas:** Define which Library personas to prioritize Organizational Levels:** Focus on specific seniority levels or decision-making authority Contact Volume:** Adjust how many contacts to discover per qualified account Runtime Context Integration: Configure dynamic content injection: Context Definition:** Specify what external data represents in your sequences Usage Instructions:** Define how to incorporate context into messaging Email-Level Control:** Apply different context to different emails in sequences Sequence Generation: Customize email creation: Core Context (Library):** Define personas, use cases, and offering definitions Strategy (Playbooks):** Configure messaging frameworks and value propositions Writing Style (Agent):** Adjust tone, voice, and communication approach Campaign Integration: Adapt for different email platforms: Update API endpoints and authentication for your preferred platform Modify variable mapping for platform-specific requirements Adjust sequence formatting and length based on platform capabilities Use Cases Complete inbound lead processing from website visitor to qualified outreach Event-triggered account processing for funding announcements or hiring spikes Competitive displacement campaigns with account qualification and contact discovery Market expansion automation for entering new territories or segments Product launch outreach with context-aware targeting and messaging Customer expansion workflows for upselling within existing account bases. An n8n automation workflow template by Nalin.

By Nalin

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Generate dynamic email sequences with runtime context and external data Who is this for? Growth teams, sales development reps, and outbound marketers who want to reference specific, real-time information about prospects in their email sequences. Built for teams that have access to external data sources and want to create truly contextualized outreach that feels impossibly relevant. What problem does this solve? Most outbound sequences are static - they use the same messaging for everyone regardless of what's actually happening at the prospect's company right now. You might know they're hiring, launched a product, got funding, or expanded to new markets, but your email sequences can't dynamically reference these timely events. This workflow shows how to inject real-time external context into Octave's sequence generation, creating outreach that feels like you're personally monitoring each prospect's company. What this workflow does Lead Data & Context Collection: Receives lead information via webhook (firstName, companyName, companyDomain, profileURL, jobTitle) Uses external data sources to gather timely context about the prospect's company Example: AI agent researches current job postings to find roles they're actively hiring for Processes this context into structured data for sequence generation Runtime Context Integration: Feeds external context into Octave's sequence generation as "runtime context" Defines both WHAT the context is ("they are hiring a software engineer") and HOW to use it ("mention the role in the opening") Allows Octave to weave timely, relevant details into each email naturally Creates sequences that feel like personal research rather than mass outreach Dynamic Sequence Generation: Leverages Octave's context engine plus runtime data to create hyper-relevant sequences (1-7 emails) Generates subject lines and email content that reference specific, current company context Maintains your positioning and value prop while incorporating timely relevance Creates messaging that feels unmistakably meant for that specific moment in the prospect's business Campaign Integration: Automatically adds leads with contextualized sequences to your email platform Maps generated content to campaign variables for automated sending Supports multiple email platforms with easy customization Setup Required Credentials: Octave API key and workspace access External data source API (job boards, news APIs, enrichment services, etc.) Email platform API key (Instantly.ai configured, easily adaptable) Optional: LLM credentials if using the example AI agent for testing Step-by-Step Configuration: Set up External Data Source: Replace the AI Agent with your preferred data source (job board APIs, news APIs, company databases) Configure data collection to find relevant, timely information about prospects Structure the output to provide clean context for sequence generation Set up Octave Sequence Agent: Add your Octave API credentials in n8n Replace your-octave-sequence-agent-id with your actual sequence agent ID Configure runtime context parameters: Runtime Context: Define WHAT the external data represents Runtime Instructions: Specify HOW to use it in the messaging Configure Email Platform: Add your email platform API credentials Replace your-campaign-id-here with your actual campaign ID Ensure campaign supports custom variables for dynamic content Set up Lead Source: Replace your-webhook-path-here with a unique, secure path Configure your lead source to send prospect data to the webhook Test end-to-end flow with sample leads Required Webhook Payload Format: { "body": { "firstName": "Alex", "lastName": "Chen", "companyName": "InnovateTech", "companyDomain": "innovatetech.com", "profileURL": "https://linkedin.com/in/alexchen", "email": "alex@innovatetech.com", "jobTitle": "VP of Engineering" } } How to customize External Data Sources: Replace the AI agent with your preferred context collection method: Job Board APIs:** Reference current hiring needs and team expansion News APIs:** Mention recent company announcements, funding, or product launches Social Media Monitoring:** Reference recent LinkedIn posts, company updates, or industry discussions Enrichment Services:** Pull real-time company data, technology stack changes, or market expansion Runtime Context Configuration: Customize how external data integrates with sequences: Context Definition:** Specify what the external data represents ("they just raised Series B funding") Usage Instructions:** Define how to incorporate it ("mention the funding in the opening and tie it to growth challenges") Email-Level Control:** Configure different context usage for different emails in the sequence Global vs. Specific:** Apply context to all emails or target specific messages Data Processing: Replace the example AI agent with your external data processing: Modify data source connections to pull relevant context Ensure consistent output formatting for runtime context integration Add error handling for cases where external data isn't available Implement fallback context for prospects without relevant external data Sequence Customization: Configure Octave sequence generation: Core Context (Library):** Define your personas, use cases, and offering definitions Strategy (Playbooks):** Configure messaging frameworks and value proposition delivery Writing Style (Agent):** Adjust tone, voice, and communication style Email Platform Integration: Adapt for different email sequencing platforms: Update API endpoints and authentication for your preferred platform Modify variable mapping for platform-specific custom fields Adjust sequence length and formatting requirements Use Cases Job posting-triggered outreach for hiring managers and HR teams Funding announcement follow-ups for growth-stage companies Product launch congratulations with relevant use case discussions Market expansion outreach when companies enter new territories Technology adoption sequences based on recent stack additions Event attendance follow-ups with session-specific references. An n8n automation workflow template by Nalin.