Browse 13,012 Workflows

By Hans Wilhelm Radam

Description: This workflow automates personalized email outreach to a list of hospitals. It uses a chat-based interface to accept a region and a list of hospital names, looks up their specific contact details from a structured Google Sheet, and sends a tailored email via Gmail. Who’s it for This template is perfect for healthcare startups, medical device sales representatives, or IT consultants who need to conduct targeted outreach to hospital administrators. It's designed for anyone looking to automate a personalized, region-specific email campaign without manual data entry. How it works Trigger: You provide input via a chat message. The first line is the region (e.g., LUZON), and each subsequent line is a hospital name. Parsing: A Code node splits your message into a structured list of items for processing. Batching: The workflow processes each hospital one by one for reliable execution. Data Lookup: Based on the region, the workflow queries the corresponding sheet in a Google Sheets document to find the hospital's specific contact details. Email Delivery: A personalized email is sent to the hospital's email address using Gmail, pulling data from the spreadsheet to customize the message. How to set up Credentials: Set up n8n credentials for Google Sheets and Gmail (using OAuth2 recommended). Google Sheet: Duplicate the provided template Sheet structure. Your sheet must have columns like Hospital Name and Main Email. Workflow Configuration: Replace the placeholder Google Sheet ID in the Set Configuration node with the ID of your own sheet. Requirements An n8n instance (cloud or self-hosted). A Google account with access to Google Sheets and Gmail. The provided Google Sheets template structure. How to customize Email Template:* Modify the email subject and body in the *Send Gmail Message** node. Use placeholders like {{ $json["Your Field"] }} to insert data from your Google Sheet. Data Source:** Replace the Google Sheets node with another data source (e.g., Airtable, PostgreSQL) by ensuring it outputs data in a similar JSON format. Output:** Instead of Gmail, use the SendBlue node to send an SMS or the Slack node to send a DM. An n8n automation workflow template by Hans Wilhelm Radam.

By IranServer.com

Monitor VPS security with AI analysis via SSH and Telegram alerts This n8n template automatically monitors your VPS for suspicious processes and network connections using AI analysis. It connects to your server via SSH, analyzes running processes, and sends Telegram alerts when potential security threats are detected. Who's it for System administrators managing VPS/dedicated servers DevOps teams monitoring production environments Security-conscious users who want automated threat detection Anyone running services on Linux servers who wants proactive monitoring How it works The workflow runs on a scheduled basis and performs the following steps: SSH Connection: Connects to your VPS via SSH and executes system commands to gather process and network information Data Collection: Runs ps aux --sort=-%cpu,-%mem && ss -tulpn to capture running processes sorted by CPU/memory usage and active network connections AI Analysis: Uses OpenAI's language model to analyze the collected data for suspicious patterns, malware signatures, unusual network connections, or abnormal resource usage Structured Output: Parses AI responses into structured data identifying malicious and suspicious activities with explanations Alert System: Sends immediate Telegram notifications when malicious processes are detected Requirements SSH access** to your VPS with valid credentials OpenAI API key** for AI analysis (uses GPT-4 mini model) Telegram Bot** and chat ID for receiving alerts Linux-based VPS or server to monitor How to set up Configure SSH credentials: Set up SSH connection to your VPS in the "Execute a command" node Add OpenAI API key: Configure your OpenAI credentials in the "OpenAI Chat Model" node Set up Telegram bot: Create a Telegram bot and get the API token Get your Telegram chat ID Update the admin_telegram_id in the "Edit Fields" node with your chat ID Configure Telegram credentials in the "Send a text message" node Adjust schedule: Modify the "Schedule Trigger" to set your preferred monitoring frequency Test the workflow: Run a manual execution to ensure all connections work properly How to customize the workflow Change monitoring frequency**: Adjust the schedule trigger interval (hourly, daily, etc.) Modify analysis criteria**: Update the AI prompt in "Basic LLM Chain" to focus on specific security concerns Add more commands**: Extend the SSH command to include additional system information like disk usage, log entries, or specific service status Multiple servers**: Duplicate the SSH execution nodes to monitor multiple VPS instances Different alert channels**: Replace or add to Telegram with email, Slack, or Discord notifications Custom filtering**: Add conditions to filter out known safe processes or focus on specific suspicious patterns Good to know The AI model analyzes both running processes and network connections for comprehensive monitoring Each analysis request costs approximately $0.001-0.01 USD depending on system activity The workflow only sends alerts when malicious or suspicious activity is detected, reducing notification noise SSH commands require appropriate permissions on the target server Consider running this workflow from a secure, always-on n8n instance for continuous monitoring. An n8n automation workflow template by IranServer.com.

By vanhon

Split Test AI Prompts Using Supabase & Langchain Agent This workflow allows you to A/B test different prompts for an AI chatbot powered by Langchain and OpenAI. It uses Supabase to persist session state and randomly assigns users to either a baseline or alternative prompt, ensuring consistent prompt usage across the conversation. 🧠 Use Case Prompt optimization is crucial for maximizing the performance of AI assistants. This workflow helps you run controlled experiments on different prompt versions, giving you a reliable way to compare performance over time. ⚙️ How It Works When a message is received, the system checks whether the session already exists in the Supabase table. If not, it randomly assigns the session to either the baseline or alternative prompt. The selected prompt is passed into a Langchain Agent using the OpenAI Chat Model. Postgres is used as chat memory for multi-turn conversation support. 🧪 Features Randomized A/B split test per session Supabase database for session persistence Langchain Agent + OpenAI GPT-4o integration PostgreSQL memory for maintaining chat context Fully documented with sticky notes 🛠️ Setup Instructions Create a Supabase table named split_test_sessions with the following columns: session_id (text) show_alternative (boolean) Add credentials for: Supabase OpenAI PostgreSQL (for chat memory) Modify the "Define Path Values" node to set your baseline and alternative prompts. Activate the workflow. Send messages to test both prompt paths in action. 🔄 Next Steps Add tracking for conversions or feedback scores to compare outcomes. Modify the prompt content or model settings (e.g. temperature, model version). Expand to multi-variant tests beyond A/B. 📚 Learn More How This Workflow Uses Supabase + OpenAI for Prompt Testing. An n8n automation workflow template by vanhon.

By Atik

Automate multi-document handling with AI-powered extraction that adapts to any format and organizes it instantly. What this workflow does Monitors Google Drive for new uploads (receipts, resumes, claims, physician orders, blueprints, or any doc type) Automatically downloads and prepares files for analysis Identifies the document type using Google Gemini Parses structured data via the trusted VLM Run node with OCR + layout parsing Stores records in Google Sheets — AI Agent maps values to the correct sheet dynamically Setup Prerequisites: Google Drive & Google Sheets accounts, VLM Run API credentials, n8n instance. Install the verified VLM Run node by searching for VLM Run in the node list, then click Install. Once installed, you can integrate it directly for high-accuracy data extraction. Quick Setup: Configure Google Drive OAuth2 and select a folder for uploads Add VLM Run API credentials Create a Master Reference Google Sheet with the following structure: | Document_Name | Spreadsheet_ID | | ---------------------- | ----------------------------- | | Receipt | your-receipt-sheet-id | | Resume | your-resume-sheet-id | | Physician Order | your-physician-order-sheet-id | | Claims Processing | your-claims-sheet-id | | Construction Blueprint | your-blueprint-sheet-id | The first column holds the document type, and the second column holds the target sheet ID where extracted data should be appended. In the AI Agent node, edit the agent prompt to: Analyze the JSON payload from VLM Run Look up the document type in the Master Reference Sheet If a matching sheet exists → fetch headers, then append data accordingly If headers don’t exist → create them from JSON keys, then insert values If no sheet exists → add the new type to the Master Reference with an empty Spreadsheet ID Test with a sample upload and activate the workflow How to customize this workflow to your needs Extend functionality by: Adjusting the AI Agent prompt to support any new document schema (just update field mappings) Adding support for multi-language OCR or complex layouts in VLM Run Linking Sheets data to BI dashboards or reporting tools Triggering notifications when new entries are stored This workflow leverages the VLM Run node for flexible, precision extraction and the AI Agent for intelligent mapping, creating a powerful system that adapts to any document type with minimal setup changes. An n8n automation workflow template by Atik.

By Anshul Chauhan

Automate Your Life: The Ultimate AI Assistant in Telegram (Powered by Google Gemini) Transform your Telegram messenger into a powerful, multi-modal personal or team assistant. This n8n workflow creates an intelligent agent that can understand text, voice, images, and documents, and take action by connecting to your favorite tools like Google Calendar, Gmail, Todoist, and more. At its core, a powerful Manager Agent, driven by Google Gemini, interprets your requests, orchestrates a team of specialized sub-agents, and delivers a coherent, final response, all while maintaining a persistent memory of your conversations. Key Features 🧠 Intelligent Automation: Uses Google Gemini as a central "Manager Agent" to understand complex requests and delegate tasks to the appropriate tool. 🗣️ Multi-Modal Input: Interact naturally by sending text, voice notes, photos, or documents directly into your Telegram chat. 🔌 Integrated Toolset: Comes pre-configured with agents to manage your memory, tasks, emails, calendar, research, and project sheets. 🗂️ Persistent Memory: Leverages Airtable as a knowledge base, allowing the assistant to save and recall personal details, company information, or past conversations for context-rich interactions. ⚙️ Smart Routing: Automatically detects the type of message you send and routes it through the correct processing pipeline (e.g., voice is transcribed, images are analyzed). 🔄 Conversational Context: Utilizes a window buffer to maintain short-term memory, ensuring follow-up questions and commands are understood within the current conversation. How It Works The Telegram Trigger node acts as the entry point, receiving all incoming messages (text, voice, photo, document). A Switch node intelligently routes the message based on its type: Voice**: The audio file is downloaded and transcribed into text using a voice-to-text service. Photo**: The image is downloaded, converted to a base64 string, and prepared for visual analysis. Document**: The file is routed to a document handler that extracts its text content for processing. Text**: The message is used as-is. A Merge node gathers the processed input into a unified prompt. The Manager Agent receives this prompt. It analyzes the user's intent and orchestrates one or more specialized agents/tools: memory_base (Airtable): For saving and retrieving information from your long-term knowledge base. todo_and_task_manager (Todoist): To create, assign, or check tasks. email_agent (Gmail): To compose, search, or send emails. calendar_agent (Google Calendar): To schedule events or check your agenda. research_agent (Wikipedia/Web Search): To look up information. project_management (Google Sheets): To provide updates on project trackers. After executing the required tasks, the Manager Agent formulates a final response and sends it back to you via the Telegram node. Setup Instructions Follow these steps to get your AI assistant up and running. Telegram Bot: Create a new bot using the BotFather in Telegram to get your Bot Token. In the n8n workflow, configure the Telegram Trigger node's webhook. Add your Bot Token to the credentials in all Telegram nodes. For proactive messages, replace the chatId placeholders with your personal Telegram Chat ID. Google Gemini AI: In the Google Gemini nodes, add your credentials by providing your Google Gemini API key. Airtable Knowledge Base: Set up an Airtable base to act as your assistant's long-term memory. In the memory_base nodes (Airtable nodes), configure the credentials and provide the Base ID and Table ID. Google Workspace APIs: Connect your Google account credentials for Gmail, Google Calendar, and Google Sheets. In the relevant nodes, specify the Document/Sheet IDs you want the assistant to manage. Connect Other Tools: Add your credentials for Todoist and any other integrated tool APIs. Configure Conversational Memory: This workflow is designed for multi-user support. Verify that the Session Key in the "Window Buffer Memory" nodes is correctly set to a unique user identifier from Telegram (e.g., {{ $json.chat.id }}). This ensures conversations from different users are kept separate. Review Schedule Triggers: Check any nodes designed to run on a schedule (e.g., "At a regular time"). Adjust their cron expressions, times, and timezone to fit your needs (e.g., for daily summaries). Test the Workflow: Activate the workflow. Send a text message to your bot (e.g., "Hello!"). Estimated Setup Time 30–60 minutes:** If you already have your API keys, account credentials, and service IDs (like Sheet IDs) ready. 2–3 hours:** For a complete, first-time setup, which includes creating API keys, setting up new spreadsheets or Airtable bases, and configuring detailed permissions. An n8n automation workflow template by Anshul Chauhan.

By iMan

Quick overview This workflow completely automates posting Instagram Stories using a Google Sheet. By adding direct video URLs to your sheet, the workflow automatically schedules, shuffles, and publishes the content while preventing duplicates, giving you a hands-free social media strategy. How it works A scheduled trigger kicks off the workflow automatically at your specified daily time. The workflow connects to your Google Sheet and retrieves the list of available video URLs. It intelligently filters out videos that have already been published by checking the posted_story column for a "true" value. The remaining unposted video URLs are randomized to ensure a varied content mix rather than posting straight down the list. The workflow sends the selected direct video link to the Instagram Graph API, which processes and publishes the video as a Story. Finally, the workflow updates your Google Sheet, marking the published video row as "true" to prevent any future duplicate posts. Setup Prepare your Google Sheet by ensuring it has two specific columns named exactly source_url and posted_story. You can extract your Sheet ID from the URL. Log into your Instagram account via the Accounts Center and copy your Instagram Business Account ID (the numerical format at the end of the URL). Go to Meta for Developers, create a new Meta App, and add the "Instagram Graph API" product. Grant the necessary permissions in your Meta App: instagram_basic, instagram_content_publish, pages_show_list, and pages_read_engagement. Generate a Long-Lived Access Token from Meta so n8n maintains persistent access to post on your behalf. Open the n8n Configuration Hub Node and input your IG_BUSINESS_ID, SHEET_DOC_ID, and the exact SHEET_TAB_NAME. Create and connect your Google Sheets credentials and Facebook Graph API credentials within the required nodes, run a manual test, and activate the workflow. Requirements An Instagram Business or Creator account that is fully connected to a Facebook Page. A Meta Developer Account to create the necessary App permissions. A publicly accessible storage solution that provides direct links to your video files (e.g., Amazon S3, Shopify, or a secure WordPress site). Direct video URLs only; shared links from services like Google Drive or Dropbox are incompatible and will fail. Customization Adjust the posting frequency and times by modifying the Auto Schedule node to fit your audience's peak engagement hours. Connect a custom Google Sheet template (downloadable below) to manage your video queue seamlessly. Additional info If the workflow runs but doesn't post, check that you have empty rows in the posted_story column; if all are marked true, there is no new content. If you receive an "Unsupported post request" error, double-check that your video URL is a direct file link and doesn't lead to a web preview page. If you hit a permission error, verify your Meta App scopes in the Developer Dashboard. Resources: Template Download for Long-Lived-Token: https://oprootor.com/wp-content/uploads/2026/06/FaceBook-Long-Lived-Token.zip Creator: @iMan (https://oprootor.com/). An n8n automation workflow template by iMan.

By ResilNext

📖 Description 🔹 How it works This workflow introduces an AI + Human-in-the-Loop pipeline for employee timesheet management. It combines the power of Google Drive, AI (OCR + LLM), and Gmail with a human review step to ensure accuracy and compliance. AI-Powered File Discovery Scans a Google Drive folder for new or updated timesheet files (PDF, Word, Excel, Images). AI Data Extraction Uses OCR and LLM (Mistral) to intelligently read and extract structured data. Supports multiple formats: PDF, Word (DOC/DOCX), Excel (XLS/XLSX), and Image files (JPG, PNG, scanned documents). Creates clean JSON with file details and timesheet logs (date, hours worked, tasks, notes). Smart Data Formatting Converts AI output into a clear HTML summary table for easy review. Flags potential anomalies (missing hours, duplicate dates, irregular entries). Human-in-the-Loop Verification Sends an approval email via Gmail containing: File metadata AI-generated HTML summary JSON attachment of raw extracted data HR/Managers review the summary and approve/reject before final actions occur. Post-Approval Automation (optional) Approved records can be saved in a separate Google Drive folder. Employees or HR receive confirmation emails. ⚙️ Set up steps Connect Credentials Add Google Drive and Gmail credentials in n8n. Configure Mistral (or any LLM) API credentials. Configure Google Drive In the “Search files and folders” node, replace the folderId with your company’s timesheet folder ID. Customize Extraction Schema Sticky notes explain how JSON output is structured. Adapt it for your organization’s needs (e.g., overtime, project codes). Set Up Human Verification Emails Update Gmail node recipients to your HR or approval team. Customize the email body (AI summary + JSON file attached). Activate & Test Enable the workflow. Upload a sample timesheet to trigger the AI + human verification loop. ⚡ Result: A robust AI + Human-in-the-Loop workflow that reduces repetitive data entry, prevents payroll errors, and gives HR full confidence before final approval. An n8n automation workflow template by ResilNext.

