Scrape every URL on the web without getting blocked by Anti-Bot technologies with Scrappey
Purpose of the workflow Most scraping workflows get blocked by anti-bot technologies. To avoid this, you can use Scrappey to scrape every website you want. How it works: We use Test Data and make a API Call to the Scrappey service. We get the scraped website data back as a result. Setup Steps: Replace YOURAPIKEY in the "Scrappey API Call" node with your Scrappey API Key (Register For Free) Replace the test data with your production data. You can plug in any type of data connector at this point of your workflow.
By BelaOne-click YouTube shorts generator with Leonardo AI, GPT and ElevenLabs
🎬 What it does This workflow creates an engaging YouTube Short with a single click — from script to voiceover, to visuals and background music. It combines several AI tools to automate content creation and final video assembly. --- ⚙️ How it works Accepts an input prompt or topic Generates script using GPT Converts script to voiceover using ElevenLabs Generates b-roll style images via Leonardo.Ai Matches background music Assembles a vertical 1080×1920 MP4 video using JSON render config Optionally uploads to YouTube or saves to Cloudinary --- 🧰 Setup steps Add your credentials: Leonardo API (image generation) ElevenLabs (voiceover) Cloudinary (upload destination) Any GPT-based text generator Drop your audio/music file in the right node Replace API expressions with your own credentials > 🟨 Full step-by-step instructions are in sticky notes inside the workflow.
By Huzaifa TahirGmail MCP server – your all‑in‑one AI email toolkit
Gmail MCP Server Expose Gmail’s full API as a single SSE “tool server” endpoint for your AI agents. What it does Spins up an MCP Trigger that streams Server‑Sent Events to LangChain/N8N AI Agent nodes. Maps 20+ common Gmail operations (search, send, reply, draft, label & thread management, mark read/unread, delete, etc.) to ai_tool connections, so agents can invoke them with a simple JSON payload. Why you’ll love it Agent‑ready: Plug the SSE URL into any N8N Agent or any other AI tool that uses MCP and start reasoning over email immediately. Extensible: Add more GmailTool operations or swap credentials without touching your agent logic. How to use Import the workflow (n8n ≥ v1.88). Set up a gmailOAuth2 credential and select it on the GmailTool nodes. Open the Gmail MCP Server node, copy the SSE URL, and paste it into your AI agent’s “Tool Server” field.
By Brian MoneyAI: Ask questions about any data source (using the n8n workflow retriever)
This template aims to perform Q&A on data retrieved from another n8n workflow. Since that workflow can be used to retrieve any data from any service, this template can be used to ask questions about any data. It uses a manual trigger, various AI nodes, and an OpenAI Chat Model to extract and provide relevant information based on a specific query. Note that to use this template, you need to be on n8n version 1.19.4 or later.
By n8n TeamTransfer data from Postgres to Excel
Read data from Postgres Converting it to XLS Save it to disk
By Jan OberhauserBinance SM price-24hrStats-OrderBook-Kline tool
A powerful sub-agent that collects real-time market structure data from Binance for any trading pair — including price, volume, order book depth, and candlestick snapshots across multiple timeframes (15m, 1h, 4h, 1d). --- 🎥 Watch Tutorial: [](https://youtu.be/HWHD-eXP0IE) 🎯 Purpose This workflow powers the Quant AI system with: ✅ Real-time price feed (/ticker/price) ✅ 24-hour stats (OHLC, % change, volume via /ticker/24hr) ✅ Live order book depth (/depth) ✅ Latest candlestick data (/klines) for all major intervals All outputs are parsed and formatted using GPT and returned to the parent agent (e.g., Financial Analyst Tool) as a Telegram-optimized summary. --- ⚙️ Workflow Architecture | Node | Role | | ------------------------------------ | ------------------------------------------------------------ | | 🔗 Execute Workflow Trigger | Accepts input from parent workflow | | 🧠 Simple Memory | Stores session + symbol info | | 🤖 Binance SM Market Agent | Parses prompt, routes tool calls | | 💡 OpenAI Chat Model (gpt-4o-mini) | Converts raw data into a clean, readable format for Telegram | | 🌐 getCurrentPrice | Gets latest price | | 🌐 get24hrStats | Gets OHLC/volume over past 24 hours | | 🌐 getOrderBook | Gets top 100 bids and asks | | 🌐 getKlines | Gets latest 15m, 1h, 4h, and 1d candles | --- 📥 Input Requirements This workflow is not called directly by the user. Instead, it is triggered by another workflow, such as: json { "message": "BTCUSDT", "sessionId": "539847013" } --- 📤 Telegram Output Example 📊 BTCUSDT Market Overview 💰 Price: $63,220 📈 24h Change: +2.3% | Volume: 45,210 BTC 📉 Order Book • Top Bid: $63,190 • Top Ask: $63,230 🕰️ Latest Candles • 15m: O: $63,000 | C: $63,220 | Vol: 320 BTC • 1h : O: $62,700 | C: $63,300 | Vol: 980 BTC • 4h : O: $61,800 | C: $63,500 | Vol: 2,410 BTC • 1d : O: $59,200 | C: $63,220 | Vol: 7,850 BTC --- ✅ Use Cases | Scenario | Output Provided | | ---------------------------------- | ------------------------------------------------------------ | | “Show current BTC price and trend” | Price, 24h stats, candles, and order book in one message | | “Candles for SOL” | 15m, 1h, 4h, 1d candlesticks for SOLUSDT | | Triggered by Quant AI system | Clean Telegram-ready summary with all structure tools merged | --- 🧩 Toolchain Breakdown | Tool Name | Endpoint | Purpose | | ----------------- | ---------------------- | ------------------------------ | | getCurrentPrice | /api/v3/ticker/price | Latest trade price | | get24hrStats | /api/v3/ticker/24hr | 24h OHLC, % change, volume | | getOrderBook | /api/v3/depth | Top 100 bids and asks | | getKlines | /api/v3/klines | 1-candle snapshot across 4 TFs | --- 🚀 Installation Steps Import the JSON into your n8n instance Connect your OpenAI credentials for the Chat Model node No Binance API key needed — public endpoints Trigger this tool only via: Binance SM Financial Analyst Tool Binance Spot Market Quant AI Agent --- 🔐 Licensing & Attribution © 2025 Treasurium Capital Limited Company Architecture, prompts, and trade structure are IP-protected. No unauthorized rebranding permitted. 🔗 For support: Don Jayamaha – LinkedIn
By Don Jayamaha JrSet alert on the website changes
I used this to check for a page that had Out Of Stock not found when an item came back in stock. Set the URL for the HTTP Request node and your Webhook URL and Messages for the discord nodes.
By darkesthour111Log meal nutrients from Telegram to Google Sheets using an AI agent
Who is this for? This workflow is ideal for individuals focused on nutrition tracking, meal planning, or diet optimization—whether you’re a health-conscious individual, fitness coach, or developer working on a healthtech app. It also fits well for anyone who wants to capture their meal data via voice or text, without manually entering everything into a spreadsheet. What problem is this workflow solving? Manually logging meals and breaking down their nutritional content is time-consuming and often skipped. This workflow automates that process using Telegram for input, OpenAI for natural language understanding, and Google Sheets for structured tracking. It enables users to record meals by typing or sending voice messages, which are transcribed, analyzed for nutrients, and automatically stored for tracking and review. What this workflow does This n8n automation lets users send either a text or voice message to a Telegram bot describing their meal. The workflow then: Receives the Telegram message Checks if it’s a voice message • If yes: Downloads the audio file and transcribes it using OpenAI • If no: Uses the text input directly Sends the meal description to OpenAI to extract a structured list of ingredients and nutritional details Parses and stores the results in Google Sheets Responds via Telegram with a personalized confirmation message A testing interface also allows you to simulate prompts and view structured outputs for development or debugging. Setup Create a Telegram bot via BotFather and note the API token. Create an empty Google Sheet and store the sheet ID in the environment. Set up your OpenAI credentials in the n8n credential manager. Customize the “List of Ingredients and Nutrients” node with your prompt if needed. (Optional) Use the “Testing” section to simulate messages and refine outputs before going live. How to customize this workflow to your needs • Enhance prompts in the OpenAI node to improve the structure and accuracy of responses. • Add new fields in the Google Sheet and corresponding logic in the parser if you want more detail. • Adjust the Telegram response to provide motivational feedback, dietary tips, or summaries. • Upgrade to the “Pro” version mentioned in the contact section for USDA database integration and complete nutrient breakdowns. This is a lightweight, AI-powered meal logging automation that transforms voice or text into actionable nutrition data—perfect for making healthy eating easier and more data-driven. See my other workflows here
By PollupAICentralized n8n error management system with automated email alerts via Gmail
Advanced n8n Error Handling: Automated Email Alerts & Global Error Workflow Configuration In any automated environment, n8n workflows, while powerful, can sometimes encounter unexpected issues or fail during execution. Without a dedicated error handling strategy, these failures might go unnoticed, leading to incomplete processes, data inconsistencies, or critical operational disruptions. Manually monitoring every workflow execution or sifting through logs for error details is inefficient and can significantly delay crucial fixes. This is where a centralized, automated error management system becomes essential to maintain reliability and quickly address any problems. The "Advanced n8n Error Handling: Automated Email Alerts & Global Error Workflow Configuration" template provides a robust solution to proactively manage and respond to errors within your n8n instance. For more powerful n8n templates, visit our website or contact us at AI Automation Pro. We help your business build custom AI workflow automation and apps. Highlight features Automated Email Notifications: Sends detailed HTML emails via Gmail for both execution and trigger failures, ensuring you're promptly informed. Centralized Error Management: Acts as a single, dedicated workflow to catch and process errors from multiple other n8n workflows. Proactive Global Error Handler Configuration: A scheduled task automatically scans and updates other active n8n workflows to use this workflow as their default error handler, ensuring consistent error management. Comprehensive Error Reporting: Notification emails are rich with information, including error messages, stack traces, the last executed node, direct links to failed executions, and detailed trigger failure context. Dynamic Email Content: The subject line and body of the notification email are dynamically adjusted based on whether the failure was an execution error or a trigger failure. Highly Customizable: Offers flexibility to modify email content (HTML), change the notification channel (e.g., Slack, other email providers), and adjust the logic for updating other workflows' error handlers. Scheduled Operation: The global configuration part runs on a user-definable schedule (e.g., daily, hourly) for proactive and automated error handling setup across your n8n instance. Who is this for? This workflow is designed for n8n users and administrators who want to: Establish a resilient and centralized error handling mechanism across their n8n instance. Receive immediate and detailed email notifications for any workflow failures. Automate the process of assigning a default error handling workflow to all their active n8n workflows. Save time on manually configuring error handlers for each individual workflow and ensure comprehensive error coverage. What problem is this workflow solving? / use case In an n8n environment with multiple workflows, errors can occur without immediate visibility. This can lead to: Unnoticed failures, potentially causing data loss or incomplete automated processes. Time-consuming diagnosis of issues due to a lack of readily available, detailed error information. Inefficiency and oversight from manually setting an error workflow for every new or existing workflow. This template tackles these issues by providing a proactive error management system. It not only alerts you to failures with comprehensive details but also ensures that your other workflows are automatically configured to use this centralized handler. What this workflow does This workflow operates in two distinct yet complementary parts: 1\. Scheduled Global Error Handler Configuration: Trigger: Initiates based on a configurable schedule (e.g., daily, hourly). Identify Self: Retrieves its own workflow ID to use as the designated error handler. Scan Workflows: Fetches a list of all other workflows within your n8n instance. Conditional Update Logic: For each active workflow found, it checks if: An error workflow (errorWorkflow setting) is not currently set, OR The currently set errorWorkflow is different from this central error handling workflow. The workflow is active. Apply Default Handler: If the above conditions are met, it automatically updates the target workflow's settings. This sets the current workflow as its default error handler, ensuring that any future errors in those workflows are routed here. The callerPolicy setting is also removed during this update. 2\. Error Notification via Email: Trigger: Activates whenever an error occurs in any n8n workflow that has this workflow designated as its errorWorkflow. Gather Error Context: Collects vital information about the failure, such as: The base URL of your n8n instance. Specific details of the workflow that failed (name, ID). The nature of the error: whether it's an "execution error" (occurring mid-workflow) or a "trigger failure" (occurring at the start). Format Detailed Error Message: Constructs a comprehensive HTML email tailored to the error type: For Execution Errors: The email includes a direct link to the failed execution's page, the timestamp of the error, the name of the last node that successfully executed, the error message, and the full error stack trace. For Trigger Failures: The email includes the timestamp, operational mode, error message, error name and description, relevant context data, details about the cause (message, name, code, status), and the stack trace. Send Email Notification: Dispatches the formatted HTML email using Gmail to a predefined recipient. The email subject line dynamically indicates the name of the failing workflow and the type of error, providing a quick overview. Setup Import Workflow: Import the JSON file into your n8n instance. Configure Credentials: n8n API Access: Locate the nodes: "N8n Get Error Handler", "N8n Get All Workflows", and "N8n Update Workflow". For each, select or create new n8n API credentials. These credentials must have permissions to read all workflows (workflows.read) and update workflows (workflows.update). Gmail Access: Locate the "Gmail Send Notification" node. Select or create new Gmail OAuth2 credentials to authorize n8n to send emails on your behalf. Set Email Recipient and Sender Details: Navigate to the "Settings" node, which is connected directly after the "Error Trigger" node. Modify the value for the Email Receiver variable to the email address where error notifications should be sent. Optionally, update the Email Sender Name variable. Configure Schedule (Optional): Select the "Schedule Trigger" node. Adjust the "Trigger Interval" (e.g., Every Day, Every Hour) according to how frequently you want the workflow to scan and update the error handler settings for other workflows in your n8n instance. Activate Workflow: Ensure this workflow is toggled to "Active". Once active, its scheduled component will begin operating, and it will be ready to process and notify on errors from other linked workflows. Manual Configuration (Optional): While this workflow automates the assignment, you can also manually set this workflow as the errorWorkflow in the settings of any critical existing workflows for immediate protection. How to customize this workflow to your needs Email Content & Formatting: Modify the HTML content within the "HTML For Execution Error" and "HTML For Trigger Error" nodes to alter the appearance, structure, or information included in the notification emails. Alternative Notification Channels: Replace the "Gmail Send Notification" node with a different email service node (e.g., Microsoft Outlook, SendGrid) or integrate other notification platforms like Slack, Microsoft Teams, or Discord. Remember to adjust the input data mappings for the new node. Refine Global Update Logic: Adjust the conditions within the "If No Default Error Handler Set" node if you need more granular control over which workflows are automatically updated (e.g., filter by workflow tags, names, or explicitly exclude certain workflows). Enrich Error Data: Insert additional nodes after the "Error Trigger" but before the "Settings" node if you need to fetch more context about the error or the workflow that failed (e.g., look up related information from a database or API). Advanced Notification Routing: Implement more complex logic prior to sending notifications. For example, you could use a Switch node to route error alerts to different email addresses or channels based on the name of the failing workflow or the severity of the error. Handling of callerPolicy: The "Set Data" node is configured to remove the callerPolicy setting from workflows it updates. If your workflows rely on this setting, you may need to modify or remove this part of the "Set Data" node's code. Adjust Scheduled Task: Change the frequency or timing of the "Schedule Trigger" to better suit your operational needs for the global error handler update.
By Daniel Ng🎓 Optimize Speed-Critical Workflows Using Parallel Processing (Fan-Out/Fan-In)
How it works This template is a hands-on tutorial for one of the most advanced and powerful patterns in n8n: asynchronous parallel processing, also known as the Fan-Out/Fan-In model. When should you use this? Use this pattern when speed is your top priority and you have multiple independent, long-running tasks. Instead of running them one after another (which is slow), this workflow runs them all at the same time and waits for them all to finish. We use a Construction Project analogy to explain the architecture: The Main Workflow (Top): This is the Project Manager. It defines the project, assigns all the tasks to specialist teams, and then pauses, waiting for a final report. The Sub-Workflow (Bottom): This represents the Specialist Teams. It's a single, reusable workflow that can perform any task it's assigned. Static Data (The Brains): A hidden Project Dashboard is used to track the status of every task in real-time. The process follows three key phases: Fan-Out: The Project Manager starts multiple sub-workflows at once without waiting for them to finish. Asynchronous Execution: Each Specialist Team works on its task independently and in parallel. When a team finishes, it updates its status on the Project Dashboard. Fan-In: The Project Manager, which has been paused by a Wait node, is only resumed when the Project Dashboard confirms that all tasks are complete. It then receives the aggregated results from all the parallel tasks. Set up steps Setup time: < 1 minute This workflow is a self-contained tutorial. The only setup required is to configure the AI model. Configure Credentials: Go to the The AI Specialist node in the sub-workflow (bottom flow). Select your desired AI credential (Gemini in that case). Execute the Workflow: Click the "Execute Workflow" button on the Start Project node. Explore and Learn: Follow the execution path to see how the main workflow fans out, and how the sub-workflow is called multiple times. Click on each node and read the detailed sticky notes to understand its specific role in this advanced pattern.
By Lucas PeyrinPersonalized stock portfolio analysis and recommendations with Grok-4 and Perplexity
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 📊 Grok-4 with Perplexity Daily Portolio Advisor. This workflow acts as your personal AI stock analyst—powered by Grok-4, Perplexity, and Google Sheets—to give you daily, tailored market insights based on your actual investment portfolio. Every morning, the workflow: Fetches your current stock holdings from a connected Google Sheet Uses Perplexity to search and summarize the latest stock market news relevant to your portfolio Leverages Grok-4 AI to analyze how those news events impact your stocks Provides buy/sell/hold recommendations and AI-powered investment insights Emails you a clean, easy-to-read summary—perfect for busy investors To watch the step-by-step Tutorial build of this workflow, check out: https://youtu.be/OXzsh-Ba-8Y Google Sheet Template: https://docs.google.com/spreadsheets/d/1074dZk-vhwz6LML5zoiwHdxg89Z8u_mgl7wwzqf3A98/edit?usp=sharing 🧠 What’s Inside: AI Agent: Grok-4 Stock Analyst (via xAI Grok-4) Tool Integrations: 📄 Google Sheets (Portfolio input) 🔍 Perplexity (News search) ✍️ GPT Summary Agent (Readable output) 📧 Gmail (Automated delivery) Schedule: Runs daily at 10:00 AM by default (customizable) 💡 Use Cases: Retail investors seeking personalized news summaries Portfolio managers automating market analysis Fintech startups prototyping intelligent investment advisors Anyone wanting actionable stock updates without reading 10+ articles
By Automate With MarcCreate LinkedIn posts with AI agents using MCP server
Complete MCP server exposing all LinkedIn Tool operations to AI agents. Zero configuration needed - all 1 operations pre-built. ⚡ Quick Setup Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator.. All 100% free? Join the community Import this workflow into your n8n instance Activate the workflow to start your MCP server Copy the webhook URL from the MCP trigger node Connect AI agents using the MCP URL 🔧 How it Works • MCP Trigger: Serves as your server endpoint for AI agent requests • Tool Nodes: Pre-configured for every LinkedIn Tool operation • AI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Uses official n8n LinkedIn Tool tool with full error handling 📋 Available Operations (1 total) Every possible LinkedIn Tool operation is included: 🔧 Post (1 operations) • Create a post 🤖 AI Integration Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options Response Format: Native LinkedIn Tool API responses with full data structure Error Handling: Built-in n8n error management and retry logic 💡 Usage Examples Connect this MCP server to any AI agent or workflow: • Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints ✨ Benefits • Complete Coverage: Every LinkedIn Tool operation available • Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n error handling and logging • Extensible: Easily modify or add custom logic > 🆓 Free for community use! Ready to deploy in under 2 minutes.
By David Ashby