Browse 12,955 Workflows

By Nima Salimi

Description🔍 This n8n workflow is a complete marketing automation system that connects to your CDP (Customer Data Platform), selects which flows to send, and delivers personalized emails using Brevo. It's modular and extensible — you can also add SMS, push notifications, Telegram messages, or other channels. To build a full marketing automation system, you need four key components: Workflow Automation – using n8n (this workflow) CDP – store and manage user data (e.g., NocoDB, Metabase, Power BI, etc.) Database – track transactions, templates, and send statuses (e.g., NocoDB) BI / Analytics – monitor performance by flows, journeys, and sent events This workflow represents the Workflow Automation layer. You can connect it to your own data stack or use the included example databases (cdp-ecrm, n8n-templates-ecrm, and n8n-transaction-ecrm) to get started quickly. 👤 Who’s it for? Growth & CRM teams managing user engagement flows Ecommerce marketers running time-sensitive email journeys Marketing automation pros using low-code CRM stacks Data teams building custom campaign triggers from CDPs ✅ Features 🔁 Two modular flows: "Insert user_id" and "Sending Email" 🧠 Select flow using flow_id from templates in NocoDB ✏️ Insert user data into n8n-transaction-ecrm with processing status 🔍 Filter duplicate users by user_id to avoid over-sending 📧 Validate email fields and flag disposables 📨 Send personalized emails using Brevo template parameters 📊 Track delivery with sent_result, sent_at, and status updates 🕒 Runs every 30 minutes via schedule trigger 🛠 How to Use Set your flow In the Setup Flow node, change the flow_id to match a row in your n8n-templates-ecrm table. Prepare your tables in NocoDB cdp-ecrm: contains users (user_id, email, first_name, phone_number) n8n-templates-ecrm: contains flows with metadata n8n-transaction-ecrm: stores and updates user send status Configure credentials NocoDB API Token Brevo (Sendinblue) API Key Trigger the flows Run “Insert user_id” manually or on a schedule to prepare users “Sending Email” runs automatically every 30 minutes 📌 Notes Disposable email domains are filtered using regex Status: 0-processing → just inserted 1-sending → ready to send 2-sent → email sent successfully 3-no-email → missing email address 4-disposal-email → disposable or banned email Easily duplicate the "Insert user_id" flow to add more campaigns. An n8n automation workflow template by Nima Salimi.

By David Olusola

Overview Supercharge your insurance agency's efficiency with this powerful automation template for n8n. Designed specifically for commercial insurance brokers and agents, this workflow transforms the tedious process of manual application submissions into a streamlined, one-click operation. Stop wasting hours on administrative tasks and start closing more deals. This template handles everything from reading new applications in a Google Sheet to generating custom PDFs and emailing them to the right carriers all in 40 seconds, allowing you to focus on what matters most: your clients. How it works This workflow provides a powerful foundation for automating your commercial insurance submissions. It's designed to save you hours of manual work by streamlining the entire process from application intake to carrier communication. At a high level, this is what the flow does: Fetches New Applications:** Automatically reads new insurance applications from a designated Google Sheet. Filters Suitable Carriers:** Filters a built-in list of carriers to find the best matches for each application based on revenue and industry requirements. Generates Professional PDFs:** For each matched carrier, it automatically generates a professional PDF application using a pre-formatted Google Docs template. Distributes to Carriers:** Emails the personalized application and unique PDF attachment to each matched carrier. Creates a Summary Report:** Once all submissions are complete, it generates a clean HTML summary report and emails it to the broker. Set up steps Estimated Set Up Time: 10-15 minutes This template is designed for a quick setup. The detailed, step-by-step instructions are included in the Sticky Notes inside the workflow itself. The main setup steps are: Copy the Google Sheet:** Make a copy of the provided Google Sheet template to your own Google Drive. Connect Your Google Account:** Authorize your Google account for the three required nodes (Google Sheets, Google Drive, and Google Docs). Configure Your Email:** Add your email credentials to the two Email Send nodes (one for sending to carriers and one for notifying the broker). An n8n automation workflow template by David Olusola.

By Pavlo Hurhu

This n8n workflow promotes your brand/company/platform by mentioning it in Twitter comments. The responses look human-like, the workflow is robust and designed to avoid bans. Good to know The workflow is configured to maximize efficiency while minimizing costs and ensuring your Twitter account won't get banned or shadow-banned. Generating more than 17 comments per day would require a paid Twitter subscription plan. How it works The User sets a keyword that would be used to find relevant Posts. An AI Agent analyzes each Post and writes a response, promoting User's Brand. After each reponse is submitted, the result is logged in a Report Table for tracking and convenience. Set up steps Set your target keyword and start the workflow. Detailed instructions and tutorials can be found in the workflow's sticky notes. Requirements Twitter and Google accounts. twitterapi.io subscription (used to overcome official Twitter API limitaions). Anthropic subscription (GPT models are also supported, but I personally recommend using Anthropic Claude Sonnet 4 for text generation). An n8n automation workflow template by Pavlo Hurhu.

By vinci-king-01

Smart Supplier Health Monitor with ScrapeGraphAI Risk Detection and Multi-Channel Alerts 🎯 Target Audience Procurement managers and directors Supply chain risk analysts CFOs and financial controllers Vendor management teams Enterprise risk managers Operations managers Contract administrators Business continuity planners 🚀 Problem Statement Manual supplier monitoring is reactive and time-consuming, often missing early warning signs of financial distress that could disrupt your supply chain. This template solves the challenge of proactive supplier health surveillance by automatically monitoring financial indicators, news sentiment, and market conditions to predict supplier risks before they impact your business operations. 🔧 How it Works This workflow automatically monitors your critical suppliers' financial health using AI-powered web scraping, analyzes multiple risk factors, identifies alternative suppliers when needed, and sends intelligent alerts through multiple channels to ensure your procurement team can act quickly on emerging risks. Key Components Weekly Health Check Scheduler - Automated trigger based on supplier criticality levels Supplier Database Loader - Dynamic supplier portfolio management with risk-based monitoring frequency ScrapeGraphAI Website Analyzer - AI-powered extraction of financial health indicators from company websites Financial News Scraper - Intelligent monitoring of financial news and sentiment analysis Advanced Risk Scorer - Industry-adjusted risk calculation with failure probability modeling Alternative Supplier Finder - Automated identification and ranking of backup suppliers Multi-Channel Alert System - Email, Slack, and API notifications with escalation rules 📊 Risk Analysis Specifications The template performs comprehensive financial health analysis with the following parameters: | Risk Factor | Weight | Score Impact | Description | |-------------|--------|--------------|-------------| | Financial Issues | 40% | +0-24 points | Revenue decline, debt levels, cash flow problems | | Operational Risks | 30% | +0-18 points | Management changes, restructuring, capacity issues | | Market Risks | 20% | +0-12 points | Industry disruption, regulatory changes, competition | | Reputational Risks | 10% | +0-6 points | Negative news, legal issues, public sentiment | Industry Risk Multipliers: Technology: 1.1x (Higher volatility) Manufacturing: 1.0x (Baseline) Energy: 1.2x (Regulatory risks) Financial: 1.3x (Market sensitivity) Logistics: 0.9x (Generally stable) Risk Levels & Actions: Critical Risk**: Score ≥ 75 (CEO/CFO escalation, immediate transition planning) High Risk**: Score ≥ 55 (Procurement director escalation, backup activation) Medium Risk**: Score ≥ 35 (Manager review, increased monitoring) Low Risk**: Score < 35 (Standard monitoring) 🏢 Supplier Management Features | Feature | Critical Suppliers | High Priority | Medium Priority | |---------|-------------------|---------------|-----------------| | Monitoring Frequency | Weekly | Bi-weekly | Monthly | | Risk Threshold | 35+ points | 40+ points | 50+ points | | Alert Recipients | C-Level + Directors | Directors + Managers | Managers only | | Alternative Suppliers | 3+ pre-qualified | 2+ identified | 1+ researched | | Transition Timeline | 24-48 hours | 1-2 weeks | 1-3 months | 🛠️ Setup Instructions Estimated setup time: 25-30 minutes Prerequisites n8n instance with community nodes enabled ScrapeGraphAI API account and credentials Gmail account for email alerts (or alternative email service) Slack workspace with webhook or bot token Supplier database or CRM system API access Basic understanding of procurement processes Step-by-Step Configuration 1. Configure ScrapeGraphAI Credentials Sign up for ScrapeGraphAI API account Navigate to Credentials in your n8n instance Add new ScrapeGraphAI API credentials with your API key Test the connection to ensure proper functionality 2. Set up Email Integration Add Gmail OAuth2 credentials in n8n Configure sender email and authentication Test email delivery with sample message Set up email templates for different risk levels 3. Configure Slack Integration Create Slack webhook URL or bot token Add Slack credentials to n8n Configure target channels for different alert types Customize Slack message formatting and buttons 4. Load Supplier Database Update the "Supplier Database Loader" node with your supplier data Configure supplier categories, contract values, and criticality levels Set monitoring frequencies based on supplier importance Add supplier website URLs and contact information 5. Customize Risk Parameters Adjust industry risk multipliers for your business context Modify risk scoring thresholds based on risk tolerance Configure economic factor adjustments Set failure probability calculation parameters 6. Configure Alternative Supplier Database Populate the alternative supplier database in the "Alternative Supplier Finder" node Add supplier ratings, capacities, and specialties Configure geographic coverage and certification requirements Set suitability scoring parameters 7. Set up Procurement System Integration Configure the procurement system webhook endpoint Add API authentication credentials Test webhook payload delivery Set up automated data synchronization 8. Test and Validate Run test scenarios with sample supplier data Verify ScrapeGraphAI extraction accuracy Check risk scoring calculations and thresholds Confirm all alert channels are working properly Test alternative supplier recommendations 🔄 Workflow Customization Options Modify Risk Analysis Add custom risk indicators specific to your industry Implement sector-specific economic adjustments Configure contract-specific risk factors Add ESG (Environmental, Social, Governance) scoring Extend Data Sources Integrate credit rating agency APIs (Dun & Bradstreet, Experian) Add financial database connections (Bloomberg, Reuters) Include social media sentiment analysis Connect to government regulatory databases Enhance Alternative Supplier Management Add automated supplier qualification workflows Implement dynamic pricing comparison Create supplier performance scorecards Add geographic risk assessment Advanced Analytics Implement predictive failure modeling Add supplier portfolio optimization Create supply chain risk heatmaps Generate automated compliance reports 📈 Use Cases Supply Chain Risk Management**: Proactive monitoring of supplier financial stability Procurement Optimization**: Data-driven supplier selection and management Business Continuity Planning**: Automated backup supplier identification Financial Risk Assessment**: Early warning system for supplier defaults Contract Management**: Risk-based contract renewal and negotiation Vendor Diversification**: Strategic supplier portfolio management 🚨 Important Notes Respect ScrapeGraphAI API rate limits and terms of service Implement appropriate delays between supplier assessments Keep all API credentials secure and rotate them regularly Monitor API usage to manage costs effectively Ensure compliance with data privacy regulations (GDPR, CCPA) Regularly update supplier databases and contact information Review and adjust risk parameters based on market conditions Maintain confidentiality of supplier financial information 🔧 Troubleshooting Common Issues: ScrapeGraphAI extraction errors: Check API key validity and rate limits Email delivery failures: Verify Gmail credentials and permissions Slack notification failures: Check webhook URL and channel permissions False positive alerts: Adjust risk scoring thresholds and industry multipliers Missing supplier data: Verify website URLs and accessibility Alternative supplier errors: Check supplier database completeness Monitoring Best Practices: Set up workflow execution monitoring and error alerts Regularly review and update supplier information Monitor API usage and costs across all integrations Validate risk scoring accuracy with historical data Test disaster recovery and backup procedures Support Resources: ScrapeGraphAI documentation and API reference n8n community forums for workflow assistance Procurement best practices and industry standards Financial risk assessment methodologies Supply chain management resources and tools. An n8n automation workflow template by vinci-king-01.

By Avkash Kakdiya

How it works This workflow enhances contact intelligence by retrieving new or updated contact data, enriching it using AI and external APIs, and then updating your CRM or contact management system with intelligent insights. It automates the process of gathering, enriching, and organizing contact information to improve targeting, personalization, and engagement. Step-by-step 1. Trigger & Input The workflow is triggered by a scheduler or webhook event. It reads a new contact entry (or an updated one) from your source, such as a spreadsheet or form. Basic fields like name, email, and company are used as the starting point for enrichment. 2. Contact Lookup & Parsing The contact's domain or company is extracted and used to perform a lookup via an external data source. Data such as company details, job title, or LinkedIn profile is retrieved. Parsed and cleaned to remove duplicates, missing values, or invalid results. 3. AI Enrichment The enriched contact is passed through an AI model (such as GPT or another NLP service). The model analyzes job role, seniority, and inferred interests based on available data. Insights like intent, persona category, or engagement score are generated. 4. Validation & Tagging The AI-enriched data is validated to ensure consistency and accuracy. Tags and segments (e.g., "Decision Maker", "Technical Buyer", etc.) are assigned based on rules or AI inference. This enables smart filtering, targeting, and routing later in your CRM or campaigns. 5. Output & Integration The final enriched and validated contact is written back to your CRM, sheet, or marketing platform. The system also: Sends a Slack/Email alert with a summary. Updates the original contact entry with a "Processed" or "Enriched" status. Triggers next steps, such as personalized outreach or nurture sequences. Benefits Enhances Contact Profiles with AI-generated insights and third-party data. Improves Segmentation & Targeting through smart tags and persona classification. Automates Manual Research, saving time and improving accuracy. Easily Extendable by adding more AI models, data sources, or CRM integrations. An n8n automation workflow template by Avkash Kakdiya.