By Elay Guez

AI-Powered HR Candidate Evaluation Agent with LinkedIn Data Enrichment in CSV/XLSX Format 🎯 Overview Transform your manual hiring process into an intelligent evaluation system that saves 15-20 minutes per candidate! This workflow automates the entire candidate assessment pipeline - from CSV/XLSX upload to AI-powered scoring with LinkedIn insights. When you upload a candidate list, this workflow automatically: 📊 Converts your file into a formatted Google Sheet with RTL support 🔍 Researches each candidate's recent LinkedIn posts via Apify 🤖 Evaluates candidates using GPT-4.1 with context-aware scoring (0-100) 💬 Generates professional Hebrew explanations for each score 📈 Auto-sorts by score and applies professional formatting ⚠️ Sends error alerts to keep everything running smoothly Cost per candidate: ~$0.05 | Time saved: 15-20 minutes each 👥 Who's it for? HR teams drowning in candidate applications Recruitment agencies needing consistent evaluation criteria Hiring managers seeking data-driven candidate insights Companies looking to scale their team Anyone tired of manual spreadsheet juggling ⚡ How it works Form submission triggers with CSV/XLSX upload Google Drive stores the file and creates a new Sheet Data extraction processes the file content AI Agent loops through each candidate: Fetches up to 3 recent LinkedIn posts via Apify Analyzes qualifications against job requirements Generates evaluation score and Hebrew explanation Sheet formatting applies filters, sorting, and styling Error handling notifies admin of any issues 🛠️ Setup Instructions Time to deploy: 15 minutes Requirements: Google account (Drive + Sheets access) OpenAI API key (GPT-4.1 access) Apify API key (for LinkedIn scraping) Gmail account (for error notifications) Step-by-step: Import this template into your n8n instance Configure Google credentials: Connect Google Drive OAuth2 Connect Google Sheets OAuth2 Add OpenAI API key to the GPT-4.1 node Set up Apify credentials for LinkedIn scraping Configure Gmail for error alerts (update email in "Send a message" node) Update folder IDs in Google Drive nodes to your folders Test with a sample CSV containing 2-3 candidates Activate and share the form URL with your team! 📋 Input File Format Your CSV/XLSX should include these columns (Hebrew): שם פרטי (First name) שם משפחה (Last name) חשבון לינקדאין (LinkedIn URL) Your custom evaluation questions 🎨 Customization Options Easy tweaks: Scoring criteria**: Modify the AI agent's system message Language**: Switch from Hebrew to any language Scoring rubric**: Adjust the 50/25/15/10 weighting LinkedIn posts**: Change from 3 posts to more/fewer Sheet styling**: Customize colors and formatting Advanced modifications: Add integration with your ATS (Greenhouse, Lever, etc.) Connect to Slack for real-time notifications Add multiple evaluation agents for different roles Implement multi-language support Add candidate email automation 💡 Pro Tips Better LinkedIn data**: Ensure candidates provide complete LinkedIn URLs (not just usernames) Consistent scoring**: Run batches of similar roles together for normalized scoring Cost optimization**: Adjust Apify settings to fetch only essential data Scale smartly**: Process in batches of min 10-20 for optimal performance ⚠️ Important Notes LinkedIn scraping respects Apify's rate limits Scores are relative within each batch - don't compare across different job roles The workflow handles both CSV and XLSX formats automatically Error notifications help you catch issues before they cascade 📊 Expected Results After implementation, expect: Data-driven evaluation across candidates Professional explanation for hiring decisions Happy recruiters who can focus on human connection Built with ❤️ by Elay Guez. An n8n automation workflow template by Elay Guez.

By Athanasios

AI Interior Design Assistant: Your Digital Design Partner What This System Does This n8n workflow transforms your Telegram into a professional interior design studio powered by artificial intelligence. Send a photo of furniture or a room space, and watch as the system intelligently catalogs items, documents spaces, and generates stunning custom interior designs tailored to your vision. The Magic Behind the Scenes Smart Image Recognition When you upload a photo, the system immediately springs into action with sophisticated image analysis: Furniture Detection**: Spots individual pieces like sofas, chairs, tables, and lamps with catalog-precision accuracy Room Analysis**: Identifies complete spaces, architectural features, lighting conditions, and existing design elements Style Classification**: Determines design styles from modern minimalist to traditional classic Material Recognition**: Identifies wood types, fabric textures, metal finishes, and color palettes Intelligent Database Management The workflow maintains three interconnected databases that work like a professional design firm's catalog system: Furniture Catalog (catalog_products) Comprehensive product details including style, materials, dimensions, and compatibility Professional descriptions written for interior designers Searchable tags for quick design matching High-quality image storage for visual reference Room Documentation (rooms) Detailed space analysis including size, style, and architectural features Color palette documentation and lighting assessment Existing furniture inventory for design planning Room-specific design recommendations Design Portfolio (ai_generated_images) Archive of all AI-generated interior designs Original prompts and design descriptions Searchable by style, room type, or specific elements Ready for client presentations or further modifications AI-Powered Design Generation The system's crown jewel is its ability to create stunning interior visualizations: Contextual Understanding: Combines room characteristics with catalog products to create realistic design scenarios Professional Prompting: Generates detailed, interior-design-specific prompts that result in high-quality, commercially viable designs Style Consistency: Maintains design coherence across different elements while respecting user preferences Modification Capabilities: Can reference and modify previous designs, allowing for iterative improvements The User Experience Journey Scenario 1: Building Your Furniture Catalog Upload: Send photos of furniture pieces via Telegram Analysis: AI examines each piece, identifying style, materials, dimensions, and design era Cataloging: Items are professionally documented with searchable metadata Confirmation: Receive detailed catalog entries for each piece Scenario 2: Documenting Your Spaces Room Photos: Share images of your living spaces Space Analysis: AI assesses room size, style, lighting, and architectural features Documentation: Complete room profiles are created for design planning Inventory: Existing furniture and design elements are noted Scenario 3: Creating Custom Designs Design Request: Ask for specific interior modifications or new layouts Smart Matching: System pulls relevant items from your catalog and room data AI Generation: Gemini 2.5 Flash creates photorealistic interior designs Instant Delivery: Receive professional-quality visualizations via Telegram Scenario 4: Design Evolution Reference Previous Work: Mention earlier designs you want to modify Contextual Modification: AI understands your reference and applies new changes Enhanced Generation: Creates updated designs building on previous concepts Continuous Improvement: Iterate until the design matches your vision Technical Sophistication Multi-AI Coordination OpenAI GPT-4**: Handles complex reasoning, database operations, and user interaction Google Gemini 2.5 Flash**: Specializes in high-quality image generation with interior design expertise Intelligent Routing**: Automatically determines whether to catalog, document, or generate based on context Professional Data Structure The database schema reflects real interior design workflows: Industry-standard categorization systems Professional terminology and measurements Design compatibility matrices Style and era classifications used by actual designers Seamless Integration Telegram Interface**: No app downloads or complex interfaces - just send photos and text Cloud Storage**: All images stored in Supabase with public URLs for easy access Real-time Processing**: Immediate feedback and rapid design generation Persistent Memory**: Everything is saved and searchable for future reference Why This Matters This workflow bridges the gap between professional interior design tools and accessible consumer technology. It provides: For Design Professionals: A powerful cataloging and visualization tool that streamlines client presentations and design iteration For Homeowners: Professional-level design capability without the cost or complexity of traditional design software For Businesses: A scalable solution for furniture visualization, space planning, and customer engagement The Innovation Factor Unlike simple design apps that work with generic templates, this system: Learns your specific furniture and spaces Maintains design continuity across projects Provides professional-quality outputs Scales from single rooms to complete home designs Integrates seamlessly into your daily communication workflow The result is a design assistant that feels less like software and more like having a professional interior designer available 24/7 through your phone. Future Possibilities This foundation supports expansion into: Room dimension calculations and space optimization Integration with furniture retailers for purchase links 3D room modeling and virtual reality previews Style preference learning and automated suggestions Multi-user collaboration for design teams The workflow represents a new paradigm where AI doesn't replace human creativity but amplifies it, making professional design capabilities accessible to anyone with a smartphone and an imagination. An n8n automation workflow template by Athanasios.

By Khairul Muhtadin

Deleted a workflow by accident? This backup system keeps every n8n workflow safe in Google Drive and GitHub, with full version history. Set it once, and your automations protect themselves. Last updated: September 2026. Why You Need This Right Now Stop the panic attacks. We've all been there: a workflow that took hours to build, gone in one wrong click. This is your safety net. Save your weekends. No more rebuilding lost work. One setup protects everything, automatically. Sleep better at night. Your workflows live in two places with full version history. If something breaks, you're back in minutes, not days. Perfect For These Situations Business owners** running critical automations Agencies** managing client workflows Teams** who need audit trails Anyone** who values their time and sanity How It Actually Works Think of it like a personal assistant who: Checks your workflows twice daily (you can change this) Creates organized backups with timestamps Stores them safely in Google Drive AND GitHub Tells you it's done via Telegram or Discord Keeps everything tidy with smart folder organization The result? A timestamped folder in your Google Drive and organized files in your GitHub repo. Everything is searchable, restorable, and audit-ready. Quick 5-Minute Setup Import this workflow to your n8n Connect your accounts (Google Drive, GitHub (docs), optional notifications) Set your preferences (which folder, which repo, how often) Test it once to make sure everything works Relax knowing your workflows are protected What You'll Need Your n8n instance (obviously!) Google Drive account (free works fine) GitHub account (free works too) 5 minutes of setup time Optional: Telegram or Discord for notifications Pro Tips for Power Users Want to level up? Here are some ideas: Add encryption** for sensitive workflows Create restore workflows** for one-click recovery Set up pull requests** for team review of changes Customize schedules** based on your workflow update frequency Quick Answers How often does it back up? Twice daily by default. Change the schedule to whatever fits your pace. Where are backups stored? Google Drive and GitHub, organized in timestamped folders with version history. What if something breaks? Restore from the stored version. Recovery takes minutes, not days. Made by: khmuhtadin - Automation expert who actually uses this daily Tags: backup, automation, n8n, google-drive, github, workflow-protection, business-continuity Questions? Get in touch - always happy to help fellow automation enthusiasts! Remember: The best backup is the one you set up before you need it. Your future self will thank you! Additional info Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/. An n8n automation workflow template by Khairul Muhtadin.

By ResilNext

📖 Description 🔹 How it works This workflow turns a Google Form submission into a polished, SEO-optimized technical blog with a human approval step before publishing. Google Form Submission (Trigger) The process begins when a Google Form is filled. Responses are stored in Google Sheets, which acts as the trigger for the workflow. AI Blog Draft Generation Takes the form inputs (problem statement, options tried, solution, learnings, references, etc.). AI generates a structured draft JSON blog post containing: Title & metadata Problem explanation Solution breakdown Implementation methods with realistic code snippets Troubleshooting, performance tips, security notes, advanced use cases Clear developer-focused conclusion Template Fitting Reformats the draft into a professional long-form blog structure with consistent headings (H1, H2, H3), code blocks, and clear formatting. Optimization Layer Applies multi-layer optimization to make the blog: SEO-friendly (keywords, meta description, structured headings). GEO-ready (Generative Engine Optimization for visibility in ChatGPT, Claude, Gemini, etc.). Human-like in tone (reads naturally, avoids AI-detector flags). Human-in-the-Loop Review Sends the draft via Gmail (Send + Wait for Response) to an editor or approver. Approver options: ✅ Approve → Blog is stored & marked completed. ❌ Reject → Feedback is sent for revision. 🚫 Cancel → Workflow ends save status in sheets. Publishing / Storage Approved blogs are stored in a separate Google Sheet for publication tracking. Status in the original sheet is updated to Completed. ⚙️ Set up steps Connect Google Sheets & Gmail in n8n. Link your Google Form to the trigger sheet. Add AI provider credentials (Groq, Mistral, or OpenRouter). Customize blog structure (problem, solution, code, references, etc.). Set reviewer email(s) in Gmail node. Test the workflow by submitting a sample Google Form response. google form sample: ⚡ Result: A fully automated pipeline where filling a Google Form kicks off AI-powered blog generation, optimization, and a human-in-the-loop approval process, making technical content creation faster and more reliable. An n8n automation workflow template by ResilNext.

By Yang

Who's it for This template is perfect for YouTube creators, content marketers, and social media managers who want to turn existing videos into fresh, high-performing content ideas—automatically. It’s ideal if you want to save time brainstorming and focus on publishing videos that your audience actually wants. What it does This workflow watches a Google Sheet for new YouTube video links. For each new video, it fetches the transcript and top comments using Dumpling AI, then sends that data along with the original search topic to GPT-4o. GPT-4o returns 3–5 new content ideas based on: What was discussed in the video What people are searching for What viewers are saying in the comments Each idea is saved to another Google Sheet and also sent to your email. How it works Trigger: Watches for new rows in the "YouTube Finds" sheet Transcript & Comments: Sends video URL to Dumpling AI to fetch transcript and comments Merge & Format: Cleans and aggregates comments into one input AI Prompting: GPT-4o analyzes transcript, topic, and comments to suggest ideas Output: Splits and saves the results to a "YouTube Content Idea" sheet and emails them Requirements 🧠 OpenAI API Key stored securely in credentials 🤖 Dumpling AI API Key stored as HTTP header credentials 📄 Google Sheets with the following setup: Input Sheet ("YouTube Finds") Video Link search topic Output Sheet ("YouTube Content Idea") title whyGoodIdea engagementPotential How to customize You can: Change the number of ideas returned by GPT-4o Adjust the AI prompt to reflect your niche (e.g. education, tech, travel) Add an approval step before sending the email Extend it to post ideas directly into Trello, Notion, or Airtable > This workflow gives you an automated content strategist working 24/7—turning every YouTube upload into a launching pad for future content. An n8n automation workflow template by Yang.

By Sk developer

📊 Automated Website Traffic Tracker with Google Sheets Logging Track website traffic and backlinks effortlessly using the Website Traffic Checker - Ahref API. This n8n workflow automates data retrieval and logging into Google Sheets, making it perfect for SEO professionals and digital marketers. 🧩 What This Workflow Does (Summary) Accepts a domain via a simple web form. Sends the domain to Website Traffic Checker - Ahref API. If successful: Extracts backlink and traffic data. Appends the results to two separate Google Sheets. If failed: Sends an email alert with domain and status code. 🔧 Node-by-Node Explanation | Node | Purpose | | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | 🟢 Form Trigger | Starts the workflow when a domain is submitted via form. | | 🟩 Set Domain Value | Stores the submitted domain into a variable. | | 🌐 HTTP Request | Calls Website Traffic Checker - Ahref API. | | ✅ IF Node | Checks if the API responded with statusCode = 200. | | ❌ Email Node (Fail) | Sends an alert email if API fails. | | 📦 Code (Backlink Info) | Extracts backlink data from API response. | | 📄 Google Sheet: Backlink Info | Appends backlink data to a sheet. | | 📦 Code (Traffic Info) | Extracts traffic data from API response. | | 📄 Google Sheet: Traffic Data | Appends traffic metrics to another sheet. | 📁 Google Sheet Columns Backlink Info Sheet | Column | Description | | ------------------ | --------------------------- | | website | Domain submitted | | ascore | Authority score | | referring domain | Number of referring domains | | total backlinks | Total backlinks | Traffic Data Sheet | Column | Description | |----------------------|---------------------------------------------| | accuracy | Accuracy level of the traffic data | | bounce_rate | Bounce rate percentage | | desktop_share | Percentage of traffic from desktop devices | | direct | Direct traffic sources | | display_ad | Display ad traffic sources | | display_date | Date when traffic data was captured | | mail | Traffic from email campaigns | | mobile_share | Percentage of traffic from mobile devices | | pages_per_visit | Average number of pages per visit | | paid | Paid traffic sources | | prev_bounce_rate | Bounce rate in the previous period | | prev_direct | Previous period's direct traffic | | prev_display_ad | Previous period's display ad traffic | | prev_mail | Previous period's email traffic | | prev_pages_per_visit | Previous period's pages per visit | | prev_referral | Previous period's referral traffic | | prev_search_organic | Previous organic search traffic | | prev_search_paid | Previous paid search traffic | | prev_social_organic | Previous organic social traffic | | prev_social_paid | Previous paid social traffic | | prev_time_on_site | Previous time spent on site | | prev_users | Number of users in the previous period | | prev_visits | Visits in the previous period | | rank | Global rank of the website | | referral | Referral traffic | | search | Total search traffic | | search_organic | Organic search traffic | | search_paid | Paid search traffic | | social | Total social traffic | | social_organic | Organic social traffic | | social_paid | Paid social traffic | | target | Targeted country or demographic | | time_on_site | Average time spent on site | | unknown_channel | Traffic from unknown sources | | users | Number of unique users | | visits | Total number of visits | 🔐 How to Configure 🔑 Get API Key Go to Website Traffic Checker - Ahref API on RapidAPI. Sign in or create a free RapidAPI account. Subscribe to the API plan. Copy your x-rapidapi-key from the Endpoints tab. 📝 Add Key in n8n Go to your HTTP Request node. Under Headers, set: x-rapidapi-host = website-traffic-checker-ahref.p.rapidapi.com x-rapidapi-key = your API key 📄 How to Setup Google Sheets in n8n Connect a Google account via Google Sheets credentials in n8n. Use the full Google Sheet URL in the documentId field. Set correct Sheet name or GID (e.g., "Traffic Data"). Use Auto Map or Custom Map to define columns. > Make sure your Google Sheet has edit access and headers already created. 🧠 Use Case & Benefits 👤 Ideal For: SEO analysts Digital marketers Agencies managing multiple clients Web analytics consultants ✅ Benefits: Fully automated data collection. No manual copy-paste** from tools. Real-time insights delivered to Google Sheets. Easy monitoring of backlinks and traffic trends. An n8n automation workflow template by Sk developer.

By Cong Nguyen

📄 What this workflow does This workflow turns your n8n into an automated product-video generator powered by Google Sheets. When a new row is added with status = run, it: Downloads the product image from Google Drive. Converts the image to base64 and sends it to Gemini, which creates a branded ad-style variant. Saves the generated image back into a designated Google Drive folder. Sends the image to FAL (image-to-video) to generate a short promotional video clip. Polls FAL’s response_url until the video is ready. Uploads the video to Google Drive (videos folder). Updates the original Google Sheet row with the video link and sets status = finished. Handles API latency via wait/polling and logs failures into the sheet if needed. 👤 Who is this for Marketing teams automating creative asset production. E-commerce businesses needing quick product promo videos. Agencies creating branded ad content at scale. ✅ Requirements An n8n instance. A Google Sheet with at least these columns: STT, link_image, note, status, link_video. Google Sheets & Google Drive OAuth2 credentials connected in n8n. Gemini API key (for ad-style image generation). FAL API key (for image-to-video). ⚙️ How to set up Import the provided workflow JSON into n8n. Connect Google Sheets credentials and point to your sheet (documentId + gid). Connect Google Drive credentials and update folder IDs in the two Upload File nodes (images/videos). Add Gemini and FAL API keys in the respective HTTP Request headers (via Credentials). Test: add a row with link_image, note, and status = run. The workflow should generate and save a video, then update the sheet with the link. 🔁 How it works Trigger → Google Sheets Trigger fires on rowAdded where status = run. Pre-processing → Download the product image from Google Drive → extract base64. LLM Image Generation → Gemini generates an ad-style variant based on note. Storage → Upload the generated image into the “images” Drive folder. Video Creation → FAL converts the branded image into a short video. Polling → Wait node + HTTP Request check job status until video is completed. Write-back → Upload final video into the “videos” Drive folder, update the sheet with the link_video, and set status = finished. An n8n automation workflow template by Cong Nguyen.

By ResilNext

📖 Description 🔹 How it works This workflow uses AI (Mistral LLM + Pollinations.ai) to generate high-quality visual content for social media campaigns. It automates the process from brand/campaign input to final image upload, ensuring consistency and relevance. Input Brand & Campaign Data Retrieves brand profile and campaign goals from Google Drive. Cleans and merges the data into a structured JSON format. Campaign Goal Generation AI summarizes campaign goals, audience, success metrics, and keywords. Produces a clear campaign goal summary for content planning. Image Prompt Generation AI creates 5 detailed image prompts reflecting the campaign story. Includes 1 caption and 4–6 relevant hashtags. Image Creation Pollinations.ai generates images based on the AI prompts. Each image is renamed systematically (photo1 → photo5). Post-Processing & Upload All images are merged into a single item. Workflow uploads the final output to Google Drive for campaign use. ⚙️ Set up steps Connect Credentials Add Google Drive and Mistral API credentials in n8n. Configure Google Drive Input Nodes Set fileId for brand profile and campaign goals. Customize AI Prompts Sticky notes explain AI nodes for goal summary and image prompt generation. Optionally modify tone, keywords, or target audience for brand-specific campaigns. Check Image Output Nodes Ensure Pollinations.ai HTTP request nodes are active. Verify renaming code nodes for proper photo sequence. Activate Workflow Test workflow manually to ensure images are generated and uploaded correctly. 🔹 Data Handling & Output This workflow pulls brand profile and campaign goal data from Google Drive. Data is processed into structured JSON, including: Brand Profile: name, mission, vision, values, services, tone, keywords, contact info. Campaign Goal: primary goal, focus, success metrics, target audience, core message. Supports population of multiple campaigns or brands dynamically. JSON output can be used downstream for image prompt generation, reporting, or analytics. All processing is automated, with clear nodes for extraction, parsing, and merging. pollinations.ai is an open-source free text and image generation API available. No signups or API keys required. which prioritize your privacy with zero data storage and completely anonymous usage. ⚡ Result: A fully automated AI-to-image workflow that transforms campaign goals into ready-to-use social media visuals, saving time and maintaining brand consistency. An n8n automation workflow template by ResilNext.

By Geoffroy

This n8n template saves you hours of manual SEO work by automatically parsing your sitemap and submitting updated URLs to Google and Bing (IndexNow). Who’s it for Site owners, SEOs, and marketers who want a single automation to notify Google (Indexing API) and Bing (via IndexNow) whenever site URLs are added or updated. No more need to update it manually. Hours saved What it does This workflow parses your sitemap.xml, and for each URLs that have been changed on the last X days (this is a setting from Config node), submit them to Google and Bing via IndexNow. Before submitting to Google it checks the status. For IndexNow it just submits based on the last updated date it can find on the sitemap. How it works Parses your sitemap(s)to generate a list of urls ordered by lastmod date. Create a batch of the urls updated in the last X days (settings DAYS_BACK from the "Config" node) For Google, it first aks the current indexing notification status of this exact URL. If the sitemap shows the page was modified after the last submission, the workflow sends a new "URL_UPDATED" notification to Google. If Google has no record (404), it means the URL was never submitted and the workflow treats it as new and submits it. For Bing through IndexNow, it only sends “recently changed URLs” based on the sitemap’s <lastmod> and the variable DAYS_BACK from the Config Node, by batches of 500 (current limit recommendation by Bing). IndexNow doesn't have an API to check the status of the url. Requirements Google Indexing API credentials (Service Account with https://www.googleapis.com/auth/indexing scope, added as Owner in Search Console). IndexNow API key: you can create it here https://www.bing.com/indexnow/getstarted. How to use Edit the "Config" node with your data & preferences (everything explain in the workflow). Edit the "Check status (Google)" and "URL updated (Google)" node with your Google service account credentials. Execute the workflow to test it Set up a cron with the "Schedule Trigger" node depending on your needs. An n8n automation workflow template by Geoffroy.

By Denis

How it works Multi-modal AI Image Generator powered by Google's Nano Banana (Gemini 2.5 Flash Image) - the latest state-of-the-art image generation model Accepts text, images, voice messages, and PDFs via Telegram for maximum flexibility Uses OpenAI GPT models for conversation and image analysis, then Nano Banana for stunning image generation Features conversation memory for iterative image modifications ("make it darker", "change to blue") Processes different input types: analyzes uploaded images, transcribes voice messages, extracts PDF text All inputs are converted to optimized prompts specifically tuned for Nano Banana's capabilities Set up steps Create Telegram bot via @BotFather and get API token Set up Google Gemini API key from Google AI Studio for Nano Banana image generation (~$0.04/image) Configure OpenAI API key for GPT models (conversation, image analysis, voice transcription) Import workflow and configure all three API credentials in n8n Update bot tokens in HTTP request nodes for file downloads Test with text prompts, image uploads, voice messages, and PDF documents. An n8n automation workflow template by Denis.

By Onur

Template Description: > Stop manually reading every CV and copy-pasting data into a spreadsheet. This workflow acts as an AI recruiting assistant, automating your entire initial screening process. It captures applications from a public form, uses AI to read and understand PDF CVs, structures the candidate data, saves it to Google Sheets, and notifies all parties. This template is designed to save HR professionals and small business owners countless hours, ensuring no applicant is missed and all data is consistently structured and stored. 🚀 What does this workflow do? Provides a public web form for candidates to submit their name, email, experience, and PDF CV. Automatically reads the text content from the uploaded PDF CV. Uses an AI Agent (OpenAI) to intelligently parse the CV text, extracting key data like contact info, work experience, education, skills, and more. Writes a concise summary** of the CV, perfect for quick screening by HR. Checks for duplicate applications** based on the candidate's email address. Saves all structured applicant data** into a new row in a Google Sheet, creating a powerful candidate database. Sends an automated confirmation email to the applicant. Sends a new application alert with the CV summary to the recruiter. 🎯 Who is this for? HR Departments & Recruiters:** Streamline your hiring pipeline and build a structured candidate database. Small Business Owners:** Manage job applications professionally without dedicated HR software. Hiring Managers:** Quickly get a summarized overview of each candidate without reading the full CV initially. ✨ Benefits Massive Time Savings:** Drastically reduces the time spent on manual CV screening and data entry. Structured Candidate Data:** Turns every CV into a consistently formatted row in a spreadsheet, making it easy to compare candidates. Never Miss an Applicant:** Every submission is logged, and you're instantly notified. Improved Candidate Experience:** Applicants receive an immediate confirmation that their submission was successful. AI-Powered Summaries:** Get a quick, AI-generated summary of each CV delivered to your inbox. ⚙️ How it Works Form Submission: A candidate fills out the n8n form and uploads their CV. PDF Extraction: The workflow extracts the raw text from the PDF file. AI Analysis: The text is sent to OpenAI with a prompt to structure all key information (experience, skills, etc.) into a JSON format. Duplicate Check: The workflow checks your Google Sheet to see if the applicant's email already exists. If so, it stops. Save to Database: If the applicant is new, their structured data is saved as a new row in Google Sheets. Send Notifications: Two emails are sent simultaneously: a confirmation to the applicant and a notification with the CV summary to the recruiter. 📋 n8n Nodes Used Form Trigger Extract From File OpenAI Code (or JSON Parser) Google Sheets If Gmail 🔑 Prerequisites An active n8n instance. OpenAI Account & API Key**. Google Account** with access to Google Sheets and Gmail (OAuth2 Credentials). A Google Sheet** prepared with columns to store the applicant data (e.g., name, email, experience, skills, cv_summary, etc.). 🛠️ Setup Import the workflow into your n8n instance. Configure Credentials: Connect your credentials for OpenAI and Google (for Sheets & Gmail) in their respective nodes. Customize the Form: In the 1. Applicant Submits Form node, you can add or remove fields as needed. Activate the workflow. Once active, copy the Production URL from the Form Trigger node and share it to receive applications. Set Your Email: In the 8b. Send Notification... (Gmail) node, change the "To" address to your own email address to receive alerts. Link Your Google Sheet: In the 5. Check for Duplicate... and 7. Save Applicant Data... nodes, select your spreadsheet and sheet. An n8n automation workflow template by Onur.

By Charles