By Gulfiia

UX Interview Analysis with OpenAI: Transcipt, Summarize, and Export to Google Sheets!* About Easily analyze and summarize UX interviews. Just upload your files to Google Drive and get the insights directly in Google Sheets. How It Works The workflow is triggered manually Upload the interview recordings in MP3 format to Google Drive (or modify the node “Filter by MP3” to support other formats) OpenAI transcribes the audio An AI agent generates a summary Store the results in Google Sheets How To Use Import the package into your n8n interface Set up credentials for each node to access the required tools Upload your interview files to Google Drive Create a Google Sheet with the following columns: • Persona • User Needs • Pain Points • New Feature Requests Connect the Google Sheets node titled “Insert results to Google Sheets” to your created document Start the workflow Requirements OpenAI for transcription and summarization (you can replace it with Gemini if preferred). An n8n automation workflow template by Gulfiia.

By WeblineIndia

GitHub PR Deep-Link & Routing Validator (ExecuteCommand + GitHub Comment) 🚀 Quick-Start TL;DR Import the workflow JSON into n8n (Cloud or self-hosted). Create a GitHub Personal Access Token with repo:public_repo (or repo) scope and add it to n8n credentials. Open the “CONFIG - Variables” node and tweak: manifestPath – path to your deep-link manifest (AndroidManifest.xml, Info.plist, etc.). scriptPath – helper script that boots the emulator & checks each route. Enable the workflow. Every push to a PR branch triggers validation and posts a Markdown pass/fail matrix back to the PR. What It Does This workflow delivers an automated, CI-friendly smoke-test of every deep link defined in your mobile app. On each push to an open GitHub PR, it: Clones the PR branch. Runs a lightweight validation script (provided) that spins up an emulator/simulator, attempts to open each declared URI, and records OK/FAIL. Generates a Markdown table summarizing the results. Comments that table in the PR, letting reviewers spot broken schemes at a glance. Who’s It For Mobile teams maintaining Android or iOS deep-link manifests. CI engineers who need a simple, language-agnostic check they can publish to each PR. OSS maintainers wanting a template-library-ready n8n recipe. Requirements | Requirement | Notes | |-------------|-------| | n8n Cloud / CE | Works everywhere; self-hosted users need Docker with Android / Xcode if validating on-runner. | | GitHub Personal Access Token | Used for posting PR comments. | | Emulator-capable runner | Local dev hardware or CI image that can run adb / xcrun simctl. | How It Works GitHub Trigger fires on pull_request → synchronize (i.e., each push to the PR branch). Set (CONFIG - Variables) centralises repo URL, manifest path, script path, timeout, and comment mode. ExecuteCommand clones the repo and calls the validation script. Function converts CLI CSV output into a Markdown table. GitHub node posts (or appends) the results as a comment on the PR. How To Set Up Auth: In n8n, add a GitHub credential with your PAT named “GitHub Personal Access Token”. Import: Settings → Import workflow and paste the JSON above. Edit Config: Double-click CONFIG - Variables and change any default values. Validation Script: Commit scripts/validate_deeplinks.sh into your repo (see sample below). Enable the workflow. Push to any PR branch and watch the comment appear. Sample validate_deeplinks.sh #!/usr/bin/env bash set -e while getopts "m:" opt; do case $opt in m) MANIFEST="$OPTARG" ;; esac done echo "⇨ Parsing deep links from $MANIFEST" rudimentary parser—replace with something smarter for XML/Plist grep -oE 'http[s]?://+' "$MANIFEST" | while read -r uri; do if adb shell am start -W -a android.intent.action.VIEW -d "$uri" >/dev/null 2>&1; then echo "$uri,OK" else echo "$uri,FAIL" fi done How To Customise Multiple manifests:** duplicate the Execute-Command step or extend the script to accept a list. Replace-latest comment:** switch commentMode to replace-latest and update the GitHub node to search for the newest bot comment before editing. Status checks instead of comments:** call the GitHub → “Create Commit Status” endpoint. Add-Ons | Add-On | Idea | |--------|------| | Multi-platform sweep | Loop over Android + iOS manifests and aggregate results. | | Slack/Teams alert | Push failures into your chat of choice via Incoming-Webhook node. | | Parallel device grid | Trigger multiple emulators (API 19 → 34) to catch OS-specific issues. | Use Case Examples Ensure new features don’t break existing URI schemes before merge. Catch mis-typed hosts/paths introduced by junior devs. Baseline check on dependency bumps (e.g., upgrading Navigation libraries). Validate white-label builds that override path segments. Automated QA gate that blocks merge if any link fails. (…and many more!) Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|---------------|----------| | Workflow hangs at “Execute – Validate” | Emulator image isn’t installed | Pre-install SDK & start the emulator in a startup script | | PR comment missing | Token lacks repo scope | Regenerate PAT with proper scopes | | All links marked FAIL | Manifest path incorrect | Update manifestPath in CONFIG | | Command node hits timeout | Huge manifest / slow CI | Increase timeoutSecs in CONFIG | Need a Hand? 🤝 Stuck or want to extend this with multi-platform coverage? WeblineIndia’s automation experts can help. Drop us a note to fine-tune or scale out your n8n workflows — fast. An n8n automation workflow template by WeblineIndia.

By Trung Tran

🎙️ VoiceScribe AI: Telegram Audio Message Auto Transcription with OpenAI Whisper > Automatically transcribe Telegram voice messages and store them as structured logs in Google Sheets, while backing up the audio in Google Drive. 🧑‍💼 Who’s it for Journalists, content creators, or busy professionals who often record voice memos or short interviews on the go. Anyone who wants to turn voice recordings into searchable, structured notes. ⚙️ How it works / What it does User sends a voice message to a Telegram bot. n8n checks if the message is an audio voice note. If valid, it downloads the audio file and: Transcribes it using OpenAI Whisper (or your LLM of choice). Uploads the original audio to Google Drive for safekeeping. The transcript and audio metadata are merged. The workflow: Logs the data into a Google Sheet. Sends a formatted confirmation message to the user via Telegram. If the input is not audio, the bot politely informs the user that only voice messages are accepted. ✅ Features Accepts only Telegram voice messages. Transcribes via OpenAI Whisper. Logs DateTime, Duration, Transcript, and Audio URL to Google Sheets. Sends user feedback message via Telegram with download + transcript link. 🚀 How to set up Prerequisites Telegram Bot connected to n8n (via Telegram Trigger) Google Drive & Google Sheets credentials configured OpenAI or Whisper API credentials (for transcription) Steps Telegram Trigger Start the flow when a new message is sent to your bot. Check Message Type Use a conditional node to confirm it's a voice message. Download Voice Message Download the .oga file from Telegram. Transcribe Audio Send the binary audio to OpenAI Whisper or your transcription service. Upload to Google Drive Backup the original audio file. Merge Outputs Combine transcription with Drive metadata. Transform to Row Format Prepare structured JSON for Google Sheets. Append to Google Sheet Store the transcript log (DateTime, Duration, Transcript, AudioURL). Send Confirmation to User Inform the user via Telegram with their transcript and download link. Unsupported Message Handler Reply to users who send non-audio messages. 📄 Example Output in Google Sheet | DateTime | Duration | Transcript | AudioURL | |-----------------------|----------|--------------------------------------------|------------------------------------------------------------| | 2025-08-07T13:12:19Z | 27 | Dự án Outlet Activation là... | https://drive.google.com/uc?id=xxxx&export=download | 🧠 How to customize the workflow Swap Whisper with Deepgram, AssemblyAI, or other providers. Add speaker name detection or prompt-based tagging via GPT. Route transcripts into Notion, Airtable, or CRM systems. Add multi-language support or summarization steps. 📦 Requirements | Component | Required | |---------------------|----------| | Telegram API | ✅ | | Google Drive API | ✅ | | Google Sheets API | ✅ | | OpenAI Whisper API | ✅ | | n8n Cloud or Self-hosted | ✅ | Created with ❤️ using n8n. An n8n automation workflow template by Trung Tran.

By Rosh Ragel

Automatically Send Weekly Sales Reports from Square via Gmail What It Does This workflow automatically connects to the Square API and generates a weekly sales summary report for all your Square locations. The report matches the figures displayed in Square Dashboard > Reports > Sales Summary. It's designed to run weekly and pull the previous week’s sales into a CSV file, which is then sent to a manager/finance team for analysis. This workflow builds on my previous template, which allows users to automatically pull data from the Square API into n8n for processing. (See here: https://n8n.io/workflows/6358) Prerequisites To use this workflow, you'll need: A Square API credential (configured as a Header Auth credential) A Microsoft Outlook credential How to Set Up Square Credentials: Go to Credentials > Create New Choose Header Auth Set the Name to Authorization Set the Value to your Square Access Token (e.g., Bearer <your-api-key>) How It Works Trigger: The workflow runs every Monday at 8:00 AM Fetch Locations: An HTTP request retrieves all Square locations linked to your account Fetch Orders: For each location, an HTTP request pulls completed orders for the previous week (e.g., Monday to Sunday) Filter Empty Locations: Locations with no sales are ignored Aggregate Sales Data: A Code node processes the order data and produces a summary identical to Square’s built-in Sales Summary report Create CSV File: A CSV file is created containing the relevant data Send Email: An email is sent to the chosen third party Example Use Cases Automatically send weekly Square sales data to management to improve the quality of planning and scheduling decisions Automatically send data to an external third party, such as a landlord or agent, who is paid via commission Automatically send data to a bookkeeper for entry into QuickBooks How to Use Configure both HTTP Request nodes to use your Square API credential Set the workflow to Active so it runs automatically Enter the email address of the person you want to send the report to and update the message body If you want to remove the n8n attribution, you can do so in the last node Customization Options Add pagination to handle locations with more than 1,000 orders per week Why It's Useful This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data — whether for operations, finance, or performance monitoring. An n8n automation workflow template by Rosh Ragel.

By Jason Krol

Using the power and ease of Telegram, send a simple text or audio message to a bot with a request to add a new Task to your Notion Tasks database. How it works ChatGPT is used to transacribe the audio or text message, parse it, and determine the title to add as a new Notion Task. You can optionally include a "do date" as well and ChatGPT will include that when creating the task. Once complete you will receive a simple confirmation message back. Minimal Setup Required Just follow n8n's instructions on how to connect to Telegram and create your own chatBot, provide the chatID in the 2 Telegram nodes, and you're finished! A few optional settings include tweaking the ChatGPT system prompt (unnecessary) and the timezone for your Notion Task(s). An n8n automation workflow template by Jason Krol.

By Rosh Ragel

Automatically Send Square Summary Report for Yesterday's Sales via Microsoft Outlook What It Does This workflow automatically connects to the Square API and generates a daily sales summary report for all your Square locations. The report matches the figures displayed in Square Dashboard > Reports > Sales Summary. It's designed to run daily and pull the previous day's sales into a CSV file, which is then sent to a manager/finance team for analysis. This workflow builds on my previous template, which allows users to automatically pull data from the Square API into n8n for processing. (See here: https://n8n.io/workflows/6358) Prerequisites To use this workflow, you'll need: A Square API credential (configured as a Header Auth credential) A Microsoft Outlook credential How to Set Up Square Credentials: Go to Credentials > Create New Choose Header Auth Set the Name to Authorization Set the Value to your Square Access Token (e.g., Bearer <your-api-key>) How It Works Trigger: The workflow runs every day at 4:00 AM Fetch Locations: An HTTP request retrieves all Square locations linked to your account Fetch Orders: For each location, an HTTP request pulls completed orders for the specified report_date Filter Empty Locations: Locations with no sales are ignored Aggregate Sales Data: A Code node processes the order data and produces a summary identical to Square’s built-in Sales Summary report Create CSV File: A CSV file is created containing the relevant data Send Email: An email is sent to the chosen third party Example Use Cases Automatically send Square sales data to management to improve the quality of planning and scheduling decisions Automatically send data to an external third party, such as a landlord or agent, who is paid via commission Automatically send data to a bookkeeper for entry into QuickBooks How to Use Configure both HTTP Request nodes to use your Square API credential Set the workflow to Active so it runs automatically Enter the email address of the person you want to send the report to and update the message body If you want to remove the n8n attribution, you can do so in the last node Customization Options Add pagination to handle locations with more than 1,000 orders per day Instead of a daily summary, you can modify this workflow to produce a weekly summary once a week Why It's Useful This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data — whether for operations, finance, or performance monitoring. An n8n automation workflow template by Rosh Ragel.

By Matheus Pedrosa