🚀 AI Facebook Post Generator - Complete Setup Guide > Transform your content ideas into viral Facebook posts with AI-powered automation in just 30 minutes! 📋 Prerequisites Checklist What you'll need before we start: ✅ n8n instance (cloud or self-hosted) ✅ Facebook Business Page (not personal profile) ✅ Google account with Sheets & Gmail access ✅ Basic understanding of API credentials ⏱️ Estimated Setup Time: 30-45 minutes 🎯 Difficulty Level: Intermediate 💰 Cost: Free tier available for all services 🎨 What You'll Build By the end of this guide, you'll have: 📝 Smart Content Form - Web form that captures your ideas 🤖 AI Content Optimizer - Gemini AI that polishes your writing 🖼️ Auto Image Generator - Custom visuals created automatically 📊 Content Tracker - Google Sheets logging for analytics 📱 Facebook Publisher - Direct posting to your page 📧 Success Notifications - Email confirmations with post links 🔧 Step-by-Step Setup Step 1: 📘 Facebook Integration Setup 🔸 1.1 Create Your Facebook App Why this matters: This gives your workflow permission to post on your behalf. Navigate to Facebook Developers 🌐 Click "My Apps" → "Create App" Select "Business" as your app type App Name: AI-Content-Poster (or your preferred name) Hit "Create App" > 💡 Pro Tip: Choose a descriptive name - you'll see this in your Facebook activity logs 🔸 1.2 Configure App Settings In your app dashboard: "Add a Product" Find "Facebook Login" → "Set Up" Navigate to Settings → Basic App Domains: Add app.n8n.cloud (for n8n cloud users) Save changes ✅ 🔸 1.3 Generate Your Page Access Token This is the key that unlocks posting powers! 🔑 Go to Tools → Graph API Explorer Select your newly created app Click "Generate Access Token" Required Permissions: pages_manage_posts pages_read_engagement pages_show_list Select your target Facebook page Copy the token (starts with EAAG...) ⚠️ Critical Step - Make Token Long-Lived: In Graph API Explorer, make a GET request to: /oauth/access_token?grant_type=fb_exchange_token&client_id=YOUR_APP_ID&client_secret=YOUR_APP_SECRET&fb_exchange_token=YOUR_SHORT_TOKEN 🔸 1.4 Find Your Page ID Two methods to get your Page ID: Method 1 - Direct from Facebook: Visit your Facebook page Click "About" tab Scroll to find "Page ID" Method 2 - API Explorer: Use Graph API Explorer GET request to: /me/accounts Find your page in the response Step 2: 🔍 Google Services Setup 🔸 2.1 Enable Required APIs Setting up your Google Cloud foundation: Visit Google Cloud Console ☁️ Create new project or select existing "APIs & Services" → "Library" Enable these APIs: ✅ Google Sheets API ✅ Gmail API ✅ Google Drive API (optional) 🔸 2.2 Create Service Account This creates a "robot" account for automated access: "APIs & Services" → "Credentials" "Create Credentials" → "Service Account" Name: ai-facebook-automation "Create and Continue" Skip role assignment → "Continue" "Done" ✅ 🔸 2.3 Download Credentials File Click your service account email "Keys" tab → "Add Key" → "Create New Key" Choose "JSON" format Download and save securely 📁 > 🔒 Security Note: This file contains sensitive credentials. Store it safely! 🔸 2.4 Prepare Your Google Sheets Create your data tracking system: 📊 Sheet 1: Content Log Purpose:** Track all generated content Columns:** A: Date (Ngày) B: Short Content (Nội dung ngắn) C: Full Content (Nội dung đầy đủ) 📝 Sheet 2: Input Tracking Purpose:** Log form submissions Columns:** A: Date B: Time C: Content 🔗 Important: Share both sheets with your service account email (found in the JSON file) Step 3: 🤖 AI Services Configuration 🔸 3.1 Get Your Gemini API Key Power up your AI content generation: Head to Google AI Studio 🎨 Sign in with Google account "Create API Key" Copy the key (starts with AIza...) > 💰 Cost Info: Gemini offers generous free tier limits - perfect for getting started! Step 4: ⚙️ n8n Workflow Configuration 🔸 4.1 Import the Magic ✨ Copy the workflow JSON from the template In n8n: "Import from JSON" Paste the workflow code "Import" to load your new automation 🔸 4.2 Configure Your Credentials 🔑 Facebook Graph API Setup: Settings → Credentials → "Add Credential" Search: "Facebook Graph API" Access Token: Your Page Access Token from Step 1.3 Test connection → Save as: Facebook Page Access 🔍 Google Services Setup: "Add Credential" → "Google Service Account" Upload your JSON file from Step 2.3 Test connection → Save as: Google Services 🧠 Gemini AI Setup: "Add Credential" → "Google PaLM API" Enter your Gemini key from Step 3.1 Save as: Gemini AI 🔸 4.3 Customize Node Settings 📱 Update Facebook Configuration: In "Facebook Graph API" node: Replace "113732581629527" with your Page ID from Step 1.4 In "Facebook Upload Img" node: Replace "113732581629527" with your Page ID from Step 1.4 📊 Update Google Sheets: In "save content" node: Replace Document ID with your Content Log Sheet ID In "Append row in sheet" node: Replace Document ID with your Input Tracking Sheet ID > 💡 Finding Sheet ID: It's the long string in your Google Sheets URL after /spreadsheets/d/ 📧 Update Notification Email: In "Send a message" node: Replace xxx@gmail.com with your email address Configure Gmail credentials Step 5: 🧪 Testing & Validation 🔸 5.1 Component Testing 📊 Test Google Sheets Connection: Right-click "Append row in sheet" node "Execute Node" ✅ Verify test row appears in your sheet 🤖 Test Gemini AI: Right-click "Basic LLM Chain" node "Edit Input Data" → Add test content Execute → ✅ Verify AI response quality 🖼️ Test Image Generation: Right-click "HTTP Request" node Ensure valid prompt from previous step Execute → ✅ Check for base64 image data 📱 Test Facebook Upload: Run full workflow with test content ✅ Check your Facebook page for new post ✅ Verify image uploaded correctly 🔸 5.2 End-to-End Victory Test 🎉 "Execute Workflow" on trigger node Submit test content through the form Monitor each node execution 🎊 Celebrate your first AI-generated post! 🎯 Success Indicators Your setup is complete when you see: ✅ Form accepts and processes content ✅ AI generates optimized text + image prompt ✅ Custom image appears in Facebook post ✅ Content logged in Google Sheets ✅ Success email in your inbox ✅ Professional-looking post on your Facebook page 🚨 Troubleshooting Quick Fixes Facebook Issues Token Expired?** → Generate new long-lived token Permission Denied?** → Check page admin rights Invalid Page ID?** → Double-check Page ID format Google Sheets Problems 403 Forbidden?** → Share sheet with service account Sheet Not Found?** → Verify Sheet ID in URL Column Errors?** → Match exact column names AI Content Issues Empty Responses?** → Check Gemini API quotas Poor Quality?** → Adjust AI prompts JSON Errors?** → Validate parsing logic 🎨 Customization Ideas Make it uniquely yours: 🎨 Brand Voice: Adjust AI prompts for your tone ⏰ Scheduling: Add time delays for strategic posting 📈 Analytics: Connect performance tracking tools 🔄 Multi-Platform: Extend to Instagram, LinkedIn 👥 Team Features: Add approval workflows 🎉 You Did It! Congratulations! You've built an AI-powered content machine that will save you hours every week. What's Next? Test with different content types Monitor performance in Google Sheets Refine AI prompts for better results Share your success with the community! Need Help? 🤝 Join n8n Discord Visit Community Forum Check n8n Documentation Ready to revolutionize your content creation? Your AI assistant is waiting! 🚀. An n8n automation workflow template by Charles.

By Davide Boizza

This workflow automates the process of transcribing audio/video files into text using ElevenLabs Speech-to-Text, saving the transcripts to Google Docs, and generating AI-powered summaries and analysis, which are then emailed to a specified address. This ElevenLabs Speech-to-Text model excels in scenarios requiring accurate speech-to-text conversion: Transcription Services: Perfect for converting audio/video content to text Meeting Documentation: Ideal for capturing and documenting conversations Content Analysis: Well-suited for audio content processing and analysis Multilingual Recognition: Supports accurate transcription across 99 languages Files up to 3 GB in size and up to 10 hours in duration are supported. This API supports uploading both audio and video files for transcription. Key Advantages ✅ Automation of Repetitive Tasks: Eliminates manual transcription, note-taking, and reporting. ✅ High-Accuracy Transcription: Powered by ElevenLabs, supporting multiple languages and long files. ✅ Structured Insights: AI-powered analysis (Gemini) transforms raw transcripts into professional summaries with action items and key decisions. ✅ Seamless Integration: Works with Google Sheets, Google Docs, and Gmail for easy workflow adoption. ✅ Scalable & Reusable: Handles multiple recordings in batch and integrates smoothly into existing processes. ✅ Improved Productivity: Teams save time by receiving clear, well-structured meeting recaps without effort. How It Works The workflow operates in a linear sequence, processing one audio URL at a time from a Google Sheet. Trigger & Data Fetch: The process starts manually. It first reads from a specified Google Sheet to get a list of audio file URLs that haven't been processed yet (marked with "DONE"). Transcription: For each audio URL, it sends a request to the ElevenLabs Speech-to-Text API, passing the cloud storage URL of the audio file. Document Creation & Storage: Upon receiving the transcription text from ElevenLabs, the workflow: Creates a new Google Doc named after the transcription ID. Writes the full raw transcript text into this newly created document. Analysis & Summary: The raw transcript text is passed to Google Gemini AI. The AI analyzes the text based on a detailed, pre-defined system prompt that instructs it to extract key points, decisions, action items, and insights, formatting the output as a structured summary. Notification: The AI-generated analysis (converted from Markdown to HTML) is sent via Gmail as an email to a predefined address. Status Update: Finally, the workflow updates the original row in the Google Sheet, marking it as "DONE" (with an 'x') and recording the ID of the newly created Google Doc for future reference. This ensures the same audio file is not processed again on the next run. Set Up Steps To configure this workflow, you need to complete the following steps: Credentials Setup: ElevenLabs API: In the "Speech-to-Text" HTTP Request node, configure the HTTP Header Auth credentials. The header name should be xi-api-key and the value should be your valid ElevenLabs API key. Google Services: Ensure your Google Sheets, Google Docs, and Gmail nodes are connected to valid Google OAuth2 credentials with the necessary permissions to read, write, and send emails. Google Gemini AI: The "Transcript Analysis" node must be connected to valid Google Gemini (PaLM) API credentials. Google Sheet Configuration: Make a copy of the provided Google Sheet template. In the "Get audio urls" node, update the documentId parameter to match the ID of your new Google Sheet. Similarly, update the documentId in the "Update row" node. Populate your sheet with the URLs of the audio/video files you want to process in the 'AUDIO URL' column. Output Configuration: In the "Send email" node, change the sendTo parameter to the email address where you want to receive the analysis summaries. The "Create Doc" node specifies a folderId; change this to the ID of the specific Google Drive folder where you want the transcripts to be saved. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Lenouar

Digital Signature Agent with SignNow + Telegram Solve the #1 Bottleneck in Closing Deals Tired of chasing clients for signed NDAs and contracts? This workflow eliminates the email back-and-forth and lets your clients sign instantly inside Telegram. Faster deal flow** → Cut signing time from days to minutes. No lost opportunities** → Eliminate delays that kill urgency in sales. Professional & secure** → Legally binding signatures, fully trackable. Hands-off automation** → Bot collects details, generates the signing link, and confirms when done. Who Benefits Most ✅ Brokers & consultants: Collect NDAs instantly before sharing sensitive offers. ✅ Agencies & freelancers: Sign contracts with clients on the spot. ✅ SMEs & startups: Speed up sales and onboarding with zero admin overhead. ✅ HR teams: Seamlessly manage employee forms, waivers, and agreements. What It Does for You Triggered by a Telegram chat → no more clunky portals or attachments. Collects name, email, and company in-chat. Copies your SignNow template (NDA, contract, waiver, or any doc). Prefills smart fields automatically. Generates a one-click signing link. Sends it via Telegram as a button (“🖊 Open NDA”). Tracks completion with SignNow webhook → you get notified instantly. Why This Template Instead of Building It Yourself Save 20–30 hours** of research, API testing, and debugging. Avoid headaches connecting SignNow’s API with Telegram. Get a production-ready workflow you can deploy in minutes. Customize easily → swap the NDA for any legal doc, add email/CRM integrations, or adjust the bot’s tone. Peace of mind**: we’ve already tested it end-to-end (template copy, smart fields, webhook confirmation). Requirements n8n (self-hosted or cloud). Active SignNow developer account with API key. A Telegram bot via @BotFather. HTTPS domain/server for webhook callbacks. Bottom Line 💡 This workflow pays for itself the first time it helps you close a deal faster. Instead of waiting 48 hours for someone to check email, they sign within 5 minutes in Telegram—so you can focus on closing, not chasing. 👉 By purchasing, you get: Full workflow JSON file. Email delivery with setup guidelines. Access to a step-by-step Loom walkthrough video. Contact Us** via services@quantumti.ae. An n8n automation workflow template by Lenouar.

By Ketan Sharma

This n8n template demonstrates a complete AI-driven content pipeline for social media. It automatically generates captions and hashtags for new product images, collects human approval via Telegram, and publishes approved content to Twitter. It’s ideal for marketers, e-commerce businesses, and creators who want to speed up content creation while keeping human oversight. How it works Trigger: The workflow starts when a new file is added to a specific Google Drive folder. File Analysis: The image is processed to extract product information. AI Captioning: Gemini generates a caption and five relevant hashtags based on the product. Telegram Approval: The image, caption, and hashtags are sent to the user for approval. ✅ If approved → The content is posted to Twitter and a confirmation is sent back via Telegram. 🔄 If regenerate → Gemini creates a new caption and hashtags, and the approval loop repeats. ❌ If discard → A message is sent on Telegram and the workflow ends. Requirements Google Drive account Gemini API credentials for captioning and hashtags Telegram bot for approvals Twitter Developer Account with API credentials Customising this workflow Swap Google Drive with Dropbox, Notion, or Airtable as the content source. Extend publishing to LinkedIn, Instagram, or multiple platforms. Add multi-user approval flows in Telegram for team-based decisions. An n8n automation workflow template by Ketan Sharma.

By Rahul Joshi

Description Automatically convert Gmail emails and Slack messages into Zendesk support tickets with intelligent priority detection, comprehensive Google Sheets tracking, and real-time team notifications. Streamlines support workflows with zero manual ticket creation. 🎫📧 What This Template Does Monitors Gmail inbox for unread emails and Slack support channel for new messages. 📥 Normalizes data from both sources with intelligent content processing and HTML cleanup. 🧼 Creates structured Zendesk tickets with proper subject lines, descriptions, and priority tagging. 🎫 Generates comprehensive tracking logs in Google Sheets with clickable ticket URLs. 📊 Sends formatted Slack notifications for successful ticket creation or error alerts. 📢 Key Benefits Eliminates manual ticket creation with automated processing. ⏱️ Unified support workflow across Gmail and Slack channels. 🔄 Complete audit trail with Google Sheets tracking. 🧾 Real-time team notifications with ticket details and direct links. 📲 Intelligent priority detection based on "urgent" keywords. 🚨 Error handling with detailed failure notifications. 🛡️ Features Gmail polling every minute for unread email detection. 📧 Real-time Slack message monitoring in designated support channel. 💬 Smart data normalization with HTML tag removal and urgency detection. 🧠 Automatic Zendesk ticket creation with priority-based tagging. 🏷️ Google Sheets logging with ticket URLs, timestamps, and metadata. 📈 Formatted Slack notifications with emojis and clickable links. ✨ Comprehensive error detection and team alerting system. 🚨 Requirements n8n instance (cloud or self-hosted). Gmail OAuth2 credentials in n8n with inbox access permissions. Slack Bot API credentials with channels:history, chat:write, and webhook capabilities. Zendesk API credentials for ticket creation and management. Google Sheets OAuth2 credentials with spreadsheet write permissions. Designated Slack channel for support requests (e.g., "#post-ticket"). Target Audience Customer support teams automating multi-channel ticket creation. 🎧 Help desk operations seeking unified request processing. 🆘 Small to medium businesses streamlining support workflows. 🏢 IT support teams managing internal and external requests. 💻 Service organizations requiring comprehensive audit trails. 📋 Remote teams needing automated workflow notifications. 🌐 Step-by-Step Setup Instructions Connect Gmail, Slack, Zendesk, and Google Sheets credentials in n8n. 🔑 Configure Slack channel ID for support message monitoring (default: "#post-ticket"). 📱 Set up Google Sheets document for ticket tracking and logging. 📊 Import the workflow and assign all required credentials to respective nodes. 📦 Configure Zendesk subdomain in the "Format Sheet Data" node for proper ticket URLs. 🔗 Test with a sample email or Slack message to validate end-to-end automation. ✅. An n8n automation workflow template by Rahul Joshi.

By Rahul Joshi

Description Automatically detect customer churn risks from Zendesk tickets, log them into Google Sheets for tracking, and send instant Slack alerts to your customer success team. This workflow helps you spot unhappy customers early and take proactive action to reduce churn. 🚨📊💬 What This Template Does Fetches Zendesk tickets daily on schedule (8:00 PM). ⏰ Processes and formats ticket data into clean JSON (priority, age, urgency). 🧠 Identifies churn risks based on negative satisfaction ratings. ⚠️ Logs churn risk tickets into Google Sheets for analysis and reporting. 📈 Sends formatted Slack alerts with ticket details to the CS team channel. 📢 Key Benefits Detects unhappy customers before they churn. 🚨 Centralized churn tracking for reporting and team reviews. 🧾 Proactive alerts to reduce response delays. ⏱️ Clean, structured ticket data for analytics and filtering. 🔄 Strengthens customer success strategy with real-time visibility. 🌐 Features Schedule Trigger – Runs every weekday at 8:00 PM. 🗓️ Zendesk Integration – Fetches all tickets automatically. 🎫 Smart Data Processing – Adds ticket age, urgency, and priority mapping. 🧮 Churn Risk Filter – Flags tickets with negative satisfaction scores. 🚩 Google Sheets Logging – Saves churn risk details with metadata. 📊 Slack Alerts – Sends formatted messages with ID, subject, rating, and action steps. 💬 Requirements n8n instance (cloud or self-hosted). Zendesk API credentials with ticket read access. Google Sheets OAuth2 credentials with write permissions. Slack Bot API credentials with channel posting permissions. Pre-configured Google Sheet for churn risk logging. Target Audience Customer Success teams monitoring churn risk. 👩‍💻 SaaS companies tracking customer health. 🚀 Support managers who want proactive churn alerts. 🛠️ SMBs improving retention through automation. 🏢 Remote CS teams needing instant notifications. 🌐 Step-by-Step Setup Instructions Connect your Zendesk, Google Sheets, and Slack credentials in n8n. 🔑 Update the Schedule Trigger (default: daily at 8:00 PM) if needed. ⏰ Replace the Google Sheet ID with your churn risk tracking sheet. 📊 Confirm the Slack channel ID for alerts (default: zendesk-churn-alerts). 💬 Adjust churn filter logic (default: satisfaction_score = "bad"). 🎯 Run a test to fetch Zendesk tickets and validate Sheets + Slack outputs. ✅. An n8n automation workflow template by Rahul Joshi.

By Satyam Tripathi

Try It Out! This n8n template demonstrates how to build an autonomous AI news agent using Decodo MCP that automatically finds, scrapes, and delivers fresh industry news to your team via Slack. Use cases are many – automated news monitoring for your industry, competitive intelligence gathering, startup monitoring, regulatory updates, research automation, or daily briefings for your organization. How it works Define your news topics using the Set node – AI, MCP, web scraping, whatever matters to your business. The AI Agent processes those topics using the Gemini Chat Model, determining which tools to use and when. Here's where it gets interesting: Decodo MCP gives your AI agent the tools to search Google, scrape websites, and parse content automatically – all while bypassing geo-restrictions and anti-bot measures. The agent hunts for fresh articles from the last 48 hours, extracts clean data, and returns structured JSON results. Format Results cleans up the AI's messy output and removes duplicates. Your polished news digest gets delivered to Slack with clickable links and summaries. How to use Schedule trigger runs daily at 9 AM – adjust timing or swap for webhook triggers as needed. Customize topics in the Set node to match your industry. Scales effortlessly: add more topics, tweak search criteria, done. Requirements Decodo MCP credentials (free trial available) – grab the Smithery connection URL with keys and paste it straight into your n8n MCP node. Done. Gemini API key for the AI processing – drop it into the Google Gemini Chat Model node and pick whichever Gemini model fits your needs. Slack workspace for delivery – n8n's Slack integration docs have you covered. What the final output looks like Here's what your team receives in Slack every morning: Need help? Join the Discord or email support@decodo.com for questions. Happy Automating!. An n8n automation workflow template by Satyam Tripathi.

By Rahul Joshi

Description This workflow automates Zendesk ticket handling with AI-powered auto-replies. It pulls in new support tickets, checks against a Google Sheets FAQ database, and generates accurate responses using GPT-4o-mini. If the question matches an FAQ, the system replies with the predefined answer; otherwise, it drafts a polite, professional custom response. Finally, the workflow formats and sends the reply via Gmail, ensuring customers always receive quick and reliable support. What This Template Does (Step-by-Step) 🎫 Fetch Latest Zendesk Ticket Retrieves and filters tickets, keeping only the most recent one. 📋 Load FAQ Knowledge Base (Google Sheets) Provides predefined answers for common support queries. 🔀 Merge Ticket + FAQs Combines ticket details and FAQ list into one clean dataset. 🧹 Prepare Data for AI Restructures merged data into JSON with two sections: ticket + faqs. 🤖 Generate Support Reply (Azure OpenAI GPT-4o-mini) If ticket matches FAQ → sends exact predefined answer. If no match → crafts a polite AI-generated reply. 📧 Fetch Requester Email (Zendesk) Resolves requester_id into a usable customer email. 🔗 Merge Reply + User Info Joins AI reply with customer’s email into one dataset. 📝 Format for Gmail Creates a ready-to-send JSON: to, subject, body. 📨 Send Auto-Reply (Gmail) Delivers the response directly to the customer’s inbox. Prerequisites Zendesk account & API credentials Google Sheet with FAQ list (questions + answers) n8n instance (cloud or self-hosted) Azure OpenAI API key (GPT-4o-mini) Gmail API credentials (for reply delivery) 1 Step-by-Step Setup Connect Zendesk API → Pull latest tickets. Configure Google Sheets → Load FAQ dataset. Merge both streams (ticket + FAQs) → Prepare JSON. Use LLM (Azure OpenAI GPT-4o-mini) → Match against FAQ or generate AI response. Fetch Requester Email from Zendesk. Merge AI reply + email address. Format structured JSON for Gmail. Send final email via Gmail OAuth2. Customization Ideas ⚡ Add Slack/Teams notification for each reply sent. 📊 Log all ticket + AI replies into Airtable/Notion for tracking. 🎨 Personalize tone of AI responses (friendly, formal, technical). 📂 Add auto-tagging in Zendesk (e.g., “AI handled” vs “FAQ match”). 🔁 Extend workflow to escalate unresolved queries to human agents. Key Benefits ✅ Always-on support replies — no waiting time ✅ Accurate FAQ answers + fallback to AI-generated responses ✅ Seamless Gmail integration for customer communication ✅ Reduces manual ticket load on agents ✅ Fully customizable for tone, logging, and escalation Perfect For 🎯 Customer support teams handling repetitive queries 📈 Growing startups needing scalable support 🤖 Businesses wanting AI + FAQ hybrid support 📩 Any company using Zendesk + Gmail for customer service. An n8n automation workflow template by Rahul Joshi.

By Davide Boizza

This workflow creates a user-friendly web form to upload a file, which allows users to upload a single large file (up to 5Gb) through a custom web form and automatically send it via TransferNow, handling the complex multi-part upload process required for large files. Advantages ✅ No manual steps: The entire process from file upload to email delivery is fully automated. ✅User-friendly: Anyone can upload files via a simple web form, without needing to access TransferNow directly. ✅Supports large files: TransferNow’s API handles large files that are not suitable for email attachments. ✅ Secure file delivery: The workflow uses TransferNow’s secure, expiring download links. ✅Customizable: You can easily adjust the workflow to support multiple file types, multiple recipients, or different validity rules. ✅Scalable: Works for individuals, teams, or businesses that frequently need to share large documents. How It Works The workflow is triggered when a user submits the embedded web form. Here is the process: Form Trigger: A user accesses the form, fills in the required details (Title, Message, Recipient Email), and uploads a single PDF file. Submitting the form starts the workflow. File Processing: The workflow calculates the size of the uploaded file, which is a necessary parameter for the TransferNow API. Transfer Creation: It sends a request to the TransferNow API to create a new file transfer. The API responds with details needed for the upload, including a unique transferId and uploadId. Upload URL Retrieval: The workflow requests a pre-signed upload URL from TransferNow for the specific part of the file. File Upload: The binary file data from the form and the upload URL from the previous step are merged. The workflow then performs a direct PUT request to the secured TransferNow URL to upload the file's binary content. Upload Confirmation: After the upload, the workflow informs the TransferNow API that the file part upload is complete. Finalization: Once the entire upload is confirmed, the workflow finalizes the transfer on TransferNow's side. Data Retrieval & Response: The workflow fetches the final transfer data, constructs a public download URL, and sends a success message back to the user's browser, displaying the recipient's email and the download link. Set Up Steps To use this workflow, you need to configure the connection to the TransferNow API. Get TransferNow API Credentials: Create a free account on TransferNow developer portal to get your API key (a 14-day free trial is available). Configure Credentials in n8n: In the n8n editor, locate the HTTP Request nodes named "Set Transfer", "Get Upload Url", etc. These nodes use a credential called "Header Auth TransferNow". You need to create this credential. Go to Credentials > Add Credential and select "HTTP Header Auth". Give it a name (e.g., "TransferNow API Key"). In the Name field, enter x-api-key. In the Value field, paste your personal TransferNow API key. Save the credential. The existing nodes will automatically use it, or you can select it from the dropdown in each node's credentials section. Activate the Workflow: Save the workflow and click the Activate toggle to make it live. Once activated, the On form submission node will provide a unique public URL for your form. Share this URL with users to start uploading and sending files. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Gabriel Santos

This workflow streamlines how employees request equipment/items and how those requests reach the Procurement team. It validates the employee by enrollment number, detects whether a manager exists, and then either requests approval (if the requester has a manager) or routes the request directly to Procurement (if the requester is a manager). All messages are written in a professional tone using an LLM, and emails are sent via Gmail with a built-in approve/deny step for managers. Who’s it for HR/IT/Operations teams that handle equipment requests, need a lightweight approval flow, and want clean, professional emails without manual drafting. How it works Employee submits their enrollment number. Workflow fetches employee (and manager, if any). Employee describes the requested item(s). If a manager exists → an approval email (double opt-in) is sent to the manager. Approved → notify employee and forward a polished request to Procurement. Denied → notify employee. If the requester is a manager → skip approval and send directly to Procurement. End pages confirm the outcome. Requirements MySQL (or compatible DB) with an employees table (id, name, email, enrollment_number, manager). Gmail credentials (OAuth) in n8n. LLM provider (OpenAI or compatible) for message polishing. How to customize Replace the Procurement NoOp nodes with your email, helpdesk, or ERP integration. Adjust email copy and tone in the LLM prompt nodes. Add tracking IDs, SLA text, or CCs for auditing. Style the forms with your brand (CSS blocks provided). An n8n automation workflow template by Gabriel Santos.

By Rahul Joshi

Description Automate Zendesk ticket follow-up management by fetching pending tickets daily, enriching and logging them into Google Sheets, creating ClickUp tasks for team reminders, and sending professional follow-up emails to customers. Keeps your support pipeline clean and ensures no pending tickets fall through the cracks. 🎫📊📧✅ What This Template Does Triggers daily (Mon–Fri at 8 PM) to check Zendesk for pending tickets. ⏰ Filters only "pending" status tickets to reduce noise. 🔍 Formats ticket data with priority, age, and attention flags. 🧠 Logs all tickets into Google Sheets for reporting and analytics. 📊 Creates ClickUp tasks for team follow-up and accountability. 📋 Generates professional HTML follow-up emails grouped by customer. 🎨 Sends emails via Gmail with ticket details and next steps. 📧 Key Benefits Ensures no pending Zendesk tickets are forgotten. ⏱️ Builds a historical log for analytics and audit trails. 🧾 Keeps your support team accountable with ClickUp tasks. ✅ Delivers personalized, branded follow-up emails to customers. 💡 Reduces manual effort in tracking and responding to tickets. 🔄 Features Schedule Trigger – Runs Mon–Fri at 8:00 PM. 🗓️ Zendesk Integration – Fetches pending tickets automatically. 🎫 Smart Data Processing – Cleans descriptions, calculates age, flags urgent tickets. ⚡ Google Sheets Logging – Maintains a structured log with Ticket ID, URL, tags, status, etc. 📈 ClickUp Tasks – Automatically creates tasks per pending ticket. 📋 Email Generation – Groups tickets per customer, builds professional HTML follow-ups. 🎨 Gmail Delivery – Sends personalized follow-ups directly to customers. 📧 Requirements n8n instance (cloud or self-hosted). Zendesk API credentials with read access. Google Sheets OAuth2 credentials with write access. ClickUp API credentials for task creation. Gmail OAuth2 credentials for sending emails. Pre-configured Google Sheet for pending ticket tracking. Target Audience Customer support teams managing Zendesk tickets. 🎧 SaaS companies wanting automated follow-ups. 🚀 CS managers ensuring accountability in ticket handling. 🛠️ SMBs reducing customer wait time with proactive follow-ups. 🏢 Remote support teams needing automated reminders and logs. 🌐 Step-by-Step Setup Instructions Connect Zendesk, Google Sheets, ClickUp, and Gmail credentials in n8n. 🔑 Update the schedule trigger (default: Mon–Fri at 8:00 PM). ⏰ Replace the Google Sheet ID with your pending ticket log sheet. 📊 Configure your ClickUp space/list IDs for task creation. 📋 Update email branding and sender address in the email generator. 🎨 Test with sample tickets to validate Sheets logging, ClickUp tasks, and Gmail delivery. ✅. An n8n automation workflow template by Rahul Joshi.

By Amit Mehta

This workflow performs structured data extraction and data mining from a web page by combining the capabilities of Bright Data and Google Gemini. How it Works This workflow focuses on extracting structured data from a web page using Bright Data's Web Unlocker Product. It then uses n8n's AI capabilities, specifically Google Gemini Flash Exp, for information extraction and custom sentiment analysis. The results are sent to webhooks and saved as local files. Use Cases Data Mining**: Automating the process of extracting and analyzing data from websites. Web Scraping**: Gathering structured data for market research, competitive analysis, or content aggregation. Sentiment Analysis**: Performing custom sentiment analysis on unstructured text. Setup Instructions Bright Data Credentials: You need to have an account and a Web Unlocker zone with Bright Data. Update the Header Auth account credentials in the Perform Bright Data Web Request node. Google Gemini Credentials: Provide your Google Gemini(PaLM) Api account credentials for the AI-related nodes. Configure URL and Zone: In the Set URL and Bright Data Zone node, set the web URL you want to scrape and your Bright Data zone. Update Webhook: Update the Webhook Notification URL in the relevant HTTP Request nodes. Workflow Logic Trigger: The workflow is triggered manually. Set Parameters: It sets the target URL and the Bright Data zone. Web Request: The workflow performs a web request to the specified URL using Bright Data's Web Unlocker. The output is formatted as markdown. Data Extraction & Analysis: The markdown content is then processed by multiple AI nodes to: Extract textual data from the markdown. Perform topic analysis with a structured response. Analyze trends by location and category with a structured response. Output: The extracted data and analysis are sent to webhooks and saved as JSON files on disk. Node Descriptions | Node Name | Description | |-----------|-------------| | When clicking 'Test workflow' | A manual trigger node to start the workflow. | | Set URL and Bright Data Zone | A Set node to define the URL to be scraped and the Bright Data zone to be used. | | Perform Bright Data Web Request | An httpRequest node that performs the web request to Bright Data's API to retrieve the content. | | Markdown to Textual Data Extractor | An AI node that uses Google Gemini to convert markdown content into plain text. | | Google Gemini Chat Model | A node representing the Google Gemini model used for the data extraction. | | Topic Extractor with the structured response | An AI node that performs topic analysis and outputs the results in a structured JSON format. | | Trends by location and category with the structured response | An AI node that analyzes and clusters emerging trends by location and category, outputting a structured JSON. | | Initiate a Webhook Notification... | These nodes send the output of the AI analysis to a webhook. | | Create a binary file... | Function nodes that convert the JSON output into binary format for writing to a file. | | Write the topics/trends file to disk | readWriteFile nodes that save the binary data to a local file (d:\topics.json and d:\trends.json). | Customization Tips Change the web URL in the Set URL and Bright Data Zone node to scrape different websites. Modify the AI prompts in the AI nodes to customize the analysis (e.g., change the sentiment analysis criteria). Adjust the output path in the readWriteFile nodes to save the files to a different location. Suggested Sticky Notes for Workflow Note**: "This workflow deals with the structured data extraction by utilizing Bright Data Web Unlocker Product... Please make sure to set the web URL of your interest within the 'Set URL and Bright Data Zone' node and update the Webhook Notification URL". LLM Usages**: "Google Gemini Flash Exp model is being used... Information Extraction is being used for the handling the custom sentiment analysis with the structured response". Required Files 1GOrjyc9mtZCMvCr_Structured_Data_Extract,Data_Mining_with_Bright_Data&_Google_Gemini.json: The main n8n workflow export for this automation. Testing Tips Run the workflow and check the webhook to verify that the extracted data is being sent correctly. Confirm that the d:\topics.json and d:\trends.json files are created on your disk with the expected structured data. Suggested Tags & Categories Engineering AI. An n8n automation workflow template by Amit Mehta.

By Gloria