Who is this template for? This template is ideal for n8n instance administrators, developers, and DevOps teams who need a proactive and organized way to monitor the health of their automations. If you want to be notified about failures as soon as they happen, without having to manually check execution logs, this workflow is for you. What does this template do? This workflow automates error monitoring on your n8n instance. Every hour, it performs the following steps: Queries the n8n API to fetch all executions that have failed in the last hour. Groups the errors by workflow to consolidate the information. Builds a rich message for each failed workflow, including the error count. Sends an alert to a Slack channel with a button to open the workflow directly, allowing for immediate investigation. Requirements Before you start, you will need to have the following configured in your n8n instance: n8n API Credentials:** You need to generate an API key in your n8n instance settings so the workflow can query execution data. Slack Credentials:* A configured *Slack (OAuth2 API)** credential to allow n8n to send messages to your workspace. How to set it up Setup is simple and only takes a few minutes: Config Node: In the node named "Config", you must set the value for the baseUrl to your n8n instance's URL (e.g., https://n8n.yourdomain.com). This is crucial for generating the correct workflow links in the Slack message. Schedule Trigger: The workflow is pre-configured to run every hour. You can adjust the frequency in this node to fit your needs. "Get Failed Executions" Node (HTTP Request): Under Authentication, select 'Header Auth'. In the Credentials field, select your n8n API credential. "Post to Slack" Node (Slack): Select your Slack credential. In the Channel field, enter the name of the channel where error notifications should be sent (e.g., #n8n-alerts). Activate the Workflow! After these steps, just activate the workflow to start the automatic error monitoring. How to customize the workflow You can easily customize this template: Change the Schedule:** Modify the Schedule Trigger node to run at different intervals (every 15 minutes, once a day, etc.). Change the Notification Channel:** Instead of Slack, you can replace the last node to send notifications to Discord, Microsoft Teams, Telegram, or even by email. Add More Information:** You can modify the MakeMessage node that generates the message to include more details about the errors, such as the error message or the exact time of failure. An n8n automation workflow template by Matheus Pedrosa.

By 1Shot API

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Monetize Your Private LLM Models with x402 and Ollama Self-hosting custom LLMs is becoming more popular and easier with turn-key inferencing tools like Ollama. With Ollama you can host your own proprietary models for customers in a private cloud or on your own hardware. But monetizing custom-trained, propietary models is still a challenge, requiring integrations with payment processors like Stripe, which don't support micropayments for on-demand API consumption. With this free workflow you can quickly monetize your proprietary LLM models with the x402 payment scheme in n8n with 1Shot API. Setup Steps: Authenticate the 1Shot API node against your 1Shot API business account. Point the 1Shot API simulate and execute nodes at the x402-compatible payment token you'd like to receive as payment. Configure the Ollama n8n node in the workflow (with optional authentication) to forward to your Ollama API endpoint and let users query it through an n8n webhook endpoint while paying you directly in your preferred stablecoin (like USDC). Through x402, users and AI agents can pay per-inference, whith no overhead wasted on centralized payment processors. Walkthrough Tutorial Check out the YouTube tutorial for this workflow so see the full end-to-end process. An n8n automation workflow template by 1Shot API.

By Hybroht

Source Discovery - Automatically Search More Up-to-Date Information Sources 🎬 Overview Version : 1.0 This workflow utilizes various nodes to discover and analyze potential sources of information from platforms like Google, Reddit, GitHub, Bluesky, and others. It is designed to streamline the process of finding relevant sources based on specified search themes. ✨ Features Automated source discovery from multiple platforms. Filtering of existing and undesired sources. Error handling for API requests. User-friendly configuration options. 👤 Who is this for? This workflow is ideal for researchers, content marketers, journalists, and anyone looking to efficiently gather and analyze information from various online sources. 💡 What problem does this solve? This workflow addresses the challenge of manually searching for relevant information sources, saving time and effort while ensuring that users have access to the most pertinent content. Ideal use-cases include: Resource Compilation for Academic and Educational Purposes Journalism and Research Content Marketing Competitor Analysis 🔍 What this workflow does The workflow gathers data from selected platforms through search terms. It filters out known and undesired sources, analyzes the content, and provides insights into potential sources relevant to the user's needs. 🔄 Workflow Steps 1. Search Queries Fetch sources using SerpAPI search, DuckDuckGo, and Bluesky. Utilizes GitHub repositories to find relevant links. Leverages RSS feeds from subreddits to identify potential sources. 2. Filtering Step Removes existing and undesired sources from the results. 3. Source Selection Analyzes the content of the identified sources for relevance. 📌 Expected Input / Configuration The workflow is primarily configured via the Configure Workflow Args (Manual) node or the Global Variables custom node. Search themes: Keywords or phrases relevant to the desired content. Lists of known sources and undesired sources for filtering. 📦 Expected Output A curated list of potential sources relevant to the specified search themes, along with insights into their content. 📌 Example ⚙️ n8n Setup Used n8n version:** 1.105.3 n8n-nodes-serpapi:** 0.1.6 n8n-nodes-globals:** 1.1.0 n8n-nodes-bluesky-enhanced**: 1.6.0 n8n-nodes-duckduckgo-search**: 30.0.4 LLM Model:** mistral-small-latest (API) Platform:** Podman 4.3.1 on Linux Date:** 2025-08-06 ⚡ Requirements to Use / Setup Self-hosted or cloud n8n instance. Install the following custom nodes: SerpAPI, Bluesky, and DuckDuckGo Search. n8n-nodes-serpapi n8n-nodes-duckduckgo-search n8n-nodes-bluesky-enhanced Install the Global Variables Node for enhanced configuration: n8n-nodes-globals (or use Edit Field (Set) node instead) Provide valid credentials to nodes for your preferred LLM model, SerpAPI, and Bluesky. Credentials for GitHub recommended. ⚠️ Notes, Assumptions \& Warnings Ensure compliance with the terms of service of any platforms accessed or discovered in this workflow, particularly concerning data usage and attribution. Monitor API usage to avoid hitting rate limits. The workflow may encounter errors such as 403 responses; in such cases, it will continue by ignoring the affected substep. Duplicate removal is applied, but occasional overlaps might still appear depending on the sources. This workflow assumes familiarity with n8n, APIs, and search engines. Using AI agents (Mistral or substitute LLMs) requires access to their API services and keys. This is not a Curator of News. It is designed to find websites that are relevant and useful to your searches. If you are looking for a relevant news selector, please check this workflow. ℹ️ About Us This workflow was developed by the Hybroht team. Our goal is to create tools that harness the possibilities of technology and more. We aim to continuously improve and expand functionalities based on community feedback and evolving use cases. For questions, reach out via contact@hybroht.com. ⚖️ Warranty & Legal Notice This free workflow is provided "as-is" without any warranties of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. By using this workflow, you acknowledge that you do so at your own risk. We shall not be held responsible for any damages, losses, or liabilities arising from the use or inability to use this workflow, including but not limited to any direct, indirect, incidental, or consequential damages. It is your responsibility to ensure that your use of this workflow complies with all applicable laws and regulations. An n8n automation workflow template by Hybroht.

By Vladimir

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Automated Meeting Bot: Google Meet → AI Summary → Slack How it works Automatically joins Google Meet calls, transcribes conversations, and posts AI-generated summaries to Slack - completely hands-free meeting notes for busy teams. The workflow triggers when a Google Meet starts in your calendar, joins the meeting with a bot, waits for completion, then generates and posts a structured summary to your Slack channel. Set up steps Connect Google Calendar API for meeting detection Set up Vexa.ai account and obtain API key for meeting bot functionality Configure OpenAI API credentials for AI-powered summarization Create Slack bot token and add to desired channel Update calendar ID and Slack channel in workflow settings Test with a sample meeting to verify end-to-end functionality Keep detailed descriptions in sticky notes inside your workflow for easy configuration and troubleshooting. An n8n automation workflow template by Vladimir.

By Jorge Martínez

Lead Enrichment & Email Discovery from Google Sheets What this workflow does This template automates the enrichment of business leads from a Google Sheet by: Triggering when a row is activated Searching for company information with Serper.dev Generating and validating potential contact pages Scraping company pages with ScrapingBee Extracting emails and updating the sheet Marking rows as finished Prerequisites Google Sheet with columns: business type, city, state, activate Copy the ready-to-use template:** Sheet Template Google Sheets API credentials (from Google Cloud) Serper.dev API key (free tier available) ScrapingBee API key (free tier available) Inputs Google Sheet row:** Must include business type, city, state, activate Set Information Node:** country, country_code, language, result_count (can also be provided via columns in the sheet) Outputs Google Sheet update:** Company names, URLs, found email addresses (comma-separated if multiple), and status updates (Running, Missing information, Finished) Configuration Required Connect Google Sheets node with your Google Cloud credentials Add your Serper.dev API key to the HTTP Request node Add your ScrapingBee API key to the scraping node Adjust search and filtering options as needed How to customize the workflow Send country, country_code, and result_count from the sheet:** Add these as columns in your sheet and update the workflow to read their values dynamically, making your search fully configurable per row. Add more blacklist terms:** Update the code node with additional company names or keywords you want to exclude from the search results. Extract more contact details:** Modify the email extraction code to find other contact info (like phone numbers or social profiles) if needed. An n8n automation workflow template by Jorge Martínez.

By iamvaar

Nodes Used: Manual Execution Trigger HTTP Request (Get Zillow Properties) Code Node (Split Listings Array) IF Node (Filter by Budget) Google Sheets (Append or Update) Description : This workflow automates the extraction, refinement, and organization of live real estate data from a top property platform into a clean, always-updated spreadsheet. It intelligently filters incoming data using custom criteria and ensures your sheet remains accurate without duplicates. Ideal for realtors, investors, or property analysts who need a real-time snapshot of viable listings without lifting a finger. YOUTUBE VIDEO OF EXECUTION: https://youtu.be/zoBnYGu7fvU. An n8n automation workflow template by iamvaar.

By Guillaume Duvernay

Unlock a new level of sophistication for your AI agents with this template. While the native n8n Think Tool is great for giving an agent an internal monologue, it's limited to one instance. This workflow provides a clever solution using a sub-workflow to create multiple, custom thinking tools, each with its own specific purpose. This template provides the foundation for building agents that can plan, act, and then reflect on their actions before proceeding. Instead of just reacting, your agent can now follow a structured, multi-step reasoning process that you design, leading to more reliable and powerful automations. Who is this for? AI and automation developers:** Anyone looking to build complex, multi-tool agents that require robust logic and planning capabilities. LangChain enthusiasts:** Users familiar with advanced agent concepts like ReAct (Reason-Act) will find this a practical way to implement similar frameworks in n8n. Problem solvers:** If your current agent struggles with complex tasks, giving it distinct steps for planning and reflection can dramatically improve its performance. What problem does this solve? Bypasses the single "Think Tool" limit:** The core of this template is a technique that allows you to add as many distinct thinking steps to your agent as you need. Enables complex reasoning:** You can design a structured thought process for your agent, such as "Plan the entire process," "Execute Step 1," and "Reflect on the result," making it behave more intelligently. Improves agent reliability and debugging:** By forcing the agent to write down its thoughts at different stages, you can easily see its line of reasoning, making it less prone to errors and much easier to debug when things go wrong. Provides a blueprint for sophisticated AI:** This is not just a simple tool; it's a foundational framework for building state-of-the-art AI agents that can handle more nuanced and multi-step tasks. How it works The re-usable "Thinking Space": The magic of this template is a simple sub-workflow that does nothing but receive text. This workflow acts as a reusable "scratchpad." Creating custom thinking tools: In the main workflow, we use the Tool (Workflow) node to call this "scratchpad" sub-workflow multiple times. We give each of these tools a unique name (e.g., Initial thoughts, Additional thoughts). The power of descriptions: The key is the description you give each of these tool nodes. This description tells the agent when and how it should use that specific thinking step. For example, the Initial thoughts tool is described as the place to create a plan at the start of a task. Orchestration via system prompt: The main AI Agent's system prompt acts as the conductor, instructing the agent on the overall process and telling it about its new thinking abilities (e.g., "Always start by using the Initial thoughts tool to make a plan..."). A practical example: This template includes two thinking tools to demonstrate a "Plan and Reflect" cycle, but you can add many more to fit your needs. Setup Add your own "action" tools: This template provides the thinking framework. To make it useful, you need to give the agent something to do. Add your own tools to the AI Agent, such as a web search tool, a database lookup, or an API call. Customize the thinking tools: Edit the description of the existing Initial thoughts and Additional thoughts tools. Make them relevant to the new action tools you've added. For example, "Plan which of the web search or database tools to use." Update the agent's brain: Modify the system prompt in the main AI Agent node. Tell it about the new action tools you've added and how it should use your customized thinking tools to complete its tasks. Connect your AI model: Select the OpenAI Chat Model node and add your credentials. Taking it further Create more granular thinking steps:** Add more thinking tools for different stages of a process, like a "Hypothesize a solution" tool, a "Verify assumptions" tool, or a "Final answer check" tool. Customize the thought process:* You can change *how the agent thinks by editing the prompt inside the fromAI('Thoughts', ...) field within each tool. You could ask for thoughts in a specific format, like bullet points or a JSON object. Change the workflow trigger:** Switch the chat trigger for a Telegram trigger, email, Slack, whatever you need for your use case! Integrate with memory:** For even more power, combine this framework with a long-term memory solution, allowing the agent to reflect on its thoughts from past conversations. An n8n automation workflow template by Guillaume Duvernay.

By Rahi Uppal