Premium n8n Workflow: DataForSEO + Airtable Keyword Research This premium n8n workflow harnesses the power of DataForSEO's API combined with Airtable's relational database capabilities to transform your keyword research process, providing deeper insights for content creation without the hefty price tag of traditional SEO tools. 🚀 Features 🔍 Comprehensive Data Extracts related keywords, search volume 📈, keyword difficulty 📊, search intent 🤔, and more directly from DataForSEO's powerful API 🚀. 💰 Cost-Effective Leverages DataForSEO's pay-as-you-go model 💸, making it budget-friendly. 🏗️ Airtable Integration Organizes your data in a powerful relational database for advanced filtering, sorting, and visualization capabilities. 🔄 Cross-Reference Capabilities Create relationships between keyword sets to identify content opportunities traditional tools miss. 🤖 Fully Automated Set up once and run keyword research with a single click. ⚙️ Efficient & Scalable Handles large keyword lists with Airtable's robust data management system. 👥 This Workflow is Perfect For: Content creators 📝 Bloggers 💻 YouTubers 🎥 Small business owners 💼 Digital marketers 📊 SEO professionals 🔍 Entrepreneurs 🚀 E-Commerce website owners 💻 Stop overspending on expensive SEO tools and start generating actionable keyword insights with a professional-grade database. 📝 What's Included? ⚙️ n8n Workflow Template Ready-to-use workflow with pre-configured DataForSEO API endpoints for comprehensive keyword data collection. 📊 Airtable Database Structure Pre-built tables and fields specifically designed for SEO keyword analysis. 🔌 DataForSEO Integration Complete setup for pulling multiple data types (related keywords, suggestions, people also ask, subtopics) from DataForSEO's API. 🔄 Automated Data Processing Logic to clean, format, and structure raw API data into usable insights. 📋 Documentation Step-by-step instructions for connecting your DataForSEO account and configuring the workflow. 🏆 Why Choose the Airtable Version? 📱 Access Anywhere: Review your keyword research on any device through Airtable's apps. 🤝 Team Collaboration: Share your keyword database for collaborative planning. 🔄 Data Relationships: Connect keywords, content ideas, and publishing schedules in one place. 🔌 Extensibility: Integrate with other tools via Airtable's ecosystem. 🎯 Content Planning: Use Airtable as a complete content management system, from research to publication tracking. 🛠️ How It Works 1️⃣ Import the provided n8n workflow into your n8n instance 📥. 2️⃣ Configure your DataForSEO API credentials and Airtable connections ⚙️. 3️⃣ Input your target keywords and desired parameters 📝. 4️⃣ Trigger the workflow — n8n automatically gathers and organizes your keyword research in Airtable 🤖. 5️⃣ Use Airtable’s interface to analyze relationships, identify opportunities, and plan your strategy 📊. Additional detailed instructions are provided in the workflow. 🏁 What You Need to Get Started 🔹 Access to n8n (self-hosted or cloud) ☁️ 🔹 A DataForSEO account with API credentials 🔑 🔹 An Airtable account (free tier works, Pro recommended for advanced features) 📊 🔹 Basic understanding of API usage and n8n workflows 🧠 💡 You can also connect this workflow with my SEO-Based Keyword Categorization & Clustering Strategy Workflow with Airtable and my Multi-Agent SEO Optimized Blog Writing System with Hyperlinks for E-Commerce, both available on my profile, to build a fully automated, end-to-end SEO content machine. An n8n automation workflow template by Gloria.

By Automate With Marc

🤖 Telegram Image Editor with Nano Banana Send an image to your Telegram bot, and this workflow will automatically enhance it with Google’s Nano Banana (via Wavespeed API), then return the polished version back to the same chat—seamlessly. 👉 Watch step-by-step video tutorials of workflows like these on www.youtube.com/@automatewithmarc What it does Listens on Telegram for incoming photo messages Downloads the file sent by the user Uploads it to Google Drive (temporary storage for processing) Sends the image to Nano Banana API with a real-estate style cleanup + enhancement prompt Polls until the job is complete (handles async processing) Returns the edited image back to the same Telegram chat Perfect for Real-estate agents previewing polished property photos instantly Social media managers editing on-the-fly from Telegram Anyone who wants “send → cleaned → returned” image flow without manual edits Apps & Services Telegram Bot API (Trigger + Send/Receive files) Google Drive (Temporary file storage) Wavespeed / Google Nano Banana (AI-powered image editing) Setup Connect your Telegram Bot API token in n8n. Add your Wavespeed API key for Nano Banana. Link your Google Drive account (temporary storage). Deploy the workflow and send a test photo to your Telegram bot. Customization Adjust the Nano Banana prompt for different styles (e.g., ecommerce cleanup, portrait retouching, color correction). Replace Google Drive with another storage service if preferred. Add logging to Google Sheets or Airtable to track edits. An n8n automation workflow template by Automate With Marc.

By Br1

Load Jira open issues with comments into Pinecone + RAG Agent (Direct Tool or MCP) Who’s it for This workflow is designed for support teams, data engineers, and AI developers who want to centralize Jira issue data into a vector database. It collects open issues and their associated comments, converts them into embeddings, and loads them into Pinecone for semantic search, retrieval-augmented generation (RAG), or AI-powered support bots. It’s also published as an MCP tool, so external applications can query the indexed issues directly. How it works The workflow automates Jira issue extraction, comment processing, and vector storage in Pinecone. Importantly, the Pinecone index is recreated at every run so that it always reflects the current set of unresolved tickets. Trigger – A schedule trigger runs the workflow at defined times (e.g., 8, 11, 14, and 17 on weekdays). Issue extraction with pagination – Calls the Jira REST API to fetch open issues matching a JQL query (unresolved cases created in the last year). Pagination is fully handled: issues are retrieved in batches of 25, and the workflow continues iterating until all open issues are loaded. Data transformation – Extracts key fields (issue ID, key, summary, description, product, customer, classification, status, registration date). Comments integration – Fetches all comments for each issue, filters out empty/irrelevant ones (images, dots, empty markdown), and merges them with the issue data. Text cleaning – Converts HTML descriptions into clean plain text for processing. Embedding generation – Uses the OpenAI Embeddings node to vectorize text. Vector storage with index recreation – Loads embeddings and metadata into Pinecone under the jira namespace and the openissues index. The namespace is cleared at every run to ensure the index contains only unresolved tickets. Document chunking – Splits long issue texts into smaller chunks (512 tokens, 50 overlap) for better embedding quality. MCP publishing – Exposes the Pinecone index as an MCP tool (openissues), enabling external systems to query Jira issues semantically. How to set up Jira – Configure a Jira account and generate a token. Update the Jira node with credentials and adjust the JQL query if needed. OpenAI – Set up an OpenAI API key for embeddings. Configure embedding dimensions (default: 512). Pinecone – Create an index (e.g., openissues) with matching dimensions (512). Configure Pinecone API credentials and namespace (jira). The index will be cleared automatically at every run before reloading unresolved issues. Schedule – Adjust the cron expression in the Schedule Trigger to fit your update frequency. Optional MCP – If you want to query Jira issues via MCP, configure the MCP trigger and tool nodes. Requirements Jira account with API access and permissions to read issues and comments. OpenAI API key with access to the embedding model. Pinecone account with an index created (dimensions = 512). n8n instance with credentials set up for Jira, OpenAI, and Pinecone. How to customize the workflow JQL query**: Modify it to control which issues are extracted (e.g., by project, type, or time window). Pagination size**: Adjust the maxResults parameter (default 25) if you want larger or smaller batches per iteration. Metadata fields**: Add or remove fields in the “Extract Relevant Info” code node. Chunk size**: Adjust chunk size/overlap in the Document Chunker for different embedding strategies. Embedding model**: Switch to a different embedding provider if preferred. Vector store**: Replace Pinecone with another supported vector database if needed. Downstream use**: Extend with notifications, dashboards, or AI assistants that consume the vector data. AI Chatbot for Jira open tickets with SLA insights Who’s it for This workflow is designed for commercial teams, customer support, and service managers who need quick, conversational access to unresolved Jira tickets. It enables them to check whether a client has open issues, see related details, and understand SLA implications without manually browsing Jira. How it works Chat interface** – Provides a web-based chat that team members can use to ask natural language questions such as: “Are there any issues from client ACME?” “Do we have tickets that have been open for a long time?” AI Agent** – Powered by OpenAI, it interprets questions and queries the Pinecone vector store (openissues index, jira namespace). Memory** – Maintains short-term chat history for more natural conversations. Ticket retrieval** – Uses Pinecone embeddings (dimension = 512) to fetch unresolved tickets enriched with metadata: Issue key, description, customer, product, severity color, status, AM contract type, and SLA. SLA integration** – Service levels (Basic, Advanced, Full Service, with optional Fast Support) are provided via the SLA node. The agent explains which SLA applies based on ticket severity, registration date, and contract type. AI response** – Returns a friendly, collaborative summary of all tickets found, including: Ticket identifier Description Customer and product Severity level (Red, Yellow, Green, White) Ticket status Contract level and SLA explanation Setup Configure Jira → Pinecone index (openissues, 512 dimensions) already populated with unresolved tickets. Provide OpenAI API credentials. Ensure the SLA node includes the correct service-level definitions. Adjust chat branding (title, subtitle, CSS) if desired. Requirements Jira account with API access. Pinecone account with an index (openissues, dimensions = 512). OpenAI API key. n8n instance with LangChain and chatTrigger nodes enabled. How to customize Change the SLA node text if your service levels differ. Adjust the chat interface design (colors, title, subtitle). Expand metadata in Pinecone (e.g., add project type, priority, or assigned team). Train with additional examples in the system message to refine AI behavior. An n8n automation workflow template by Br1.

By Alejandro Scuncia

An extendable triage workflow that classifies severity, sets components, and posts actionable guidance for support engineers using n8n + Gemini + Cache Augmented Generation (CAG). Designed for Jira Service Management, but easily adaptable to Zendesk, Freshdesk, or ServiceNow. Description Support teams loose valuable time when tickets are misclassified: wrong severity, missing components, unclear scope. Engineers end up re-routing issues and chasing missing info instead of solving real problems. This workflow automates triage by combining domain rules with AI-driven classification and guidance, so engineers receive better-prepared tickets. It includes: ✅ Real-time ticket capture via webhook ✅ AI triage for severity and component ✅ CAG-powered guidance: 3 next steps + missing info ✅ Internal audit comment with justifications & confidence ✅ Structured metrics for reporting ⚙️ How It Works This workflow runs in 4 stages: 📥 Entry & Setup Webhook triggers on ticket creation Loads domain rules (priority policy, components, guidance templates) Sets confidence threshold & triage label 🧠 AI Analysis (Gemini + CAG) Builds structured payload with ticket + domain context Gemini proposes severity, component, guidance, missing info Output normalized for safe automation (valid JSON, conservative confidence) 🤖 Update & Audit Updates fields (priority, component, labels) if confidence ≥ threshold Posts internal audit comment with: 3 next steps Missing info to request Justifications + confidence 📊 Metrics Captures applied changes, confidence scores, and API statuses Enables reliability tracking & continuous improvement 🌟 Key Features CAG-powered guidance** → lightning-fast, context-rich next steps Explainable automation** → transparent audit comments for every decision Domain-driven rules** → adaptable to any product or support domain Portable* → swap JSM with *Zendesk, Freshdesk, ServiceNow** via HTTP nodes 🔐 Required Credentials | Tool | Use | |------|-----| | Jira Service Management | Ticketing system (API + comments) | | Google Gemini/Gemma | LLM analysis | | HTTP Basic Auth | For Jira API requests (bot user) | ⚠️ Setup tip: create a dedicated bot user in Jira Service Management with an API token. This ensures clean audit logs, proper permissions, and avoids mixing automation with human accounts. 🧰 Customization Tips Replace https://your-jsm-url/... with your own Jira Service Management domain. Update the credentials with the bot user’s API token created above. Swap Jira Service Management nodes with other ticketing systems like Zendesk, Freshdesk, or ServiceNow. Extend the domain schema (keywords, guidance_addons) to fit your product or support environment. 🗂️ Domain Schema This workflow uses a domain-driven schema to guide triage. It defines: Components** → valid areas for classification Priority policies & rules** → how severity is determined Keywords** → domain-specific signals (e.g., “API error”, “all users affected”) Guidance addons** → contextual next steps for engineers No-workaround phrases** → escalate severity if present ✨ The full domain JSON (with complete keyword & guidance mapping) is included as a sticky note inside the workflow. 💡 Use Cases Automated triage for IT & support tickets Incident classification with outage/security detection Contextual guidance for engineers in customer support Faster escalation and routing of critical issues 🧠 Who It’s For Support teams running Jira Service Management Platform teams automating internal ticket ops AI consultants prototyping practical triage workflows Builders exploring CAG today, RAG tomorrow 🚀 Try It Out! ⚙️ Import the Workflow in n8n (cloud or self-hosted). 🔑 Add Credentials (JSM API + Gemini key). ⚡ Configure Setup (confidence threshold, triage label, domain rules). 🔗 Connect Webhook in JSM → issue_created → n8n webhook URL. 🧪 Test with a Ticket → see auto-updates + AI audit comment. 🔄 Swap the Ticketing System → adapt HTTP nodes for Zendesk, Freshdesk, or ServiceNow. 💬 Have Feedback or Ideas? I’d Love to Hear This project is open, modular, and evolving. If you try it, adapt it, or extend it, I’d love to hear your feedback — let’s improve it together in the n8n builder community. 📧 ascuncia.es@gmail.com 🔗Linkedin. An n8n automation workflow template by Alejandro Scuncia.

By Avkash Kakdiya

How it works This workflow automatically captures website visitors using Albacross, enriches their data with Datagma, and syncs it into HubSpot. Once leads are created or updated, a personalized email is generated and sent through Gmail. All email activities are logged in HubSpot for proper sales tracking and follow-up. Step-by-step 1. Trigger the workflow Schedule Trigger** – Runs the workflow at set intervals (hourly, daily, or custom). 2. Capture website visitors Albacross Website Visitor** – Pulls company and visitor details from website activity. 3. Enrich lead data Enrich Lead Data** – Enhances visitor records with personal and professional details via Datagma. 4. Sync to CRM Create/Update HubSpot Contact** – Creates or updates contact records in HubSpot with enriched lead data. 5. Generate personalized outreach Generate Personalized Message** – Builds a tailored email including company, industry, and value propositions. 6. Send and track emails Send Personalized Email** – Sends the outreach message through Gmail. Log Email Activity in HubSpot** – Tracks email engagement automatically in HubSpot. Why use this? Capture and identify anonymous website visitors as potential leads. Enrich contact details with accurate, professional information. Keep HubSpot updated automatically without manual data entry. Send highly personalized outreach emails tailored to each lead. Log all communication for better pipeline visibility and sales follow-up. An n8n automation workflow template by Avkash Kakdiya.

By Amit Mehta