WABA Message Journey Flow Documentation This document outlines the automated workflow for sending WhatsApp messages to contacts, triggered hourly and managed through disposition and message count logic. The workflow is designed to ensure contacts receive messages based on their status and the frequency of previous interactions. Trigger and Data Retrieval The journey begins with a time-based trigger and data retrieval from the Supabase contacts table. Trigger: A "Schedule Trigger3" node initiates the workflow every hour. This ensures that the system regularly checks for contacts requiring messages. Get Contacts: The "Get many rows1" node (Supabase) then retrieves all relevant contact data from the contacts_ampere table in Supabase. This brings in contact details such as name, phone, Disposition, Count, and last_message_sent. Disposition-Based Segregation After retrieving the contacts, the workflow segregates them based on their Disposition status. Disposition Switch: The "Disposition Switch" node acts as the primary routing mechanism. It evaluates the Disposition field of each contact and directs them to different branches of the workflow based on predefined categories. Case 0: new_lead: Contacts with the disposition new_lead are routed to the "Count Switch" for further processing. Cases 1-4: The workflow also includes branches for test_ride, Booking, walk_in, and Sale dispositions, though the detailed logic for these branches is not fully laid out in the provided JSON beyond the switch nodes ("Switch2", "Switch3", "Switch4", "Switch5"). The documentation focuses on the new_lead disposition's detailed flow, which can be replicated for others. Message Count Logic (for new_lead Disposition) For contacts identified as new_lead, the workflow uses a "Count Switch" to determine which message in the sequence should be sent. Count Switch: This node evaluates the Count field for each new_lead contact. This Count likely represents the number of messages already sent to the contact within this specific journey. Count = 0: Directs to "Loop Over Items1" (first message in sequence). Count = 1: Directs to "Loop Over Items2" (second message in sequence). Count = 2: Directs to "Loop Over Items3" (third message in sequence). Count = 3: Directs to "Loop Over Items4" (fourth message in sequence). Looping and Interval Check Each "Loop Over Items" node processes contacts in batches and incorporates an "If Interval" check (except for Loop Over Items1). Loop Over Items (e.g., "Loop Over Items1", "Loop Over Items2", "Loop Over Items3", "Loop Over Items4"): These nodes iterate through the contacts received from the "Count Switch" output. Interval Logic: "If Interval" (for Count = 1 from "Loop Over Items2"): Checks if the interval is greater than or equal to 4. This interval value is handled by a separate Supabase cron job, which updates it every minute based on Current time - last api hit time in hours. "If Interval1" (for Count = 2 from "Loop Over Items3"): Checks if the interval is exactly 24 hours. "If2" (for Count = 3 from "Loop Over Items4"): Checks if the interval is exactly 24 hours. Sending WhatsApp Messages If a contact passes the interval check (or immediately for Count = 0), a WhatsApp message is sent using the Gallabox API. HTTP Request Nodes (e.g., "new_lead_0", "new_lead_", "new_lead_3", "new_lead_2"): These nodes are responsible for sending the actual WhatsApp messages via the Gallabox API. They are configured with: Method: POST URL: https://server.gallabox.com/devapi/messages/whatsapp Authentication: apiKey and apiSecret are used in the headers. Body: Contains channelId, channelType (whatsapp), and recipient (including name and phone). WhatsApp Message Content: Includes type: "template" and templateName (e.g., testing_rahi, wu_2, testing_rahi_1). The bodyValues dynamically insert the contact's name and other details. Some messages also include buttonValues for quick replies (e.g., "Show me Brochure"). Logging and Updating Contact Status After a message is sent (or attempted), the workflow logs the interaction and updates the contact's record. Create Logs (e.g., "Create Logs", "Create Logs1", "Create Logs2", "Create Logs3"): These Supabase nodes record details of the message send attempt into the logs_nurture_ampere table. This includes: message_id (from the Gallabox API response body) phone and name of the contact disposition and mes_count (which is Count + 1 from the contacts table) last_sent (timestamp from Gallabox API response headers) status_code and status_message (from Gallabox API response or error). These nodes are configured to "continueRegularOutput" on error, meaning the workflow will attempt to proceed even if logging fails. Status Code Check (e.g., "If StatusCode", "If StatusCode 202", "If StatusCode 203", "If StatusCode 204"): Immediately after attempting to create a log, an "If" node checks if the status_code from the message send attempt is "202" (indicating acceptance by the messaging service). Update Contact Row (e.g., "Update a row1", "Update a row2", "Update a row3", "Update a row4"): If the status code is 202, these Supabase nodes update the contacts_ampere table for the specific contact. The Count for the contact is incremented by 1 (Count + 1). The last_message_sent field is updated with the date from the Gallabox API response headers. These nodes are also configured to "continueRegularOutput" on error. This structured flow ensures that contacts are nurtured through a sequence of WhatsApp messages, with each interaction logged and the contact's status updated for future reference and continuation of the journey. An n8n automation workflow template by Rahi Uppal.

By FabioInTech

📝 Automated Blog Post Publishing from Airtable to Hashnode This workflow streamlines your content publishing process by automatically creating draft blog posts on Hashnode from content stored in Airtable. Perfect for content creators, marketing teams, and developers who want to maintain a consistent publishing schedule while managing multiple Hashnode publications from a centralized database. 🎯 Who's it for Content creators** managing multiple blog publications Marketing teams** coordinating content across different Hashnode accounts Developers** looking to automate their technical blog publishing workflow Agencies** managing content for multiple clients on Hashnode ⚙️ How it works The workflow operates in a simple 7-step process: Retrieves unpublished posts from your Airtable database (filtered by "Not Published" status) Processes each post individually using a loop to handle multiple posts Fetches the publication ID from Hashnode using the provided domain Validates the publication exists before proceeding with post creation Creates draft posts on Hashnode with the title and markdown content Updates post status to "Published" in Airtable upon successful creation Handles errors by marking failed posts with "Error" status for easy troubleshooting 📋 Requirements Airtable Setup: Your Airtable table must include these columns: Title - The blog post title Content_markdown - Full blog post content in Markdown format Hashnode_Token - Your Hashnode API authentication token HashNode_Publication_Domain - Your publication's domain (e.g., "yourblog.hashnode.dev") Status - Publication status ("Not Published", "Published", or "Error") Hashnode Requirements: Valid Hashnode account with API access Publication domain configured API token with draft creation permissions 🔧 How to set up Configure Airtable credentials in the "Get Posts" and "Update Post" nodes Set your Airtable base and table IDs to match your setup Ensure your Airtable table contains all required columns listed above Add your content with status "Not Published" to trigger the workflow Test the workflow with a single post before processing multiple items 🎨 How to customize the workflow Modify the filter criteria** in the "Get Posts" node to target different post statuses Add content validation** before posting (word count, required fields, etc.) Include post scheduling** by adding date/time conditions Extend with notifications** using Slack, Discord, or email nodes Add SEO optimization** by including meta descriptions and tags Create published post tracking** by storing Hashnode draft IDs in Airtable 💡 Need Help? Join the Discord or ask in the Forum!. An n8n automation workflow template by FabioInTech.

By Cristian Baño Belchí

How it works: Accesses a target website, searches for new PDFs, and downloads them automatically. Extracts content from each PDF and sends it to an AI for summarization. Delivers the AI-generated summary directly to a Discord channel. Marks processed URLs in Google Sheets to avoid duplicates. Set up steps: Configure the website URL in the HTTP Request node. Connect to Google Cloud API (enable Drive & Sheets) and link your spreadsheet. Set up an OpenRouter API key and choose your preferred AI model. Create a Discord webhook for notifications. An n8n automation workflow template by Cristian Baño Belchí.

By Dominic Spatz

🔄 Purpose of the Workflow: The Update-N8N workflow is designed to automatically trigger a (Portainer) webhook to update an N8N container, but only if a new version of N8N is available. ⚙️ Detailed Workflow Steps: 🕒 Scheduled Trigger The workflow runs every 16 hours at minute 8 using a schedule trigger node. 🌐 Fetch Latest N8N Version It sends an HTTP GET request to https://registry.npmjs.org/n8n/latest to retrieve the latest published N8N version from the npm registry. 📈 Get Currently Running Local Version Another HTTP GET request is sent to https://127.0.0.1/metrics (likely the Prometheus metrics endpoint of the local N8N instance) to extract the currently installed N8N version. 🧠 Version Comparison The workflow compares the local version (parsed from metrics) with the latest available version. 📬 Trigger Portainer Webhook If the versions do not match (i.e., an update is available), a POST request is sent to a webhook URL, which might be a Portainer webhook that redeploys or updates the N8N container/stack. ✅ Key Benefits: No manual checks or updates needed. Triggers only when a new version is available. Integrates seamlessly with Portainer via webhook. Secure configuration, e.g., disallowing unauthorized TLS certs for external requests. An n8n automation workflow template by Dominic Spatz.

By Paul

🚀 AI OPS Agent for n8n — Stop Doing Busy Work. Start Leading. Your AI workforce is ready. Are you? 💰 What You Get: Your ROI in 30 Days Replace 10-15 hours/week of manual work with intelligent automation that actually understands your business. While your competitors copy-paste data between tools, you'll be making strategic decisions. 🧠 The Powerhouse Stack That Does Everything | Module | Core Job | Your Competitive Edge | |------------|-------------|--------------------------| | MAIN AGENT (Grok 4) | Orchestrator & brain | • Reads your message → builds execution plan• Delegates to specialized agents• Delivers results through your preferred channel | | Knowledge Agent | Company-wide research assistant | • Vector-searches your Supabase docs instantly• Runs live SQL queries for real-time numbers• Hunts & parses Drive files automatically• Pulls fresh web intelligence via Perplexity | | Google Sheets MCP Toolkit | Spreadsheet automation | Natural-language control over read/append/update/clear/create/delete operations on any tab or range | | Google Drive MCP Toolkit | File intelligence pipeline | • Auto-detects file types & extracts text from PDFs/CSVs• Transcribes audio/video content• Describes images with GPT-4o Mini | | Vector Store Loader | Long-term memory system | • Auto-chunks new files• Creates OpenAI embeddings• Stores in Supabase for instant semantic search | | Postgres Chat Memory | Conversation context | Never repeat yourself—every follow-up question builds on previous context | | Report Agent | Executive briefing machine | • Converts raw outputs → clean Markdown → HTML• Auto-emails/Slacks/Telegrams polished reports | | LinkedIn Scraper | Talent & market intelligence | Scrapes full LinkedIn profiles via Apify, delivers structured JSON for analysis | | Multi-Channel Triggers | Meet users where they work | Slack • Gmail • Telegram • WhatsApp • HTTP Webhooks | | LLM Layer | Right model, right job | Grok 4 (reasoning) • Claude Sonnet 4 (analysis) • GPT-4o Mini (speed) • Perplexity (live web) | ⚡ How It Works (The Magic in 5 Steps) Message arrives (Slack mention, email, webhook) MAIN AGENT analyzes → selects optimal tool chain Specialized toolkits execute (Sheets, Drive, SQL, Scraper...) Knowledge Agent synthesizes everything using the perfect LLM Report Agent packages & delivers results to your chosen channel 🎯 Real Commands That Save Hours Daily > "Update the Marketing-Spend sheet with last week's totals, then email me a chart." > > "Find the product-launch PDF from Drive, summarize key risks, post to Slack." > > "Scrape this LinkedIn URL, rank the candidate's skills, add them to our CRM sheet." > > "Create a new Sprint 11 tab, copy headers from Sprint 10, and ping the team." One command. Multiple systems. Zero manual work. Why Choose This Over Other Products: ✅ All Your Data, One Brain No more jumping between 12 different tools. Your AI agent connects everything. You can go further If you want to increase the Agent capabilities or make the more powerfull you can reach the dev. ✅ Vector Search Built-In Upload a 100-page document once. Search it forever with natural language. ✅ Executive-Ready Reports Your C-suite gets clean HTML briefs, not raw data dumps that waste their time. ✅ Deploy in Minutes Plug into your existing n8n setup, add credentials, watch routine ops handle themselves. An n8n automation workflow template by Paul.

By Hunyao

Note: This workflow assumes you already have your product’s Amazon reviews saved in a Google Sheet. If you still need those reviews, run my Amazon Reviews Scraper workflow first, then plug the resulting spreadsheet into this template. What it does Transforms any draft Google Doc into multiple high-converting sales pages. It blends Alex Hormozi’s value-stacking tactics with persona targeting based on Maslow’s Hierarchy of Needs, using your own customer reviews for proof and voice of customer (VOC). Perfect for • Growth and creative strategists • Freelance copywriters and agencies • Founders sharpening offers and funnels Apps used Google Sheets, Google Docs, LangChain OpenRouter LLM How it works Form Trigger collects Drive folder IDs, base copy URL and options. Workflow fetches the draft copy and product feature doc. It samples reviews, extracts VOC insights and maps them to Maslow needs. LLM drafts headlines and hooks following Hormozi’s \$100M Offers principles. Personas drive tone, objections and urgency in each copy variant. Loop writes one Google Doc per variant in your chosen folder. Customer analysis docs are saved to a second folder for reuse. Setup Share two Drive folders, copy the IDs (text after folders/). Paste each ID into Customer Analysis Folder ID and Advertorial Copy Folder ID. Provide File Name, Base copy (Google Docs URL) and Product Feature/USPs Doc. Optional: Reviews Sheet URL, Number of reviews to use, Target City. Set Number of Copies you need (1–20). Add Google Docs OAuth2 and Google Sheets OAuth2 credentials in n8n. If you have any questions in running the workflow, feel free to reach out to me at my youtube channel: https://www.youtube.com/@lifeofhunyao. An n8n automation workflow template by Hunyao.

By Rahul Joshi

Description: Streamline your social content creation workflow with this AI-powered n8n automation template. It monitors a specific Google Drive folder for new LinkedIn post images, automatically uploads them to Cloudinary, analyzes the content using GPT-4o via Azure OpenAI, and instantly emails a ready-to-publish HTML email with a full LinkedIn-style post. Perfect for solopreneurs, content creators, social media managers, and marketing teams who want to automate the creation of branded LinkedIn posts based on visual assets. What This Template Does (Step-by-Step): 📁 Google Drive Folder Monitoring Watches a specified Google Drive folder Triggers when a new image file is added ⬇️ Download the New Image File Securely downloads the uploaded file for processing ☁️ Upload to Cloudinary for Public Hosting Converts local file to public URL via Cloudinary Necessary for embedding in email content 🧠 Analyze Image with Azure OpenAI (GPT-4o) Sends the public image URL to a GPT-4o model Prompts the AI to generate: LinkedIn headline Overview Key features Ideal users Tech stack Hashtags Complete mobile-friendly HTML email body 📧 Deliver Email with HTML LinkedIn Post Sends the generated LinkedIn post via email Designed with inline CSS for Gmail & Outlook compatibility Best For: 🧑‍💼 LinkedIn creators & consultants 📣 Social media managers & freelancers 🛠️ SaaS founders and product marketers 📸 Anyone using Google Drive to manage social post assets Built With: Google Drive Trigger Cloudinary Upload API Azure OpenAI (GPT-4o-mini) HTML Email via SMTP Custom Prompt with LangChain LLM Chain Key Benefits: ✅ Fully hands-free LinkedIn post generation 🚀 Speed up social media content workflows 🎨 Visual-first input: image → post → email 💡 Uses your design work to inspire original posts 📬 Emails ready-to-post content directly to your inbox. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description: Build your own AI-powered Client FAQ system with Retrieval-Augmented Generation (RAG) — fully automated using n8n, Google Drive, and Azure OpenAI (GPT-4o-mini). This no-code automation enables your clients or team to ask questions through a webhook, and get precise answers sourced directly from a collection of PDF documents stored in Google Drive. Ideal for support teams, sales enablement, onboarding automation, and customer self-service — this RAG-powered bot ensures accurate, document-based answers with no hallucinations or AI guesses. What This Template Does (Step-by-Step): 🌐 Webhook Trigger for Incoming Questions Accepts POST requests with a client’s question Triggers the entire FAQ automation on request 🗂️ Search Google Drive Folder for Source Documents Connects to a specific Google Drive folder (e.g., “Case Studies”) Fetches all PDFs to be used as the context source 📥 Downloads and Processes Each File Downloads all matched files Extracts clean text from each PDF file 🔄 Iterates Over Each File for Text Extraction Loops through multiple files Extracts relevant content from each file individually 🧠 Prepares Clean Context + Question for RAG Combines the extracted PDF text into a single context block Injects the user’s question into the RAG-ready prompt 💬 Azure OpenAI (GPT-4o-mini) RAG Prompt Generates an accurate answer ONLY from the extracted documents If the answer isn’t found, returns a fallback response 📤 Sends the Final Response Back via Webhook Returns the AI-generated answer directly to the client via HTTP response Perfect For: 📞 Sales & client onboarding teams 📚 Knowledge base & internal SOP support 🧑‍💻 B2B SaaS customer success teams 🏢 Enterprises automating policy or document queries 💼 Agencies offering client-specific documentation portals Built With: Webhook Trigger (n8n) Google Drive API (search + download) PDF Text Extractor Loop / Split Batches Azure OpenAI GPT-4o-mini via LangChain LLM Context-safe RAG prompt logic Webhook Response for real-time delivery Key Benefits: ✅ Fast, context-aware answers from internal PDFs 🔒 No hallucinations — AI only responds using uploaded documents 📎 Works with any internal client folder in Google Drive 💬 Easily embed into any app, bot, or portal via Webhook 🧩 100% modular — extend with email, Slack, CRM, or ticketing tools. An n8n automation workflow template by Rahul Joshi.

By Robert Breen

This n8n workflow reads emails from your Outlook inbox, drafts AI-powered replies using OpenAI, and routes them through the gotoHuman node for human approval before replying automatically. ✅ Key Features Reads Outlook emails** from today only (excluding those from your own address). AI-generated replies** crafted using OpenAI based on the subject and body of the email. Community node integration**: Uses the gotoHuman node for human review and approval of replies before sending. Safe sending**: Only approved responses are automatically sent back via Outlook. Expandable**: Can be easily modified to: Send drafts instead of full replies Include additional email filters Trigger at intervals or via webhook 🧠 Nodes Used Microsoft Outlook – Fetch and reply to emails OpenAI – Generates smart reply text gotoHuman – Human-in-the-loop approval system Loop Over Items, IF, Code, and Set nodes for processing logic Manual Trigger – For testing 🔧 Setup Instructions 1. Connect APIs Outlook OAuth2**: Go to Azure Portal Register an app Add Mail.Read, Mail.Send scopes Set redirect URI: https://api.n8n.cloud/oauth2-credential/callback Paste credentials in n8n credential manager OpenAI API**: Create account at OpenAI Create an API Key Add it to n8n credentials gotoHuman API**: Go to https://gotoHuman.ai and sign in Create a review template (e.g., “Email Responses”) Copy the Template ID and API key into n8n credentials 🪜 Workflow Steps Overview 1. Trigger Use the Manual Trigger to test or schedule execution with a cron node. 2. Filter Emails from Today A Code node outputs today's date in the proper yyyy-mm-dd format. const today = new Date(); today.setHours(0, 0, 0, 0); return [{ json: { searchQuery: received:${today.toISOString().split('T')[0]} } }]; 3. Search and Filter Outlook Messages Uses the Outlook node with a search query like: received:2025-08-06 -from:rbreen@ynteractive.com (Update to your email) 4. Generate AI Response Text prompt to OpenAI: subject: {{ $json.subject }} body: {{ $json.body.content }} System prompt: > You are a personal assistant helping respond to emails. I am an AI automation expert specializing in helping small and medium-size businesses automate processes. Create a short response to the email. Sign the email as Robert Breen. 5. Review with gotoHuman Submit AI output for human approval using the gotoHuman node. The output schema should match the Review Template fields (e.g., "email", "OriginalEmail"). 6. IF Node Decision If status is approved, send reply If not, return to loop for revision or skip ✏️ Customization Ideas ✉️ Send only drafts by skipping the "reply" step and storing results. 🕒 Schedule the workflow with a Cron trigger for automation. 🔎 Add label filters or subject keywords for advanced targeting. 🔗 External Links gotoHuman Community Node OpenAI Microsoft Outlook API Setup 💬 Need More Help? If you'd like help customizing this or building similar automations, reach out: Robert Breen AI & Automation Consultant 🌐 https://ynteractive.com 📧 robert.j.breen@gmail.com 🔗 LinkedIn. An n8n automation workflow template by Robert Breen.

By Davide Boizza

This workflow automates the process of generating and scheduling social media posts using content from a WordPress blog. It leverages advanced AI (OpenAI & Anthropic Claude), Google Sheets, and the Postiz platform to create and publish platform-specific posts across LinkedIn, Facebook, Instagram, and Twitter (X). This system streamlines cross-platform social media publishing, ensuring consistent branding and AI-optimized content. Key Features Content Source: WordPress Automatically fetches the content of a WordPress post by its Post ID. Content Transformation via AI Uses Anthropic Claude and OpenAI to generate unique, optimized captions for each platform: LinkedIn: professional and insight-driven Instagram: creative with emojis and storytelling Facebook: community-oriented and friendly Twitter (X): concise, hashtag-optimized Visual Generation (Optional) Uses OpenAI's DALL·E (via OpenRouter) to generate custom images based on the AI-generated Instagram and Facebook/LinkedIn captions. Post Management with Google Sheets Uses a Google Sheet as the control panel: Simply input the WordPress Post ID Marks each post as “done” by updating corresponding columns (TWITTER, FACEBOOK, INSTAGRAM, LINKEDIN) Publishing via Postiz Uses the Postiz API to schedule or immediately publish posts to your connected social accounts. Handles image uploads and scheduling time for each platform. Benefits 💡 Intelligent automation: Saves time by removing manual copywriting and platform formatting. 🎯 Platform optimization: Ensures posts are tailored to each platform’s audience and algorithm. 🛠️ No-code friendly: Simple setup via Google Sheets + Postiz + WordPress. 🔁 Repeatable & Scalable: Ideal for agencies or content creators managing multiple posts per week. 🧪 +20 Social Media Platforms: Easy to start with social integrations. How It Works Input & Data Fetching: The workflow starts with a manual trigger (e.g., "Test workflow") or scheduled execution. It retrieves a WordPress post ID from a Google Sheets document, then fetches the full post content (title and body) via the WordPress API. AI-Powered Content Generation: The "Social Media Manager" node (powered by Claude Opus 4.1) analyzes the post and generates platform-optimized captions for: Twitter/X: Concise, hashtag-rich text (≤150 chars). Facebook/LinkedIn: Professional yet engaging copy with CTAs. Instagram: Visual-focused captions with emojis and hashtags. AI-generated images are created for Instagram (square) and Facebook/LinkedIn (landscape) using OpenAI’s image model. Publishing Automation: Captions and images are uploaded to Postiz, a social media scheduler. Postiz publishes the content to connected platforms (Twitter, Facebook, LinkedIn, Instagram) at the specified time. Google Sheets is updated with status markers (e.g., "x" in columns like TWITTER, FACEBOOK) to track published posts. Set Up Steps Prerequisites: Postiz Account: Sign up for Postiz (free trial available). API Keys: Configure Postiz API credentials in the "Postiz" and "Upload Image" nodes. Social Channels: Link your social accounts in Postiz’s dashboard and note their integrationId values (replace "XXX" in Postiz nodes). Google Sheets Setup: Clone the template Sheet and add WordPress post IDs to the "POST ID" column. Configure Nodes: WordPress: Add credentials for your WordPress site in the "Get Post" node. AI Models: Ensure API keys for Claude (Anthropic) and OpenAI (for images) are valid. Postiz Nodes: Replace placeholder integrationId values with your actual Postiz channel IDs. Test & Deploy: Trigger the workflow manually to verify captions, images, and Postiz scheduling. Activate the workflow for automation (e.g., run daily to publish new WordPress posts). Note: This workflow requires self-hosted n8n due to community nodes (Postiz, LangChain). Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By AI/ML API | D1m7asis

📲 AI Multi-Model Telegram Chatbot (n8n + AIMLAPI) This n8n workflow enables Telegram users to interact with multiple AI models dynamically using #model_id commands. It also supports a /models command to list all available models. Each user has a daily usage limit, tracked via Google Sheets. 🚀 Key Features Dynamic Model Selection:** Users choose models on-the-fly via #model_id (e.g., #openai/gpt-4o). /models Command:** Lists all available models grouped by provider. Daily Limit Per User:** Enforced using Google Sheets. Prompt Parsing:** Extracts model and message from user input. Logging:** Logs every request & result into Google Sheets for usage tracking. Seamless Telegram Delivery:** Responses are sent directly back to the chat. 🛠 Setup Guide 1. 📲 Create a Telegram Bot Go to @BotFather Use /newbot → Set name & username. Copy the generated API token. 2. 🔐 Add Telegram Credentials to n8n Go to n8n > Credentials > Telegram API. Create a new credential with the BotFather token. 3. 📗 Google Sheets Setup Create a Google Sheet named Sheet1. Add columns: user_id | date | query | result Share the sheet with your Service Account or OAuth Email (depending on auth method). 4. 🔌 Connect AIMLAPI Get your API key from AIMLAPI. In n8n > Credentials, add AI/ML API: API Key: your_key_here. 5. ⚙️ Customize Limits & Enhancements Adjust daily limits in the Set Daily Limit node. Optional: Add NSFW content filtering. Implement alias commands. Extend with /help, /usage, /history. Add inline button UX (advanced). 💡 How It Works ➡️ Command Examples: Start a chat with a specific model: #openai/gpt-4o Write a motivational quote. Request available models list: /models ➡️ Workflow Logic: Receives a Telegram message. Switch node checks if the message is /models or a prompt. For /models, it fetches and sends a grouped list of models. For prompts: Checks usage limits. Parses #model_id and prompt text. Dynamically routes the request to the chosen model. Sends the AI's response back to the user. Logs the query & result to Google Sheets. If daily limit exceeded → sends a limit exceeded message. 🧪 Testing & Debugging Tips Test via a separate Telegram chat. Use Console/Set nodes to debug payloads. Always test commands by messaging the bot (not via "Execute Node"). Validate cases: Missing #model_id. Invalid model_id. Limit exceeded handling. An n8n automation workflow template by AI/ML API | D1m7asis.

By Oneclick AI Squad