N8N Workflow: Send and Check TTS (Text-to-speech) Voice Calls with Email Verification This workflow automates a two-factor verification process using a voice call and an email. It is designed to send a text-to-speech (TTS) voice call with a verification code and, upon successful voice verification, to send an email with a second verification code. How it Works This workflow automates the process of sending voice calls for verification and combines it with email verification. It uses the ClickSend API for the voice call and an SMTP integration for sending the email. Use Cases Two-factor authentication (2FA) for user registration or login. Automated verification for phone numbers and email addresses. Building a custom verification system for web applications. Setup Instructions ClickSend API: Register on ClickSend and obtain your API Key. In the Send Voice node, create a Basic Auth credential using your ClickSend username and API Key as the password. SMTP Credentials: In the Send Email node, you must set up your SMTP credentials for the sender's email. Workflow Logic Trigger: The workflow is started by submitting a form. Set Voice Code: The workflow sets a predefined voice verification code. Send Voice Call: A voice call is made to the provided phone number using the ClickSend API, where a synthesized voice reads the code. Verify Voice Code: A form appears to prompt the user to enter the voice code they received. Conditional Check: An If node checks if the entered voice code is correct. Set Email Code & Send Email: If the voice code is correct, a second code is set, and an email is sent to the user with that code. Verify Email Code: The user is then prompted to enter the code from the email. Final Check: A final If node verifies the email code. The workflow either leads to a Success message or a Fail email code message. Node Descriptions | Node Name | Description | |-----------|-------------| | On form submission | This trigger node presents a form to the user to collect their phone number, desired voice, language, email, and name. | | Set voice code | A Set node that defines the verification code for the voice call. | | Code for voice | A Code node that adds spaces between the digits of the voice code to make it sound clearer during the call. | | Send Voice | This httpRequest node sends a POST request to the ClickSend API to initiate the TTS voice call. | | Verify voice code | A form node that prompts the user to enter the code they received via the voice call. | | Is voice code correct? | An If node that checks if the code entered by the user matches the predefined voice code. | | Set email code | A Set node that defines the verification code for the email. | | Send Email | This node uses an SMTP credential to send an email to the user with their verification code. | | Verify email code | A form node that prompts the user to enter the code they received via email. | | Is email code correct? | An If node that checks if the code entered by the user matches the predefined email code. | | Success | A form node that displays a success message upon completion of both verifications. | | Fail voice code | A form node that displays a failure message if the voice code is incorrect. | | Fail email code | A form node that displays a failure message if the email code is incorrect. | Customization Tips You can change the verification codes by modifying the values in the Set voice code and Set email code nodes. The form can be customized to change the fields, labels, and dropdown options for voice and language. The email content and subject can be customized in the Send Email node. Suggested Sticky Notes for Workflow STEP 1**: "Register here to ClickSend and obtain your API Key... In the node 'Send Voice' create a 'Basic Auth' with the username you registered and the API Key provided as your password". STEP 2**: "Set the verification code for this explanatory flow... In the node 'Send Email' set the sender". STEP 3**: "Submit the form and you will receive a call to the phone number you entered where the selected voice will tell you the content of the text you wrote". Set voice code**: "Set the code that will be spoken in the verification phone call". Set email code**: "Set the code that will be sent in the verification email". Required Files 1g8EAij2RwhNN70t_xSend_and_check_TTS_(Text-to-speech)_voice_calls_end_email_verification.json: The n8n workflow export file for this automation. Testing Tips Run the workflow and submit the form with your phone number and email. Check your phone for the voice call and listen for the code. Enter the correct voice code in the next form and submit. Check your email for the second verification code. Enter the correct email code to test the success path, or an incorrect one to test the failure path. Suggested Tags & Categories #Verification #Voice #Email #API #Authentication. An n8n automation workflow template by Amit Mehta.

By Shohani

Auto-publish Telegram channel posts to WooCommerce store This n8n template automatically converts Telegram channel posts into WooCommerce products, perfect for businesses that share products on Telegram and want to sync them with their online shop. Who's it for E-commerce businesses, dropshippers, and retailers who: Use Telegram channels to showcase products Want to automatically sync products to their WooCommerce store Need to reduce manual data entry between platforms Handle multiple product images and want them properly organized How it works The workflow monitors your Telegram channel for new posts and automatically creates corresponding WooCommerce products: Telegram Trigger detects new channel posts with photos and captions Text Processing extracts product details from the post: First line becomes the product title First hashtag determines the product category Price is extracted using regex patterns Channel signature is removed from description Image Handling downloads and uploads images to WordPress media library Category Matching fetches WooCommerce categories and matches them with hashtags Product Creation creates the WooCommerce product with all extracted data Multi-Image Support handles posts with multiple images by updating the product How to set up Telegram Setup: Create a Telegram bot and get the API token Add the bot to your channel as an administrator Configure the Telegram Trigger with your bot credentials WooCommerce Setup: Enable WooCommerce REST API in your WordPress admin Create API keys with read/write permissions Configure the WooCommerce nodes with your API credentials WordPress Setup: Configure HTTP Basic Auth for WordPress REST API Update the woocommerce_url in the SetFields node with your domain Channel Post Format: First line: Product title Include at least one photo Add price in format: 9,500,000 or 9.500.000 Use hashtags that match your WooCommerce category names End posts with your signature after the divider character Requirements Active Telegram bot with channel admin access WooCommerce store with REST API enabled WordPress with media upload permissions How to customize the workflow Price Format: Modify the regex patterns in the Code node to match your currency format Category Mapping: Ensure your Telegram hashtags exactly match your WooCommerce category names Signature Divider: Change the signature divider character in SetFields node (default: "_") Image Quality: Adjust the Telegram file download to get different image resolutions Product Status: Modify the product creation node to set products as draft instead of published. An n8n automation workflow template by Shohani.

By Davide Boizza

This workflow automates the process of creating short videos from multiple image references (up to 7 images). It uses "Vidu Reference to Video" model, a video generation API to transform a user-provided prompt and image set into a consistent, AI-generated video. This workflow automates the process of generating AI-powered videos from a set of reference images and then uploading them to TikTok and Youtube. The process is initiated via a user-friendly web form. Advantages ✅ Consistent Video Creation: Uses multiple reference images to maintain subject consistency across frames. ✅ Easy Input: Just a simple form with prompt + image URLs. ✅ Automation: No manual waiting—workflow checks status until video is ready. ✅ SEO Optimization: Automatically generates a catchy, optimized YouTube title using AI. ✅ Multi-Platform Publishing: Uploads directly to Google Drive, YouTube, and TikTok in one flow. ✅ Time Saving: Removes repetitive tasks of video generation, download, and manual uploading. ✅ Scalable: Can run periodically or on-demand, perfect for content creators and marketing teams. ✅ UGC & Social Media Ready: Designed for creating viral short videos optimized for platforms like TikTok and YouTube Shorts. How It Works Form Trigger: A user submits a web form with two key pieces of information: a text Prompt describing the desired video and a list of Reference images (URLs separated by commas or new lines). Data Processing: The workflow processes the submitted image URLs, converting them from a text string into a proper array format for the AI API. AI Video Generation: The processed data (prompt and image array) is sent to the Fal.ai VIDU API endpoint (reference-to-video) to start the video generation job. This node returns a request_id. Status Polling: The workflow enters a loop where it periodically checks the status of the generation job using the request_id. It waits for 60 seconds and then checks if the status is "COMPLETED". If not, it waits and checks again. Result Retrieval: Once the video is ready, the workflow fetches the URL of the generated video file. Title Generation: Simultaneously, the original user prompt is sent to an AI model (GPT-4o-mini via OpenRouter) to generate an optimized, engaging title for the social media post. Upload & Distribution: The video file is downloaded from the generated URL. A copy is saved to a specified Google Drive folder for storage. The video, along with the AI-generated title, is automatically uploaded to YouTube and TikTok via the Upload-Post.com API service. Set Up Steps This workflow requires configuration and API keys from three external services to function correctly. Step 1: Configure Fal.ai for Video Generation Create an account and obtain your API key. In the "Create Video" HTTP node, edit the "Header Auth" credentials. Set the following values: Name: Authorization Value: Key YOUR_FAL_API_KEY (replace YOUR_FAL_API_KEY with your actual key) Step 2: Configure Upload-Post.com for Social Media Uploads Get an API key from your Upload-Post Manage Api Keys dashboard (10 free uploads per month). In both the "HTTP Request" (YouTube) and "Upload on TikTok" nodes, edit their "Header Auth" credentials. Set the following values: Name: Authorization Value: Apikey YOUR_UPLOAD_POST_API_KEY (replace YOUR_UPLOAD_POST_API_KEY with your actual key) Crucial: In the body parameters of both upload nodes, find the user field and replace YOUR_USERNAME with the exact name of the social media profile you configured on Upload-Post.com (e.g., my_youtube_channel). Step 3: Configure Google Drive (Optional Storage) The "Upload Video" node is pre-configured to save the video to a Google Drive folder named "Fal.run". Ensure your Google Drive credentials in n8n are valid and that you have access to this folder, or change the folderId parameter to your desired destination. Step 4: Configure AI for Title Generation The "Generate title" node uses OpenAI to access the gpt-5-mini model.. Need help customizing? Contact me for consulting and support or add me on Linkedin. An n8n automation workflow template by Davide Boizza.

By Mariela Slavenova

This template crawls a website from its sitemap, deduplicates URLs in Supabase, scrapes pages with Crawl4AI, cleans and validates the text, then stores content + metadata in a Supabase vector store using OpenAI embeddings. It’s a reliable, repeatable pipeline for building searchable knowledge bases, SEO research corpora, and RAG datasets. ⸻ Good to know • Built-in de-duplication via a scrape_queue table (status: pending/completed/error). • Resilient flow: waits, retries, and marks failed tasks. • Costs depend on Crawl4AI usage and OpenAI embeddings. • Replace any placeholders (API keys, tokens, URLs) before running. • Respect website robots/ToS and applicable data laws when scraping. How it works Sitemap fetch & parse — Load sitemap.xml, extract all URLs. De-dupe — Normalize URLs, check Supabase scrape_queue; insert only new ones. Scrape — Send URLs to Crawl4AI; poll task status until completed. Clean & score — Remove boilerplate/markup, detect content type, compute quality metrics, extract metadata (title, domain, language, length). Chunk & embed — Split text, create OpenAI embeddings. Store — Upsert into Supabase vector store (documents) with metadata; update job status. Requirements • Supabase (Postgres + Vector extension enabled) • Crawl4AI API key (or header auth) • OpenAI API key (for embeddings) • n8n credentials set for HTTP, Postgres/Supabase How to use Configure credentials (Supabase/Postgres, Crawl4AI, OpenAI). (Optional) Run the provided SQL to create scrape_queue and documents. Set your sitemap URL in the HTTP Request node. Execute the workflow (manual trigger) and monitor Supabase statuses. Query your documents table or vector store from your app/RAG stack. Potential Use Cases This automation is ideal for: Market research teams collecting competitive data Content creators monitoring web trends SEO specialists tracking website content updates Analysts gathering structured data for insights Anyone needing reliable, structured web content for analysis Need help customizing? Contact me for consulting and support: LinkedIn. An n8n automation workflow template by Mariela Slavenova.

By Avkash Kakdiya

How it works This workflow automates the transfer of files from an FTP server to Google Drive. It runs on a schedule, lists files in a defined FTP directory, and processes them in batches. Each file is downloaded sequentially from the FTP server and uploaded to Google Drive. The workflow ensures filenames are preserved for consistency during the sync process. Step-by-step 1. Trigger the workflow Schedule Trigger** – Starts the workflow automatically at set intervals. 2. List files from FTP FTP (List Files)** – Retrieves a list of files from the FTP server path. 3. Batch process files Split in Batches** – Breaks the file list into smaller chunks for sequential handling. 4. Download file from FTP FTP (Download File)** – Downloads each file from the FTP server. 5. Upload to Google Drive Google Drive (Upload File)** – Uploads the file to Google Drive while keeping its original filename. Why use this? Automates repetitive FTP-to-cloud transfer tasks with no manual intervention. Reduces system overload by processing files in manageable batches. Ensures data backup from FTP servers directly into cloud storage. Maintains file structure and filenames for easy reference and retrieval. Provides reliable, scheduled synchronization between FTP and Google Drive. An n8n automation workflow template by Avkash Kakdiya.

By Avkash Kakdiya

How it works This workflow synchronizes support tickets in Freshdesk with issues in Linear, enabling smooth collaboration between support and development teams. It triggers on new or updated Freshdesk tickets, maps fields to Linear’s format, and creates linked issues through Linear’s API. Reverse synchronization is also supported, so changes in Linear update the corresponding Freshdesk tickets. Comprehensive logging ensures success and error events are always tracked. Step-by-step 1. Trigger the workflow New Ticket Webhook** – Captures new Freshdesk tickets for issue creation. Update Ticket Webhook** – Detects changes in existing tickets. Linear Issue Updated Webhook** – Listens for updates from Linear. 2. Transform and map data Map Freshdesk Fields to Linear** – Converts priority, status, title, and description for Linear. Map Linear to Freshdesk Fields** – Converts Linear state, priority, and extracts ticket ID for Freshdesk updates. 3. Perform API operations Create Linear Issue** – Sends GraphQL mutation to Linear API. Check Linear Creation Success** – Validates issue creation before linking. Link Freshdesk with Linear ID** – Updates Freshdesk with Linear reference. Update Freshdesk Ticket** – Pushes Linear updates back to Freshdesk. 4. Manage logging and errors Log Linear Creation Success** – Records successful ticket-to-issue sync. Log Linear Creation Error** – Captures and logs issue creation failures. Log Freshdesk Update Success** – Confirms successful reverse sync. Log Missing Ticket ID Error** – Handles missing ticket reference errors. Why use this? Keep support and development teams aligned with real-time updates. Eliminate manual ticket-to-issue handoffs, saving time and reducing errors. Maintain full visibility with detailed success and error logs. Enable bidirectional sync between Freshdesk and Linear for true collaboration. Improve response times by ensuring both teams always work on the latest data. An n8n automation workflow template by Avkash Kakdiya.

By InfyOm Technologies

✅ What problem does this workflow solve? Salon staff often spend hours juggling appointment calls, managing bookings manually, and keeping track of customer preferences. This workflow automates your entire salon appointment system via WhatsApp, delivering a personalized and human-like booking experience using AI, memory, and Google Sheets. 💡 Main Use Cases 💁‍♀️ Offer personalized stylist recommendations by remembering customer preferences and past visits. 📅 Provide real-time availability and salon opening hour information. 📝 Book and update appointments directly from customer chat. 🔁 Simplify appointment changes by recalling previous booking details. 🧠 Enable context-aware, memory-driven conversations across multiple interactions. 🧠 How It Works – Step-by-Step 1. 📲 Chat Message Trigger The workflow is triggered whenever a customer sends a message to your WhatsApp salon assistant. 2. 🧠 Memory Buffer for Context Management The assistant uses a Memory Buffer to: Recognize returning customers Avoid repeating questions Maintain conversation flow across multiple sessions This enables a seamless and intelligent dialogue with each customer. 3. 💇 Stylist & Service Lookup When the customer asks for stylist suggestions, available time slots, or services: Extracts request details using AI Queries a Google Sheet containing: Stylist availability Service types Salon opening hours Returns personalized recommendations based on preferences and availability 4. ✅ Appointment Booking Collects all necessary info: Date, time, selected service, stylist, contact info Stores the appointment in Google Sheets Sends a confirmation message to the customer in WhatsApp 5. 🔄 Modify or Cancel Bookings Customers can update or cancel appointments Bot matches records by phone number Modifies or deletes the appointment in the sheet accordingly 🧩 Integrations Used WhatsApp Integration** (via Twilio, Meta API, or other connector) OpenAI/GPT Model** for natural conversation flow and extraction Google Sheets** as a simple and effective appointment database Memory Buffer** for ongoing context across chats 👤 Who can use this? Perfect for: 💇‍♀️ Salons and barbershops 💅 Spas and beauty centers 🧖‍♀️ Wellness studios 🛠 Developers building vertical AI assistants for SMBs If you're looking to modernize your booking process and impress customers with an AI-powered, memory-enabled WhatsApp bot—this workflow delivers. 🚀 Benefits ⏰ Save time for your staff 🧠 Offer truly personalized experiences 📲 Book appointments 24/7 via WhatsApp 📋 Keep all records organized in Google Sheets 🧘 Reduce human error and double bookings 📦 Ready to Launch? Just configure: ✅ Your WhatsApp number + webhook integration ✅ Google Sheet with stylist and service data ✅ OpenAI key for AI-powered conversation ✅ Memory Buffer to enable smart replies And your salon will be ready to offer automated, intelligent booking—right from a simple WhatsApp chat. An n8n automation workflow template by InfyOm Technologies.