This workflow automates real-time student tracking using iOS Shortcuts and geolocation data, notifying both teachers and parents based on geofenced logic. 🎯 What This Workflow Does Receives student location updates via webhook (iOS Shortcuts) Detects if the student has arrived at school Logs arrival data to Google Sheets Sends email alerts** to teacher and/or parent based on location 🔄 Workflow Steps | Step | Description | | --------------------------- | -------------------------------------------------------- | | Location Update Webhook | Triggered via iOS Shortcut when student location updates | | Process Location Data | Extracts coordinates and metadata | | Student Arrived? | Checks if student entered school zone | | Log School Arrival | Adds arrival data to Google Sheet | | At School? | Double-checks geofence condition before notifying | | Notify Teacher | Sends email if student is confirmed at school | | Notify Parent | Sends email to parent (can vary based on geofence logic) | | Success Response | Returns a 200 response to the triggering device | 🧠 How the Logic Works The student’s phone runs a shortcut when near school. Sends coordinates to webhook. Workflow compares coordinates with predefined geofence (e.g., radius around school). If inside school zone: Log arrival Notify teacher and/or parent Else: Optionally notify parent only 📱 iOS Shortcut Sample (Trigger Setup) Automation Trigger**: Arrive at Location (e.g., School) Action**: Run Shortcut → Make Web Request (POST) POST URL: https://your-n8n-instance.com/webhook/location-update Body Example: { "student_id": "STU042", "student_name": "Anaya Joshi", "lat": 19.0760, "lng": 72.8777, "timestamp": "2025-08-06T08:05:00" } 📊 Google Sheets Logging | Student ID | Name | Date | Time | Status | | ---------- | ----------- | ---------- | ----- | ------- | | STU042 | Anaya Joshi | 2025-08-06 | 08:05 | Arrived | ⚙️ Setup Requirements n8n Instance** with webhook support Google Sheet** with appropriate columns iOS Shortcut** setup on student device Teacher and Parent Email Addresses** configured in workflow. An n8n automation workflow template by Oneclick AI Squad.

By Oneclick AI Squad

A lightweight no-code workflow that captures student check-in data via a mobile app or webhook, stores it in a Google Sheet, and instantly notifies the class teacher via email. 🎯 What This Does Students check in using a mobile app or QR code Their data is formatted and saved to a Google Sheet A notification email is sent to the class teacher in real time 🔧 Workflow Steps | Step | Description | | ------------------------------ | ----------------------------------------------------------- | | Student Check-in (Webhook) | Triggered via POST request from mobile app or QR scanner | | Format Data | Cleans and prepares incoming JSON into structured format | | Append or Update Row | Saves student check-in data into Google Sheets | | Email Teacher | Sends formatted check-in email to the class teacher | | Success Response | Returns a confirmation response to the mobile app or system | 📱 Example Check-in Input (Webhook Body) { "student_name": "Aarav Mehta", "student_id": "STU025", "class_name": "Grade 6B" } 📊 Google Sheets Format | Student Name | Student ID | Class | Date | Time | | ------------ | ---------- | -------- | ---------- | ----- | | Aarav Mehta | STU025 | Grade 6B | 2025-08-06 | 08:35 | Date and time are added dynamically in the workflow. ⚙️ Setup Requirements n8n Instance** – Deployed with public webhook support Google Sheets** – Sheet with columns as shown above Email SMTP Settings** – For sending teacher notification ✅ Quick Setup Instructions Import the workflow into your n8n instance Replace the webhook URL in your mobile app Set your Google Sheet ID and range Enter the teacher’s email in the “Email Teacher” node Test with mock data Deploy and use live!. An n8n automation workflow template by Oneclick AI Squad.

By Oneclick AI Squad

📘 Student Absence Alerts & Attendance Tracking Automation Automatically alerts parents about student absences and tracks 30-day attendance patterns to identify risks and trends. 🔧 Main Components Daily Attendance Check – 10:30 AM** Triggers the workflow every day at 10:30 AM. Read Today’s Attendance** Retrieves current-day attendance records from the source Excel or database. Read Student Contacts** Reads contact details (email, phone) of students for alert delivery. Process Absent Students** Identifies students who are absent and unexcused for the day. Prepare Absence Email** Generates customized email content for absent students. Send Absence Email** Sends an absence alert email to the student’s parent/guardian. Prepare Absence SMS** Formats WhatsApp-friendly message for alerts. Send Absence WhatsApp** Sends the WhatsApp message using API (e.g., Facebook Graph). Generate Attendance Report** Prepares a daily attendance summary with absence level classifications. Save Attendance Report** Appends the generated report to a historical attendance sheet. ⚠️ Alert Logic Based on the past 30-day absence pattern, the system classifies students into: | Level | Absences in 30 Days | Status | | --------- | ------------------- | -------------- | | 🔴 High | 5+ | Critical Alert | | 🟡 Medium | 3–4 | Warning | | 🟢 Low | 1–2 | Low Risk | 📊 Tracking Features 🔢 Attendance Rate Calculation – Tracks each student's attendance percentage 🔍 Pattern Analysis – Detects recurring absenteeism trends 🚨 Risk Identification – Flags high-risk students for early intervention 📈 Historical Reporting – Maintains daily logs for future reference ✅ Essential Prerequisites Excel sheet or database with daily attendance logs Excel sheet or database with student contact details SMTP credentials for sending emails WhatsApp API integration (e.g., Facebook Graph or Twilio) Storage access for saving attendance reports 📁 Required Excel File Structures Attendance Sheet (daily_attendance.xlsx) | Student ID | Date | Status | | ---------- | ---------- | ------ | | ST101 | 2025-08-06 | Absent | Contacts Sheet (student_contacts.xlsx) | Student ID | Name | Email | Phone | | ---------- | ---------- | --------------------------------------------- | ------------- | | ST101 | Aryan Shah | aryan@example.com | +919123456789 | 🧾 Expected Input Format Example { "studentId": "ST101", "name": "Aryan Shah", "email": "aryan@example.com", "phone": "+919123456789", "status": "Absent", "date": "2025-08-06" } 🚀 Key Features ⏰ Scheduled Daily Execution – Automated tracking at 10:30 AM ✉️ Multi-Channel Notifications – Email + WhatsApp alerts to parents 📊 Absence Pattern Monitoring – 30-day trend analysis 🧠 Risk-Based Alerts – Smart classification into alert levels 🗂️ Daily Reports – Easy to audit attendance summary logs ⚙️ Quick Setup Guide Import Workflow JSON into n8n. Configure schedule trigger at 10:30 AM. Set Excel file paths in "Read Today’s Attendance" and "Read Student Contacts". Customize absence thresholds in the “Process Absent Students” node. Add SMTP details for the “Send Absence Email” node. Integrate WhatsApp API in the “Send Absence WhatsApp” node. Test with mock data and review reports. Activate the workflow. 🔧 Parameters to Configure | Parameter | Description | | ---------------------- | -------------------------------------- | | attendance_file_path | Path to today's attendance records | | contacts_file_path | Path to student contacts sheet | | smtp_user | Email username for SMTP server | | smtp_password | Password for SMTP server | | whatsapp_api_url | Endpoint for sending WhatsApp messages | | alert_thresholds | Absence count thresholds for alerts |. An n8n automation workflow template by Oneclick AI Squad.

By Sk developer

🚀 Download Instagram Videos to Google Drive with Auto-Email Delivery Effortlessly convert Instagram videos to MP4 and automatically store them on Google Drive with a shareable download link sent to the user via email. This n8n workflow uses the Instagram Video Downloader API to automate the process of downloading Instagram videos, uploading them to Google Drive, and sending the download link directly to users. With this workflow, you can automate Instagram video downloads without manual effort. 📝 Node-by-Node Explanation n8n Form Trigger Captures the Instagram video URL and the user's email address from a web form. This initiates the workflow process. API Request (Instagram Video Downloader) Sends the Instagram video URL to the Instagram Video Downloader API for processing and fetching the MP4 video data. Check API Response (If Node) Validates the API response to ensure no errors were returned. If the response is valid, the workflow continues; otherwise, it halts the process. Download Instagram Video (HTTP Request) Downloads the MP4 video from the API response to proceed with the next steps. Upload to Google Drive Saves the downloaded MP4 video file to Google Drive for secure storage. Set Permissions (Google Drive) Adjusts the file’s permissions to make it publicly accessible, allowing anyone with the link to view or download the MP4. Send Email with Download Link Sends an automated email to the user with a link to download their converted MP4 file, completing the process. ✅ Use Cases Marketing Campaigns:** Save Instagram videos for use in marketing and promotional campaigns. Social Media Teams:** Automate the process of downloading Instagram content for team collaboration. Client Deliverables:** Automatically deliver Instagram MP4 links to clients without manual work. 🚀 Benefits Fast & Reliable:* Integration with the *Instagram Video Downloader API** guarantees quick video downloads. Fully Automated:** The entire process is automated from start to finish, eliminating manual steps. Cloud Storage:** Securely store MP4 files on Google Drive with easy sharing options. Instant Delivery:** Users receive their MP4 download link immediately via email. No Manual Effort:** Automates the download and sharing process without any need for manual interaction. 🔑 Resolved: The process of downloading Instagram videos and sharing them is now fully automated using the Instagram Video Downloader API, Google Drive storage, and instant email delivery. An n8n automation workflow template by Sk developer.

By Avkash Kakdiya

How it works This workflow automates the job curation process by retrieving pending job search inputs from a spreadsheet, querying the JSearch API for relevant job listings, and writing the curated results back to another sheet. It is designed to streamline job discovery and reduce manual data entry. Step-by-step 1. Trigger & Input The workflow starts on a defined schedule (e.g., once per day). It reads a row from the Job Scraper sheet where the status is marked as "Pending". The selected row includes fields like Position and Location, which are used to build the search query. 2. Job Search & Processing Sends a search request to the JSearch API using the Position and Location from the spreadsheet. Parses the API response and extracts individual job listings. Filters out empty, irrelevant, or invalid entries to ensure clean and relevant job data. 3. Output & Status Update Writes valid job listings to the Job Listing output sheet with fields such as job title, company name, location, and more. Updates the original row in the source sheet to mark it as Scraped, ensuring it will not be processed again in future runs. Benefits Reduces manual effort in job research and listing. Ensures only valid, structured data is stored and used. Prevents duplicate processing with automatic status updates. Simple to expand by adding more job sources or filters. An n8n automation workflow template by Avkash Kakdiya.

By Ahmed Saadawi

Turn WhatsApp Into a 24/7 AI Sales Assistant — n8n + DeepSeek + Sheets + Gmail ⚠️ Self-Hosted n8n Only Description Turn your WhatsApp channel into a smart sales assistant! This workflow listens for inbound customer messages, looks up product data in Google Sheets, uses a DeepSeek Chat Model to answer in Saudi dialect, collects purchase details, and notifies your service rep only when the customer is ready to buy. 🔧 How to Install Community Nodes Go to Settings → Community Nodes Click Install Node, then add: n8n-nodes-evolution-api Restart n8n if prompted. 🔄 What This Workflow Does Webhook Listener Captures inbound WhatsApp messages (MESSAGES_UPSERT via Evolution API). Filters Ignores outbound (fromMe) and group (@g.us) messages. Data Extraction Pulls the customer’s message and phone number. AI Response Uses the DeepSeek Chat Model node to answer from your Google Sheets product list, greeting with “هلا وغلا” and speaking in Saudi dialect. Purchase Flow Prompts for name, phone, and delivery/pickup date. Notify Sales Sends an email via Gmail only when the customer requests to purchase. Context Memory (Optional) Stores conversation history in Postgres for coherent multi-turn chats. 📸 Visual Preview 🧩 Workflow 🛠️ Setup Instructions Evolution API Webhook In Evolution API dashboard → Events → Webhook Enable only MESSAGES\_UPSERT Set Webhook URL to: https://your-n8n-domain/webhook/whatsAppListen Google Sheets Create a spreadsheet (“You Conmanay Name Items”) with your product data [Item name, Item Model, Item Description, Item Components, Item Price, Item Availability, ...] Connect your Google Sheets credentials in n8n DeepSeek Chat Model Configure your DeepSeek API credentials in the DeepSeek Chat Model node Ensure the system prompt matches your company’s tone and data columns Gmail Notifications Add Gmail OAuth2 credentials to the Send a message in Gmail node Customize subject and email template if needed Postgres Memory (Optional) Connect a Postgres instance in the Postgres Chat Memory node for session context 👥 Who Is This For? E-commerce teams** automating first-touch customer replies Sales reps** needing AI-driven chat support on WhatsApp Businesses** using WhatsApp as a primary customer channel 🔐 Credentials Required Evolution API (webhook only) Google Sheets API DeepSeek API Gmail OAuth2 Postgres (optional, for memory) 🏷 Tags whatsapp bot, deepseek, google sheets, evolution api, gmail, postgres memory, ecommerce, sales automation, n8n template, no-code, ai, agent, ai agent. An n8n automation workflow template by Ahmed Saadawi.

By Oneclick AI Squad

📚 Automated School Fee Reminder Workflow with Payment Link Automatically sends fee reminders (via email and WhatsApp) to parents with secure payment links, 3 days before the due date. 🔧 Main Components Daily Fee Check – 8 AM** Scheduled trigger that starts the workflow daily at 8 AM. Read Pending Fees** Fetches student fee records from an Excel sheet (using getAll method). Process Fee Reminders** Filters records to find pending fees due within the next 3 days. Prepare Email Reminder** Generates personalized email messages with payment links. Wait for Email Preparation** Adds delay/wait condition for email logic readiness. Send Email Reminder** Sends the fee reminder email with a secure payment link to the parent. Prepare WhatsApp Reminder** Generates WhatsApp-friendly messages with fee and payment details. Wait for WhatsApp Preparation** Waits for WhatsApp message logic to complete. Send WhatsApp Message** Sends the message to the parent’s WhatsApp number using a message API. Update Reminder Status** Updates the Excel file to mark reminders as sent to avoid duplicates. 🧩 Channels Used 📧 Email – with personalized payment link 💬 WhatsApp – formatted reminder message 🔐 Payment Integration Secure payment links are auto-generated per student to enable direct and safe online fee payments. ✅ Essential Prerequisites Excel sheet with fee records (student_fee_data.xlsx) SMTP credentials for sending email WhatsApp API or provider integration (like Twilio or Gupshup) Access to a payment gateway or service for link generation File storage access to update reminder status in Excel 📁 Required Excel File Structure (student_fee_data.xlsx) | Student ID | Name | Email | Phone | Fee Due Date | Amount | Reminder Sent | | ---------- | ---- | ----- | ----- | ------------ | ------ | ------------- | 🧾 Expected Input Format Example { "studentId": "ST123", "name": "Ria Mehta", "email": "ria.mehta@example.com", "phone": "+919123456789", "dueDate": "2025-08-10", "amount": "₹5000", "reminderSent": "No" } 🚀 Key Features ⏰ Scheduled Daily Execution – Fully automated at 8 AM 🧮 Due-Date Filtering – Only targets fees due in the next 3 days 💬 Multi-Channel Notifications – Sends reminders via both Email and WhatsApp 🔗 Secure Payment Links – Auto-generated for each student 🔄 Reminder Tracking – Prevents duplicate reminders by updating status ⚙️ Quick Setup Guide Import Workflow JSON into your n8n instance. Configure schedule in the “Daily Fee Check” node (default: 8 AM). Set Excel file path in the “Read Pending Fees” node. Update your fee processing logic in the “Process Fee Reminders” node. Add email credentials in the “Send Email Reminder” node. Integrate WhatsApp provider API in the “Send message” node. Define how you generate secure payment links. Test with sample data and activate workflow. 🛠️ Parameters to Configure | Parameter | Description | | ------------------ | ------------------------------------------ | | excel_file_path | Path to the fee tracking Excel file | | smtp_host | SMTP server for sending email reminders | | smtp_user | Email username | | smtp_password | Email password | | whatsapp_api_key | WhatsApp API key for sending messages | | payment_api_url | URL for generating payment links | | admin_email | (Optional) Admin email for error reporting |. An n8n automation workflow template by Oneclick AI Squad.

By AppStoneLab Technologies LLP

🤖 AI Support Bot for WooCommerce with Gemini & GPT (Telegram & Gmail) Managing customer support across multiple platforms like email and chat can be a huge time sink. Answering the same questions about order status repeatedly takes your focus away from growing your business. This workflow solves that problem by deploying a 24/7 conversational AI agent to act as your first line of support for your WooCommerce store. This AI-powered bot can handle customer inquiries from both Telegram and Gmail, understand conversational follow-ups, and use a tool to fetch live order data directly from your WooCommerce store. It's designed to be reliable, with a primary/fallback AI model setup, and robust enough to prevent the common pitfalls of email automation like infinite reply loops. How It Works ⚙️ The workflow operates in a clear, logical sequence: 📢 Multi-Channel Ingestion: The workflow starts when it receives a message from one of two sources: Telegram: An instant webhook trigger fires for every new message. Gmail: A polling trigger checks your inbox every minute for new, unread emails. 💎 Data Normalization: All incoming requests are merged and processed by a Set node. This crucial step transforms the platform-specific data into a universal format that the rest of the workflow can understand (e.g., platform, sender_id, query_text). 🧠 AI Processing: The standardized query is sent to a LangChain Agent. This agent is the "brain" of the operation. It uses Conversational Memory to understand the context of the conversation (like when a user provides an order ID in a follow-up message). 🛠️ Tool Usage: Based on its prompt, the AI Agent determines if it has enough information to use its one available tool: Get an order in WooCommerce. If a valid Order ID is present, it calls the tool to fetch live order details. 📮 Response & Routing: The agent formulates a natural language response. A Switch node then inspects the platform field and routes the response to the correct channel. ✅ Cleanup: For the Gmail path, two final actions occur in parallel: the reply is sent, and the original incoming email is marked as 'Read'. This is a critical step to prevent the workflow from re-triggering on the same email in an infinite loop. Nodes Used 🔗 This workflow uses a combination of standard nodes and AI nodes to achieve its goal: Telegram Trigger: To receive messages from Telegram in real-time. Gmail Trigger: To poll for new unread emails. Merge: To combine inputs from multiple triggers. Set: To normalize data into a consistent format. LangChain Agent: The core AI "brain" that orchestrates the logic, memory, and tools. Google Gemini & OpenAI: Used as the primary and fallback language models for the agent. WooCommerce Tool: The tool the AI agent uses to fetch order data. Switch: To route the final reply to the correct platform. Telegram: To send the final response to Telegram. Gmail: To reply to emails and mark them as read. Prerequisites 🔑 To use this workflow, you will need: An active n8n instance (self-hosted or cloud). A Telegram Bot account and its API token. A Gmail account with OAuth2 credentials configured in n8n. A WooCommerce store with API credentials (Consumer Key and Secret). An OpenAI API key. A Google AI (Gemini) API key. Usage 🚀 Follow these steps to set up the workflow: Download the Workflow: Import the workflow JSON file into your n8n instance. Configure Credentials: Telegram: Select your Telegram API credentials in the Fetch user query and Send Telegram Response nodes. Gmail: Select your Gmail OAuth2 credentials in the Fetch support mail, Send Response via Mail, and Mark received mail as read nodes. WooCommerce: Select your WooCommerce API credentials in the Get an order in WooCommerce node. AI Models: Select your OpenAI and Google AI credentials in the Fallback Model and Primary Model nodes, respectively. Activate Telegram Webhook: Open the Fetch user query (Telegram Trigger) node. Copy the Webhook URL. Register this URL with your Telegram bot using the /setWebhook command in the BotFather chat. Customize AI Prompt (Optional): Open the WooCommerce Customer support Agent1 node. You can edit the prompt in the Text field to change the AI's personality, rules, or language. Activate the Workflow: Save the workflow and toggle the "Active" switch ON. Your multi-channel AI support agent is now live\! Send a message to your Telegram bot or a new, unread email to your connected Gmail account to test it out. Resources 📚 n8n Documentation n8n Community Forum LangChain in n8n. An n8n automation workflow template by AppStoneLab Technologies LLP.

By MANISH KUMAR

Automated YouTube Shorts Creator with yt-dlp & FFmpeg Description How It Works • Downloads videos/music from YouTube using yt-dlp • Merges assets with dynamic text overlays • Automatically uploads to YouTube as Shorts (9:16 format) • Tracks everything in Google Sheets Set Up Steps (~10 minutes) Install yt-dlp and FFmpeg in your n8n environment Connect Google Sheets (for video/music pools) Set up YouTube OAuth credentials Configure text overlay font (NotoSerif included) Key Features Dual Pipeline System Video Downloader (MP4) + Music Downloader (MP3 with thumbnails) Random pairing for endless combinations Professional Text Overlays Dynamic line wrapping for perfect 9:16 formatting Customizable fonts/colors YouTube API Integration Automatic upload with metadata (titles/descriptions) Privacy/license controls Google Sheets Tracking Logs download paths, YouTube URLs, timestamps Prevents duplicate processing. An n8n automation workflow template by MANISH KUMAR.

By Oneclick AI Squad

This automated n8n workflow distributes school notices to stakeholders (students, parents, and staff) via WhatsApp, email, and other channels. It streamlines the process of scheduling, validating, and sending notices while updating distribution status. System Architecture Notice Distribution Pipeline**: Daily Notice Check - 9 AM: Triggers the workflow daily at 9 AM via Cron. Read Notices getAll worksheet: Retrieves notice data from a spreadsheet. Validation Flow**: Validate Notice Data: Validates and formats notice data. Distribution Flow**: Process Notice Distribution: Prepares notices for multiple channels. Prepare Email Content: Generates personalized email content. Send Email Notice: Delivers emails to recipients. Prepare WhatsApp Content: Formats notices for WhatsApp. Send WhatsApp Notice: Sends notices via WhatsApp Business API. Status Update**: Update Notice Status: Updates the distribution status in the spreadsheet. Implementation Guide Import Workflow**: Import the JSON file into n8n. Configure Cron Node**: Set to trigger daily at 9 AM (e.g., 0 9 * * *). Set Up Credentials**: Configure SMTP and WhatsApp Business API credentials. Prepare Spreadsheet**: Create a Google Sheet with notice_id, recipient_name, email, phone, notice_text, distribution_date, and status columns. Test Workflow**: Run manually to verify notice distribution and status updates. Adjust Thresholds**: Modify validation rules or content formatting as needed. Technical Dependencies Cron Service**: For scheduling the workflow. Google Sheets API**: For reading and updating notice data. SMTP Service**: For email notifications (e.g., Gmail, Outlook). WhatsApp Business API**: For sending WhatsApp messages. n8n**: For workflow automation and integration. Database & Sheet Structure Notice Tracking Sheet** (e.g., Notices): Columns: notice_id, recipient_name, email, phone, notice_text, distribution_date, status Example: | notice_id | recipient_name | email | phone | notice_text | distribution_date | status | |-----------|----------------|-------------------|-------------|------------------------------|-------------------|-----------| | 001 | John Doe | john@example.com | +1234567890 | School closed tomorrow | 2025-08-07 | Pending | | 002 | Jane Smith | jane@example.com | +0987654321 | Parent-teacher meeting | 2025-08-08 | Sent | Customization Possibilities Adjust Cron Schedule**: Change to hourly or weekly as needed. Add Channels**: Integrate additional notification channels (e.g., Slack, SMS). Customize Content**: Modify email and WhatsApp message templates. Enhance Validation**: Add rules for data validation (e.g., email format). Dashboard Integration**: Connect to a dashboard tool for real-time status tracking. Notes The workflow assumes a Google Sheet as the data source. Replace spreadsheet_id and range with your actual values. Ensure WhatsApp Business API is properly set up with a verified phone number and token. Test the workflow with a small dataset to confirm delivery and status updates. An n8n automation workflow template by Oneclick AI Squad.

By Rahul Joshi

Description: Streamline your cloud storage with this powerful Google Drive File Renamer automation built with n8n. The workflow watches a specific Google Drive folder and automatically renames new files using a standardized format based on their creation date and time—ideal for organizing images, backups, and uploads with consistent timestamp-based names. Whether you're managing daily uploads, sorting Instagram-ready content, or organizing client submissions, this timestamp-based file naming system ensures consistent and searchable file structures—without manual intervention. What This Template Does (Step-by-Step) 🔔 Google Drive Trigger – "Watch Folder" Setup Monitors a specific folder (e.g., “Instagram”) Detects new file creations every minute Captures file metadata like ID, createdTime, and extension 🧠 Set Formatted Name Extracts file creation time (e.g., 2025-07-22T14:45:10Z) Converts it into a structured name like IMG_20250722_1445.jpg Keeps original file extension (JPG, PNG, PDF, etc.) ✏️ Rename File (Google Drive) Renames the original file using Google Drive API Applies the new timestamped name Keeps file content, permissions, and location unchanged Required Integrations: Google Drive API (OAuth2 credentials) Best For: 📸 Content creators organizing uploads from mobile 🏷️ Branding teams enforcing uniform naming 🗄️ Admins managing scanned documents or backups 📂 Automated archives for media, reports, or daily snapshots Key Benefits: ✅ Timestamped naming ensures chronological file tracking ✅ Reduces human error and messy file names ✅ Works in real-time (polls every minute) ✅ No-code: Deploy with drag-and-drop setup in n8n ✅ Fully customizable name patterns (e.g., change IMG_ prefix). An n8n automation workflow template by Rahul Joshi.

By Anna Bui

🎯 LinkedIn ICP Lead Qualification Automation Automatically identify and qualify ideal customer prospects from LinkedIn post reactions using AI-powered profile analysis and intelligent data enrichment. Perfect for sales teams and marketing professionals who want to convert LinkedIn engagement into qualified leads without manual research. This workflow transforms post reactions into actionable prospect data with AI-driven ICP classification. Good to know LinkedIn Safety**: Only use cookie-free Apify actors to avoid account detection and suspension risks Daily Processing Limits**: Scrape maximum 1 page of reactions per day (50-100 profiles) to stay under LinkedIn's radar Apify actors cost approximately $0.01-0.05 per profile scraped - budget accordingly for daily processing Includes intelligent rate limiting to prevent API restrictions and maintain LinkedIn account safety AI classification requires clear definition of your Ideal Customer Profile criteria Processing too many profiles or running too frequently will trigger LinkedIn's anti-scraping measures Always monitor your LinkedIn account health and Apify usage patterns for any warning signs How it works Scrapes LinkedIn post reactions using Apify's specialized actor to identify engaged users Extracts and cleans profile data including names, job titles, and LinkedIn URLs Checks against existing Airtable records to prevent duplicate processing and save costs Creates new prospect records with basic information for tracking purposes Enriches profiles with comprehensive LinkedIn data including company details and experience Aggregates and formats profile data for AI analysis and classification Uses AI to analyze prospects against your ICP criteria with detailed reasoning Updates records with ICP classification results and extracted email addresses Implements smart batching and delays to respect API rate limits throughout the process How to use IMPORTANT**: Select cookie-free Apify actors only to avoid LinkedIn account suspension Set up Apify API credentials in both HTTP Request nodes for safe LinkedIn scraping Configure Airtable OAuth2 authentication and select your prospect tracking base Replace the LinkedIn post URL with your target post in the initial scraper node Daily Usage**: Process only 1 page of reactions per day (typically 50-100 profiles) maximum Customize the AI classification prompt with your specific ICP criteria and job titles Test with a small batch first to verify setup and monitor both API costs and LinkedIn account health Schedule workflow to run daily rather than processing large batches to maintain account safety Requirements Apify account with API access and sufficient credits for profile scraping Airtable account with OAuth2 authentication configured OpenAI or compatible AI model credentials for prospect classification LinkedIn post URL with reactions to analyze (minimum 10+ reactions recommended) Clear definition of your Ideal Customer Profile criteria for accurate AI classification Customising this workflow Safety First**: Always verify Apify actors are cookie-free before configuring to protect your LinkedIn account Modify ICP classification criteria in the AI prompt to match your specific target customer profile Set up daily scheduling (not hourly/frequent) to respect LinkedIn's usage patterns and avoid detection Adjust rate limiting delays based on your comfort level with LinkedIn scraping frequency Add additional data fields to Airtable schema for storing custom prospect information Integrate with CRM systems like HubSpot or Salesforce for automatic lead import Set up Slack notifications for new qualified prospects or daily summary reports Create email marketing sequences in tools like Mailchimp for nurturing qualified leads Add lead scoring based on company size, industry, or engagement level for prioritization Consider rotating between different LinkedIn posts to diversify your prospect sources while maintaining daily limits. An n8n automation workflow template by Anna Bui.