By Shahzaib Anwar

📌 Overview This workflow automatically processes incoming Shopify/Gmail leads and pushes them into HubSpot as both Contacts and Deals. It helps sales and marketing teams capture leads instantly, enrich CRM data, and avoid missed opportunities. ⚡ How it works Trigger: Watches for new emails in Gmail. Extract Data: Parses email body (Name, Email, City, Phone, Message, Product URL/Title). Condition: Checks if sender is Shopify before processing. HubSpot: Creates/updates a Contact with customer details. Creates a Deal associated with that contact. 🎯 Benefits 📥 Automates lead capture → CRM 🚫 Eliminates manual copy-paste from Gmail 🔄 Real-time sync between Gmail and HubSpot 📈 Improves sales follow-up speed and accuracy 🛠 Setup Steps Import this workflow into your n8n instance. Connect your Gmail and HubSpot credentials. Replace the HubSpot Deal Stage ID with your own pipeline stage. (Optional) Adjust the Code Node regex if your email format differs. Activate the workflow and test with a sample lead email. 📝 Example Email Format Name: John Doe Email: john@example.com City: London Phone: +44 7000 000000 Body: Interested in product Product Url: https://example.com/product Product Title: Sample Product sticky_notes: name: Gmail Trigger note: > 📧 Watches for new emails in Gmail. Polls every minute and passes email data into the flow. name: Get a Message note: > 📩 Fetches the full Gmail message content (body + metadata) for parsing. name: Extract From Email note: > 🔍 Extracts the sender’s email address from Gmail to identify the source. name: If Sender is Shopify note: > ✅ Condition node that ensures only Shopify-originated emails/leads are processed. name: Code Node (Regex Parser) note: > 🧾 Parses the email body using regex to extract Name, Email, City, Phone, Message, Product URL, and Title. name: Edit Fields (Set Node) note: > 📝 Cleans and structures the extracted fields into proper JSON format before sending to HubSpot. name: HubSpot → Create/Update Contact note: > 👤 Creates or updates a HubSpot Contact with the extracted lead details. name: HubSpot → Create Deal note: > 💼 Creates a HubSpot Deal linked to the Contact, including campaign/product information. An n8n automation workflow template by Shahzaib Anwar.

By Syamsul Bahri

This workflow integrates HetrixTools with WhatsApp via the GOWA API to automate notifications about server monitoring events. It distinguishes between Uptime Monitoring and Resource Usage Monitoring events, formats the message accordingly, and sends it to a WhatsApp number using the GOWA WhatsApp REST API. It's especially useful for DevOps, sysadmins, or teams who need real-time server alerts delivered via WhatsApp. ⚙️ Setup Instructions Set up HetrixTools: Create a HetrixTools account at https://hetrixtools.com/register Create your Uptime Monitors and/or enable Resource Usage Monitoring for your servers. Go to your HetrixTools contact settings and add the n8n Webhook URL provided by the workflow. Make sure to select this contact in your monitor’s alert settings. Configure n8n Webhook: Set the Webhook node to HTTP method: POST Ensure it is accessible via a public URL (you can use n8n Cloud, reverse proxy, or tunnel like ngrok for testing). Customize WhatsApp Message: The workflow includes a conditional branch to check whether the event is a Resource Usage alert or an Uptime alert. Each branch contains editable text nodes for customizing the WhatsApp message content. Set up GOWA WhatsApp API: Make sure your GOWA instance is running and accessible. Create necessary credentials (API key, base URL, etc.). In n8n, add the credentials and fill in the sendChatPresence and sendText nodes accordingly. Deploy the Workflow: Save and activate the workflow. Trigger a test alert from HetrixTools to verify if messages are received on WhatsApp. 🧱 Prerequisites An active HetrixTools account with Uptime Monitors or Resource Usage Monitoring enabled. A publicly accessible instance of n8n with Webhook node enabled. Access to a running and configured GOWA (WhatsApp REST API) server. Required credentials configured in n8n for GOWA (API key, URL, phone number, etc.). An n8n automation workflow template by Syamsul Bahri.

By Le Nguyen

Description (How it works) This workflow keeps your Zalo Official Account access token valid and easy to reuse across other flows—no external server required. High-level steps Scheduled refresh runs on an interval to renew the access token before it expires. Static Data cache (global) stores access/refresh tokens + expiries for reuse by any downstream node. OAuth exchange calls Zalo OAuth v4 with your app_id and secret_key to get a fresh access token. Immediate output returns the current access token to the next nodes after each refresh. Operational webhooks include: A reset webhook to clear the cache when rotating credentials or testing. A token peek webhook to read the currently cached token for other services. Setup steps (estimated time ~8–15 minutes) Collect Zalo credentials (2–3 min): Obtain app_id, secret_key, and a valid refresh_token. Import & activate workflow (1–2 min): Import the JSON into n8n and activate it. Wire inputs (2–3 min): Point the “Set Refresh Token and App ID” node to your env vars (or paste values for a quick test). Adjust schedule & secure webhooks (2–3 min): Tune the run interval to your token TTL; protect the reset/peek endpoints (e.g., secret param or IP allowlist). Test (1–2 min): Execute once to populate Static Data; optionally try the token peek and reset webhooks to confirm behavior. An n8n automation workflow template by Le Nguyen.

By Abdellah Homrani

AI-Powered Meta Ads Builder (Facebook & Instagram) Turn any product page into ready-to-run Meta ads—fast, consistent, and client-friendly. Category:** Marketing Automation / Ads / AI Price:* *\$25** (one-time) Integrations:** Meta (Facebook & Instagram), OpenAI, Firecrawl, n8n Output:* Campaign → Ad Sets → Creatives → 1:1 Images (created in PAUSED status*) Description This template takes a product URL and produces publish-ready Meta ads without the busywork. Your client fills a clean form; the workflow scrapes product data, writes a creative brief, generates ad-set variations, produces 1:1 images with OpenAI, and builds Campaign → Ad Set(s) → Ad(s) in PAUSED for review. Perfect for: agencies, performance marketers, founders who need repeatable creative and less manual setup. Highlights Form-based intake (client-friendly) Schema-clean product extraction (no made-up facts) Vision cues for on-brand visuals Platform-safe 1:1 images and copy lengths Auto placements by default (or customize) Creates assets in PAUSED so you stay in control What’s inside Form Trigger**: “AI Ad Creation” Firecrawl**: scrape product content + images OpenAI (LLM + Vision)**: clean JSON + aesthetic/emotion cues Creative Brief Builder**: merges product facts with tone/goals Campaign JSON Generator**: campaign + ad\_sets as strict schema OpenAI Images**: 1:1 creatives (1024×1024 by default) Meta Graph API: upload assets, create creatives, campaign, ad sets, and ads (PAUSED**) Split / Batch / Wait / If / Set / Merge**: stable, scalable processing How it works Form → Firecrawl scrape → Product JSON (LLM) → Vision style cues → Creative brief → Campaign JSON (LLM) → Split into ad sets → For each ad set: → Generate image → Upload to Meta → Create Creative → Create Campaign → Create Ad Set → Create Ad (PAUSED) What changed in this version 🔐 No hardcoded API keys — all auth uses n8n Credentials 📌 PinData removed — the template ships clean (no sample data) 🧩 Clean placeholders for IDs/links in “Configuration Meta Ads” (your_ad_account_id, etc.) Requirements OpenAI** credential (Chat + Images) Facebook Graph API** credential (with ads_management permissions) Firecrawl** credential (API key) Your Ad Account ID, Facebook Page ID, Pixel ID, Destination URL Quick setup (5 steps) Import the JSON in n8n. Create Credentials for OpenAI, Facebook Graph API, Firecrawl. Open “Configuration Meta Ads” node and set: ad_account_id, facebook_page_id, pixel_id, website_link Open the Form Trigger URL and submit a real product URL. In Ads Manager, review campaign/ad sets/ads (they’re PAUSED), then enable. Inputs (Form) Product URL (required) Campaign Type (Launch, Seasonal, Awareness, Retargeting, LTO) Target Platform (Facebook, Instagram) Number Of Variation (integer) Target Audience Key Message / Offer Emotional Tone (multi-select: Joy, Trust, Fear, Surprise, Sadness, Disgust, Anger) Outputs Creative Brief** (concise, platform-aware) Campaign JSON** with: Ad sets (audience, placements, schedule/budget placeholders) Creative (primary\_text, headline, description, CTA, UTM defaults, reference image) AdConcept (imageName, prompt, emotional hook, 1:1 safe zones) Meta assets created: uploads → creatives → campaign → ad set(s) → ad(s) (PAUSED**) Sticky notes (mandatory) > Credentials > > * Use OpenAI, Facebook Graph API, and Firecrawl credentials in n8n. > * ⚠️ No hardcoded keys anywhere (HTTP node or otherwise). > Form Testing > > * Use a real product URL with at least one image. > * Start with 1–2 variations; scale after review. > * If scraping fails, verify Firecrawl key and the site’s policies. > Meta Upload > > * Set ad_account_id, facebook_page_id, pixel_id, website_link. > * If uploads fail, check account permissions and app scopes. > OpenAI Images > > * Default: 1:1, 1024×1024. > * You can change size in the Images node (keep FB/IG safe zones). > * Prompts should avoid policy-sensitive claims. > Safety & Review > > * Everything is created PAUSED. > * Review copy, claims, and targeting for compliance. > * Enable after quality checks. Security & compliance Secrets live in n8n Credentials or environment variables—never in nodes. Follow Meta ad policies (no restricted claims, no before/after, etc.). Product facts only; unknown fields remain null/empty arrays. Performance tips Start with auto placements; test Feed/Reels later if needed. Keep primary text 125–200 chars; headline short (testimonial-style in quotes). Use the best product image as reference. Scale carefully: tune Batch and Wait for your throughput. FAQ Does it publish automatically? No. Ads are created PAUSED for review. Instagram-only campaigns? Yes. Set placements to IG (or keep auto and let Meta optimize). Thin product pages? Extractor returns null for missing fields; the brief adapts without inventing data. Bring my own audiences? Swap the generated audience block for your saved audiences or static lists. Change image model/size? Yes—edit the OpenAI Images node (model/size). Keep 1:1 for FB/IG. An n8n automation workflow template by Abdellah Homrani.

By HoangSP

Who’s it for Teams that want to turn a chat prompt into a researched, ready-to-post social update—optionally published to Facebook. What it does / How it works Chat Trigger receives the user prompt Topic Agent optionally calls a research sub-workflow for fresh sources Outputs are validated into a structured JSON Post Writing Agent crafts a concise Vietnamese post (Optional) Facebook Graph API publishes to your Page How to set up Connect OpenAI & Facebook in Credentials (no API key inside nodes). In Tool: Call Perplexity Researcher, set your research workflowId. In Publish: Facebook Graph API, set your Page ID and edge. Adjust prompts/tone and the LANGUAGE in CONFIG. Test the flow with sample prompts in the chat. Requirements n8n (Cloud or self-hosted) OpenAI API key (stored in Credentials) Facebook Page publish permissions (Optional) a research workflow for Perplexity How to customize the workflow Add moderation/review gates before publishing. Duplicate the publish path for other platforms. Store outputs in Sheets/Notion/DB for auditing. Tune model choice & temperature for your brand voice. Security Avoid hardcoding secrets in HTTP or Code nodes. Keep identifiers (Page IDs, workflowIds) configurable in CONFIG. An n8n automation workflow template by HoangSP.

By Tegar karunia ilham

🌦️ Intelligent Aquaculture Automation for Indonesia Transform your fish farming operation with this cutting-edge n8n workflow that combines Indonesia's official BMKG weather data with IoT-powered feeding automation. This system intelligently reduces feed by 20% when rain probability exceeds 60%, preventing overfeeding during adverse weather conditions that could compromise water quality and fish health. 🚀 Key Features 🌦️ Real-time BMKG Integration: Fetches official Indonesian weather forecasts every 12 hours using BMKG's public API with precise ADM4 regional targeting 🤖 Smart Decision Engine: Advanced JavaScript algorithms analyze 6-hour and 12-hour rain probabilities to make optimal feeding decisions automatically 📱 ESP8266 IoT Control: Seamlessly sends HTTP webhook commands to your ESP8266/ESP32-based fish feeder hardware with JSON payloads 💬 Rich Telegram Notifications: Comprehensive reports including weather analysis, feeding decisions, hardware status, and next feeding schedule ⏰ Precision Scheduling: Automated execution at 05:30 and 16:30 WIB (Indonesian Western Time) with cron-based triggers 📊 Activity Logging: Complete audit trail with timestamps, weather data, and feeding decisions for operational monitoring 🛠️ Technical Architecture Core Node Components: Schedule Trigger:** Automated twice-daily execution HTTP Request:** BMKG API integration with timeout handling Code (JavaScript):** Weather parsing and feeding ratio calculations IF Condition:** Intelligent branching based on configurable rain thresholds Telegram:** Formatted notifications with markdown support Set Variables:** Secure credential management with placeholder tokens 📋 Prerequisites ✅ n8n Instance: Self-hosted or cloud deployment ✅ Telegram Bot: Create via @BotFather for notifications ✅ ESP8266/ESP32: Hardware with servo motor for automated feeding ✅ Arduino Skills: Basic programming knowledge for hardware setup ✅ Indonesian Location: Uses BMKG API with ADM4 regional codes ⚙️ Configuration Requirements 📍 Location Settings: Update latitude, longitude, and BMKG ADM4 code in the Config node 🤖 Telegram Bot: Configure bot token and chat ID in credentials 🔗 ESP8266 Webhook: Set your device's IP address for hardware communication 📊 Feeding Parameters: Customize rain threshold (default: 60%) and feed reduction (default: -20%) 🎯 Perfect For 🏭 Commercial Aquaculture: Large-scale fish farming operations requiring weather-aware feeding 🏠 Hobbyist Enthusiasts: Home aquarium and pond automation projects 🌱 Smart Agriculture: Integration with comprehensive farm management ecosystems 🔧 IoT Learning: Educational platform for weather-based automation development 🌍 Environmental Research: Combining meteorological data with livestock care protocols 📊 Rich Output Examples The workflow generates detailed Telegram reports featuring: Current Weather Analysis:** 6-hour and 12-hour rain probability breakdowns Feeding Decision Logic:** Clear rationale for feed adjustments with percentages Hardware Confirmation:** ESP8266 response status and command execution verification Schedule Preview:** Next automated feeding time with countdown Historical Logs:** Comprehensive activity tracking for pattern analysis 🔧 Hardware Integration Guide Designed for ESP8266-based feeders accepting HTTP POST commands. The workflow transmits structured JSON containing: { "command": "FEED_REDUCE_20", "feed_ratio": -20, "rain_prob": 75, "timestamp": "2024-09-18T10:30:00Z", "location": "Main Pond" } 🌍 Regional Adaptation Indonesia-Optimized: Built specifically for BMKG's official weather API with ADM4 regional precision Global Compatibility: Easily adaptable for international weather services by modifying HTTP requests and parsing logic Scalable Architecture: Supports multiple pond locations with separate ADM4 configurations 🔒 Security & Credentials All API keys use {{PLACEHOLDER}} format for secure credential management No hardcoded sensitive information in workflow nodes Telegram bot tokens managed through n8n's credential system ESP8266 webhooks support local network security 📈 Performance Benefits 20% Feed Optimization:** Automatic reduction during high rain probability periods Water Quality Protection:** Prevents overfeeding that degrades aquatic environment Cost Efficiency:** Reduces feed waste while maintaining fish health 24/7 Monitoring:** Continuous weather analysis without manual intervention Scalable Operations:** Supports multiple feeding locations from single workflow. An n8n automation workflow template by Tegar karunia ilham.