By Browser Use

A sample demo showing how to integrate Browser Use Cloud API with N8N workflows. This template demonstrates AI-powered web research automation by collecting competitor intelligence and delivering formatted results to Slack. How It Works Form trigger accepts competitor name input Browser Use Cloud API performs automated web research Webhook processes completion status and retrieves structured data JavaScript code formats results into readable Slack message HTTP request sends final report to Slack Integration Pattern This workflow showcases key cloud API integration techniques: REST API authentication with bearer tokens Webhook-based status monitoring for long-running tasks JSON data parsing and transformation Conditional logic for processing different response states Setup Required Browser Use API key (signup at cloud.browser-use.com) Slack webhook URL Perfect demo for learning browser-use cloud API integrations and building automated research workflows. An n8n automation workflow template by Browser Use.

By Jason Krol

Notion Weekly Journal AI Summary This workflow will run on a weekly schedule and retrieve your Notion Daily Journal pages for the past week and aggregate them into a ChatGPT generated concise summary. It will save that weekly summary back to your Notion as a new Note in addition to posting to a personal Discord channel. Additionally it will also retrieve all of the Tasks you've completed in the past week and provide a quick total with a congratulatory message to a Discord channel as well. Requirements/Setup: You need Notion setup w/ a Notes database If you want the Discord messages, setup a Discord webhook for your channel as well, or simply delete the Discord nodes. One of the properties for the Notes db should be Type with a value of Journal The contents of your daily Journal pages can be whatever you want I've found what works best for me is the format of "What was a highlight of the day?", "What was a low point of the day?", and "What decisions did I delegate, delay, or dodge?" You should also create an additional Type for your Weekly summary page that gets created - in this case I used simply Weekly Automate this to run weekly on your day of choice. I tend to only journal on weekdays so I've set mine up to run every Friday retrieving the past week's Journal entries. Options: You don't have to use Discord, feel free to swap out with Slack or remove altogether. You also don't need to use the Tasks summary bottom half, simply remove that if you don't want it or need it. You can easily reuse this workflow to aggregate your Weekly Summary notes (that this workflow auto generates/saves) to generate a Quarterly or even Yearly summary!. An n8n automation workflow template by Jason Krol.

By Mauricio Perera

📝 Description This workflow allows you to extract all links (URLs) contained in a PDF file by converting it to HTML via PDF.co and then extracting the URLs present in the resulting HTML. Unlike the traditional Read PDF node, which only returns visible link text, this flow provides the full active URLs, making further processing and analysis easier. 📌 Use Cases Extract all hyperlinks from PDF documents. Automate URL verification and monitoring within documents. Extract links from reports, contracts, catalogs, newsletters, or manuals. Prepare URLs for validation, classification, or storage. 🔗 Workflow Overview User uploads a PDF file via a web form. The PDF is uploaded to PDF.co. The PDF is converted to HTML (preserving links). The converted HTML is downloaded. URLs are extracted from the HTML using a custom code node. ⚙️ Node Breakdown 1. Load PDF (formTrigger) Uploads a .pdf file. Single file upload. 2. Upload (PDF.co API) Uploads the PDF file to PDF.co using binary data. 3. PDF to HTML (PDF.co API) Converts the uploaded PDF to HTML using its URL. 4. Get HTML (HTTP Request) Downloads the converted HTML from PDF.co. 5. Code1 (Function / Code) Parses the HTML content to extract all URLs (http, https, www). Uses a regex to identify URLs within the HTML text. Outputs an array of objects containing the extracted URLs. 📎 Requirements Active PDF.co account with API key. Set up PDF.co credentials in n8n (PDF.co account). Enable webhook to expose the upload form. 🛠️ Suggested Next Steps Add nodes to validate extracted URLs (e.g., HTTP requests to check status). Store URLs in a database, spreadsheet, or send via email. Extend the flow to filter URLs by domain, type, or pattern. 📤 Importing the Template Import this workflow into n8n via Import workflow and paste the provided JSON. If you want help adding extra steps or optimizing the URL extraction, just ask! If you want, I can also prepare this as a Canva visual template for you. Would you like that?. An n8n automation workflow template by Mauricio Perera.

By Naveen Choudhary

This workflow automatically enriches company domain lists with comprehensive business information scraped from ZoomInfo, organizing the data in Google Sheets for sales teams and researchers. Who's it for Sales teams** building prospect databases with accurate company information Marketing professionals** researching target companies for outreach campaigns Business development teams** qualifying leads with revenue and employee data Researchers** collecting structured company data for market analysis Lead generation specialists** enriching domain lists with contact details How it works The workflow processes unprocessed domains from a Google Sheet, searches for their ZoomInfo profiles using Serper API, scrapes the company pages through Oxylabs proxy service, and extracts structured business data. Each domain is marked as processed to prevent duplicates, and the workflow includes proper rate limiting to respect API limits. What it does Loads unprocessed domains from your Google Sheets database Searches ZoomInfo using targeted queries via Serper API for each domain Validates search results and extracts relevant ZoomInfo profile URLs Scrapes company pages using Oxylabs to bypass anti-scraping protection Extracts structured data including company details, address, revenue, and employee count Updates Google Sheets with enriched company information Tracks processing status to prevent reprocessing the same domains Requirements Serper API account** with search credits (Get API key) Oxylabs subscription** for web scraping proxy service (Sign up here) Google Sheets API access** with OAuth2 authentication Google Sheets template** - Make a copy of this template sheet with pre-configured columns How to set up Make a copy of the Google Sheets template - Click here to copy the template to your Google Drive Configure API credentials in the respective HTTP Request nodes: Add Serper API key in the search node Set up Oxylabs username/password in the scraping node Set up Google Sheets authentication using OAuth2 Update the Google Sheets document ID in all Google Sheets nodes to point to your copied template Add your domain list to the sheet with 'processed' column empty or false Run the workflow using the manual trigger How to customize the workflow Search query modification**: Update the search query in the Serper node for different geographic focus (currently set for Czech Republic) Data extraction fields**: Modify the Google Sheets column mapping to include/exclude specific company data points Rate limiting**: Adjust wait times between requests to match your API rate limits Batch processing**: Configure the split batch size for processing domains in smaller groups Error handling**: Customize the continue-on-error settings based on your data quality requirements Scheduling**: Replace Manual Trigger with Schedule Trigger for automated daily/weekly runs Output data includes Complete company name and official address Phone numbers and contact information Revenue figures and employee headcount Industry classifications and business categories LinkedIn company profile URLs Geographic location details (city, state, country, postal code) Processing status tracking for workflow management Note: This workflow includes comprehensive error handling to ensure domains are always marked as processed, preventing infinite loops while maintaining data integrity. Rate limiting is built-in to respect API quotas and avoid service interruptions. An n8n automation workflow template by Naveen Choudhary.

By Stephan Koning

VEXA: AI-Powered Meeting Intelligence I'll be honest, I built this because I was getting lazy in meetings and missing key details. I started with a simple VEXA integration for transcripts, then added AI to pull out summaries and tasks. But that just solved part of the problem. The real breakthrough came when we integrated Mem0, creating a persistent memory of every conversation. Now, you can stop taking notes and actually focus on the person you're talking to, knowing a system is tracking everything that matters. This is the playbook for how we built it. How It Works This isn't just one workflow; it's a two-part system designed to manage the entire meeting lifecycle from start to finish. Bot Management: It starts when you flick a switch in your CRM (Baserow). A command deploys or removes an AI bot from Google Meet. No fluff—it's there when you need it, gone when you don't. The workflow uses a quick "digital sticky note" in Redis to remember who the meeting is with and instantly updates the status in your Baserow table. AI Analysis & Memory: Once the meeting ends, VEXA sends the transcript over. Using the client ID (thank god for redis) , we feed the conversation to an AI model (OpenAI). It doesn't just summarize; it extracts actionable next steps and potential risks. All this structured data is then logged into a memory layer (Mem0), creating a permanent, searchable record of every client conversation. Setup Steps: Your Action Plan This is designed for rapid deployment. Here's what you do: Register Webhook: Run the manual trigger in the workflow once. This sends your n8n webhook URL to VEXA, telling it where to dump transcripts after a call. Connect Your CRM: Copy the vexa-start webhook URL from n8n. Paste it into your Baserow automation so it triggers when you set the "Send Bot" field to Start_Bot. Integrate Your Tools: Plug your VEXA, Mem0, Redis, and OpenAI API credentials into n8n. Use the Baserow Template: I've created a free Baserow template to act as your control panel. Grab it here: https://baserow.io/public/grid/t5kYjovKEHjNix2-6Rijk99y4SDeyQY4rmQISciC14w. It has all the fields you need to command the bot. Requirements An active n8n instance or cloud account. Accounts for VEXA.ai, Mem0.ai, Baserow, and OpenAI. A Redis database . Your Baserow table must have these fields: Meeting Link, Bot Name, Send Bot, and Status. Next Steps: Getting More ROI This workflow is the foundation. The real value comes from what you build on top of it. Automate Follow-ups:** Use the AI-identified next steps to automatically trigger follow-up emails or create tasks in your project management tool. Create a Unified Client Memory:** Connect your email and other communication platforms. Use Mem0 to parse and store every engagement, building a complete, holistic view of every client relationship. Build a Headless CRM:** Combine these workflows to build a fully AI-powered system that handles everything from lead capture to client management without any manual data entry. Copy the workflow and stop taking notes. An n8n automation workflow template by Stephan Koning.

By Wyeth

INST: The n8n Workflow Installer This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute. That's right, now you can package up dozens of workflows and send your client(s) a single workflow to run, that will create them all and auto-assign all the credentials. This workflow installs 3 files when you run it, demonstrating the functionality. Just make your own mods to the system, repackage it, and you are ready to go! Requirements An n8n instance with API access enabled and an access key Optional: GitHub and OpenAI access keys What This Workflow Does Installs 3 additional workflows, demonstrating the functionality One of the workflows is a packager, that you configure for your own needs Two example workflows demonstrate functionality, and can be deleted Step-by-Step Setup Run the Workflow This will get the example and tool workflows on your instance. Package Your Content Configure the packager, then run it to produce a base64-compressed version of your files. Customize the Installer Make your own copy of the installer, and set the base64 payload. Deploy the Installer Export your installer script. Now, anyone you send it to will get all your packaged workflows when they execute it. How to Use This Workflow This workflow is meant to be reused and adapted. You can: Integrate it into a deployment pipeline Turn it into a subworkflow for dynamic installs Extend it to include triggers, permission settings, or test runs If you frequently deploy or share n8n assets, this installer gives you a repeatable way to do it with confidence. An n8n automation workflow template by Wyeth.

By Jorge Martínez

Automate tweet engagement on X (formerly Twitter) Description Automate professional engagement on X (formerly Twitter) by searching for, filtering, liking, and replying to tweets that match your key topics. This workflow enables you to engage consistently and efficiently with relevant conversations, using your defined professional role and the power of GPT for filtering and replies. Save time and maintain high-quality interactions, while staying focused on your business or personal brand interests. How it Works Rotating Topic Selection The workflow selects one search term from your list on each run, using a rotating index based on the date. Search Tweets & Extract Essentials Searches X (formerly Twitter) for tweets matching the chosen topic, then extracts only the tweet id and text for further processing. GPT‑Based Filtering with Role Context Filters tweets based on your role and strict criteria, removing non-English tweets, memes, spam, Grok-generated content, political posts, internships, and more. Engagement Loop For every filtered tweet, the workflow likes the post, generates a professional, concise reply with GPT (matching language and context), and posts the reply. Wait nodes ensure compliance with Twitter’s API rate limits (can be adjusted for paid API tiers). Requirements X (Twitter) API credentials (for searching, liking, and replying to tweets) OpenAI API key (for GPT-based steps) Setup Steps Obtain your X (Twitter) API credentials. Obtain your OpenAI API key. Configure the schedule in the trigger node to your desired frequency (e.g., every 3 days or daily). Set your list of topics and professional role in the variables node. How to Customize the Workflow (Optional) Adjust prompts** in the GPT nodes to fine-tune filtering and reply style. Upgrade your Twitter API plan** to increase request limits and search for more tweets per run. Change tweet processing logic:** For high-volume engagement (e.g., analyzing 100+ tweets per run), consider switching to a per-tweet loop for advanced filtering and response handling. This workflow enables scalable, professional, and targeted engagement on X (formerly Twitter), fully customizable to your audience and objectives. An n8n automation workflow template by Jorge Martínez.