Workflow Templates

Who’s it for Teams that manage tasks in ClickUp and want those tasks reflected—and kept in sync—in Google Calendar automatically. How it works A ClickUp Trigger captures task events (create, update, delete). For new tasks, the workflow creates a Google Calendar event with the correct start/end. It stores a mapping between clickupTaskId and calendarEventId in a Google Sheet so later updates and deletions can target the right event. Multiple lanes (personal/school/tech/internship) let you route tasks to different calendars. How to set up Assign ClickUp OAuth, Google Calendar, and Google Sheets credentials to the nodes. Open the Configuration node and fill: calendarId_* for each lane sheetId and sheetTabName for the mapping sheet (optional) clickupTeamId Enable the ClickUp Trigger and run a manual test to validate mapping creation and event syncing. Requirements ClickUp workspace with OAuth permissions Google Calendar & Sheets access A Google Sheet for the event↔task mapping How to customize the workflow Edit the calendar routing in Edit Fields nodes or point them to different calendarId_* values. Adjust event colors/fields in Google Calendar nodes. Extend the mapping sheet with extra columns (e.g., status, labels) as needed.

Smart IoT Device Health Monitor with AI-Powered Dashboard Analysis and Real-Time Alerting 🎯 Target Audience IT operations and infrastructure teams IoT system administrators and engineers Facility and building management teams Manufacturing and industrial operations managers Smart city and public infrastructure coordinators Healthcare technology administrators Energy and utilities monitoring teams Fleet and asset management professionals Security and surveillance system operators Property and facility maintenance teams 🚀 Problem Statement Monitoring hundreds of IoT devices across multiple dashboards is overwhelming and reactive, often leading to costly downtime, missed maintenance windows, and system failures. This template solves the challenge of proactive IoT device monitoring by automatically analyzing device health metrics, detecting issues before they become critical, and delivering intelligent alerts that help teams maintain optimal system performance. 🔧 How it Works This workflow automatically monitors your IoT dashboard every 30 minutes using AI-powered data extraction, analyzes device health patterns, calculates system-wide health scores, and sends intelligent alerts only when intervention is needed, preventing alert fatigue while ensuring critical issues are never missed. Key Components Schedule Trigger - Runs every 30 minutes for continuous device monitoring AI Dashboard Scraper - Uses ScrapeGraphAI to extract device data from any IoT dashboard without APIs Health Analyzer - Calculates system health scores and identifies problematic devices Smart Alert System - Sends notifications only when health drops below thresholds Telegram Notifications - Delivers formatted alerts with device details and recommendations Activity Logger - Maintains historical records for trend analysis and reporting 📊 Device Health Analysis Specifications The template monitors and analyzes the following device metrics: | Metric Category | Monitored Parameters | Analysis Method | Alert Triggers | Example Output | |-----------------|---------------------|-----------------|----------------|----------------| | Device Status | Online/Offline/Error | Real-time status check | Any offline devices | "Device-A01 is offline" | | Battery Health | Battery percentage | Low battery detection | Below 20% charge | "Sensor-B03 low battery: 15%" | | Temperature | Device temperature | Overheating detection | Above 70°C | "Gateway-C02 overheating: 75°C" | | System Health | Overall health score | Online device ratio | Below 80% health | "System health: 65%" | | Connectivity | Network status | Connection monitoring | Loss of communication | "3 devices offline" | | Performance | Response metrics | Trend analysis | Degraded performance | "Response time increasing" | 🛠️ Setup Instructions Estimated setup time: 15-20 minutes Prerequisites n8n instance with community nodes enabled ScrapeGraphAI API account and credentials Telegram bot token and chat ID Access to your IoT dashboard URL Basic understanding of your device naming conventions Step-by-Step Configuration 1. Install Community Nodes Install required community nodes npm install n8n-nodes-scrapegraphai 2. Configure ScrapeGraphAI Credentials Navigate to Credentials in your n8n instance Add new ScrapeGraphAI API credentials Enter your API key from ScrapeGraphAI dashboard Test the connection to ensure it's working 3. Set up Schedule Trigger Configure the monitoring frequency (default: every 30 minutes) Adjust timing based on your operational needs: Every 15 minutes: */15 * * * * Every hour: 0 * * * * Every 5 minutes: */5 * * * * 4. Configure Dashboard URL Update the "Get Data" node with your IoT dashboard URL Customize the AI prompt to match your dashboard structure Test data extraction to ensure proper JSON formatting Adjust device field mappings as needed 5. Set up Telegram Notifications Create a Telegram bot using @BotFather Get your chat ID from @userinfobot Configure Telegram credentials in n8n Test message delivery to ensure alerts work 6. Customize Health Thresholds Adjust health score threshold (default: 80%) Set battery alert level (default: 20%) Configure temperature warning (default: 70°C) Customize alert conditions based on your requirements 7. Test and Validate Run the workflow manually with your dashboard Verify device data extraction accuracy Test alert conditions and message formatting Confirm logging functionality works correctly 🔄 Workflow Customization Options Modify Monitoring Frequency Adjust schedule for different device criticality levels Add business hours vs. off-hours monitoring Implement variable frequency based on system health Add manual trigger for on-demand monitoring Extend Device Analysis Add more device metrics (memory, CPU, network bandwidth) Implement predictive maintenance algorithms Include environmental sensors (humidity, air quality) Add device lifecycle and warranty tracking Customize Alert Logic Implement escalation rules for critical alerts Add alert suppression during maintenance windows Create different alert channels for different severity levels Include automated ticket creation for persistent issues Output Customization Add integration with monitoring platforms (Grafana, Datadog) Implement email notifications for management reports Create executive dashboards with health trends Add integration with maintenance management systems 📈 Use Cases Industrial IoT Monitoring**: Track manufacturing equipment and sensors Smart Building Management**: Monitor HVAC, lighting, and security systems Fleet Management**: Track vehicle telematics and diagnostic systems Healthcare Device Monitoring**: Ensure medical device uptime and performance Smart City Infrastructure**: Monitor traffic lights, environmental sensors, and public systems Energy Grid Monitoring**: Track smart meters and distribution equipment 🚨 Important Notes Respect your dashboard's terms of service and rate limits Implement appropriate delays between requests to avoid overloading systems Regularly review and update device thresholds based on operational experience Monitor ScrapeGraphAI API usage to manage costs effectively Keep your credentials secure and rotate them regularly Ensure alert recipients are available to respond to critical notifications Consider implementing backup monitoring systems for critical infrastructure Maintain device inventories and update monitoring parameters as systems evolve 🔧 Troubleshooting Common Issues: ScrapeGraphAI connection errors: Verify API key and account status Dashboard access issues: Check URL accessibility and authentication requirements Data extraction failures: Review AI prompt and dashboard structure changes Missing device data: Verify device naming conventions and field mappings Alert delivery failures: Check Telegram bot configuration and chat permissions False alerts: Adjust health thresholds and alert logic conditions Support Resources: ScrapeGraphAI documentation and API reference n8n community forums for workflow assistance Telegram Bot API documentation IoT platform-specific monitoring best practices Device manufacturer monitoring guidelines Industrial IoT monitoring standards and frameworks

Slack Workflow Router: AI-Powered Workflow Selection Problem Statement Slack only allows one webhook per Slack app, and n8n generates a unique webhook for each workflow. This limitation means you typically need to create multiple Slack apps to trigger multiple n8n workflows from Slack. This workflow solves that problem by acting as a gateway for a single Slack app, enabling it to trigger multiple n8n workflows. How It Works When a message is received from Slack, an AI agent analyzes the message and selects the most suitable workflow to execute. The available workflows are stored in a data table, including their ID, name, and description, which the agent uses to make its decision. This approach allows you to manage and trigger multiple workflows from a single Slack app, making your Slack-to-n8n integration much more scalable and maintainable. Key Features Trigger multiple n8n workflows from a single Slack app mention. AI-powered workflow selection based on user message and workflow descriptions. Centralized management of available workflows via a data table. Scalable and easy to maintain—no need to create multiple Slack apps. Setup Instructions Create a data table in your n8n project with these columns: workflow_id, workflow_name, and workflow_description. Add your workflows to the table. Connect your Slack and OpenAI accounts. Deploy the workflow and mention your Slack app to trigger automations. This template is ideal for teams who want to centralize and scale their Slack automation without creating multiple Slack apps.

This workflow acts as a System Prompt Optimizer Agent. You send it a draft prompt or goal, and it returns: A rewritten optimized system prompt that is clear, specific, and actionable. A recommendation for the best OpenAI model to use based on reasoning needs, complexity, and latency/cost tradeoffs. The workflow uses memory for context, so you can iteratively refine prompts. ⚙️ Setup Instructions 1️⃣ Set Up OpenAI Connection Go to OpenAI Platform Navigate to OpenAI Billing Add funds to your billing account Copy your API key into the OpenAI credentials in n8n 📝 Example Question

This workflow helps template creators automatically generate an overview sticky note for any n8n template. Paste your workflow JSON into the Set node, run the workflow, and the AI returns a ready-to-use sticky note node JSON with a clear title, “How it works” steps and a setup checklist - all formatted in Markdown and sized correctly for the canvas.

Remediate security vulnerabilities with Port This workflow automatically enriches security vulnerability alerts with organizational context from Port and routes them to the appropriate teams or AI agents for remediation. How it works n8n receives a new vulnerability from your security scanner (e.g., Snyk) via webhook The workflow calls Port's context lake to enrich the alert with service, ownership, environment, and dependency data. With this context, the workflow either sends targeted Slack notifications to the owning team or triggers an AI remediation flow to propose and apply a fix. Setup steps [ ] Sign up with a free account on port.io. [ ] Create the required AI agent in Port. [ ] Configure credentials in n8n for Port, Slack, and OpenAI/Claude. [ ] Trigger the webhook with a sample vulnerability to verify context retrieval, Slack notifications, and AI remediation.",

😎 For Fast-Growing Your Telegram Channel (Lead Magnet Gate) 📋 No plug-and-play workflow This workflow implements a subscription gate for a Telegram lead magnet campaign. Users must subscribe to a Telegram channel before they can access the lead magnet (e.g., a free resource, discount code, or exclusive content). 🇺🇦 Українською Цей воркфлоу реалізує шлюз підписки для кампанії лід-магніту в Telegram. Користувачі повинні підписатися на канал Telegram, перш ніж зможуть отримати доступ до лід-магніту (наприклад, безкоштовного ресурсу, коду знижки або ексклюзивного контенту). 🎥 YouTube Video Integration Watch Tutorial in English - UPD Link After Approve Workflow Дивитись Інструкцію Українською -UPD Link After Approve Workflow NOW Sticky Notes - all have for Implementation 🛠️ Configuration Notes Channel ID - Replace inputyourid with your actual Telegram channel ID (without @) or -100 type for closed channel Bot Token - Replace bot token placeholders with your actual Telegram bot token Lead Magnet - Update the lead magnet delivery message with your actual file/resource links/ webinar link / discount code Upsell Content - Customize the upsell/cross-sell content as needed 🌍 Bilingual Support All user-facing messages are provided in both Ukrainian and English to support international audiences: Ukrainian text appears first English text follows after a line break Buttons include both languages where appropriate. 📈 Use Cases Lead generation for Telegram channels Content gating for exclusive resources Community building through subscription requirements Marketing funnel automation 🤖 Template Features ✅ Ready-to-Use Template Simply import and configure with your Telegram bot credentials. 📚 Comprehensive Documentation Visual sticky notes explaining each node's purpose Detailed workflow documentation Logic explanation notes 🧠 Smart Workflow Design Efficient data flow with minimal API calls Proper error handling and user feedback Responsive button interactions Conditional routing based on subscription status 🚀 Quick Start Guide Import Workflow Download the JSON file Import into your n8n instance (Cloud or Self-hosted) Configure Telegram Credentials Set up your Telegram bot token in the credentials section Ensure your bot has necessary permissions Customize Channel Settings Replace inputyourid with your actual Telegram channel ID Update all placeholder links with your actual resources Personalize Messages Modify lead magnet delivery messages Customize upsell content Watch YouTube tutorial links Test the Workflow Activate the workflow in your n8n instance Test with a non-subscribed account Verify subscription verification works correctly Test the upsell sequence with the /ok command (command you can change) 📄 License This template is provided as-is for use with n8n automation platform. Feel free to modify and adapt to your specific needs. 🙋‍♂️ Support For issues with this template, please check: All placeholder values have been replaced Telegram bot has proper permissions n8n instance is properly configured Internet connectivity is available https://t.me/nikolenkoclub

Working with Large Documents In Your VLM OCR Workflow Document workflows are popular ways to use AI but what happens when your document is too large for your app or your AI to handle? Whether its context window or application memory that's grinding to a halt, Subworkflow.ai is one approach to keep you going. > Subworkflow.ai is a third party API service to help AI developers work with documents too large for context windows and runtime memory. Prequisites You'll need a Subworkflow.ai API key to use the Subworkflow.ai service. Add the API key as a header auth credential. More details in the official docs https://docs.subworkflow.ai/category/api-reference How it Works Import your document into your n8n workflow Upload it to the Subworkflow.ai service via the Extract API using the HTTP node. This endpoint takes files up to 100mb. Once uploaded, this will trigger an Extract job on the service's side and the response is a "job" record to track progress. Poll Subworkflow.ai's Jobs endpoint and keep polling until the job is finished. You can use the "IF" node looping back unto itself to achieve this in n8n. Once the job is done, the Dataset of the uploaded document is ready for retrieval. Use the Datasets and DatasetItems API to retrieve whatever you need to complete your AI task. In this example, all pages are retrieved and run through a multimodal LLM to parse into markdown. A well-known process when parsing data tables or graphics are required. How to use Integrate Subworkflow's Extract API seemlessly into your existing document workflows to support larger documents from 100mb+ to up to 5000 pages. Customising the workflow Sometimes you don't want the entire document back especially if the document is quite large (think 500+ pages!), instead, use query parameters on the DatasetItems API to pick individual pages or a range of pages to reduce the load. Need Help? Official API documentation**: https://docs.subworkflow.ai/category/api-reference Join the discord**: https://discord.gg/RCHeCPJnYw

Description: Recover missed opportunities automatically with this n8n automation template. The workflow connects with Calendly, identifies no-show meetings, and instantly sends personalized Telegram messages encouraging leads to reschedule. It then notifies the assigned sales representative via email, ensuring timely human follow-up. Perfect for sales teams, consultants, and customer success managers who want to minimize no-shows, improve conversion rates, and keep pipelines warm — all without manual tracking. What This Template Does (Step-by-Step) ⏰ Runs Every Hour Automatically triggers every hour to check your Calendly events for recently missed meetings. 📥 Fetch Active Calendly Appointments Retrieves all scheduled events from Calendly using your user URI and event metadata. 🔍 Filter for No-Shows (30+ Minutes Past) Uses a built-in logic block to detect appointments that ended over 30 minutes ago and were not attended. 🎯 Check Lead Intent Processes only leads tagged as “High Intent” in metadata to focus recovery efforts on qualified prospects. 💬 Send Telegram Message to Lead Sends a personalized message to the lead’s Telegram ID, including a direct reschedule link and friendly tone from your sales team. 📧 Notify Assigned Sales Rep via Email Alerts the relevant rep (from metadata) that the lead missed a meeting and has received an automated Telegram follow-up. Includes contact name, status update, and meeting link for manual re-engagement. 🔁 Continuous Follow-Up Automation Repeats hourly, ensuring no missed appointment goes unnoticed — even outside working hours. Key Features 🤖 Smart detection of no-shows via Calendly API 💬 Telegram message automation with personalization 📧 Sales rep email alerts with complete context 🎯 Filters by “High Intent” tag to focus efforts ⚙️ Easy setup with environment variables and credentials Use Cases 📞 Automatically re-engage missed sales calls 📅 Reduce no-show rates for Calendly meetings 💬 Keep your sales pipeline active and responsive 📢 Notify sales reps in real time about recovery actions Required Integrations Calendly API – to fetch scheduled events and meeting details Telegram API – to send automated reschedule messages SMTP or Gmail – to alert the assigned sales representative Why Use This Template? ✅ Saves hours of manual follow-up effort ✅ Boosts reschedule rate for missed meetings ✅ Keeps high-value leads warm and engaged ✅ Ensures your sales reps never miss a no-show

This workflow is designed for teams or freelancers who want to auto-generate and send contracts based on information gathered from a Typeform (e.g., client name, project scope, deadlines). Perfect for HR onboarding, client agreements, or legal operations. Prerequisites To use this workflow, you’ll need: A Typeform account and a published form Access to Google Docs (or use a local document template) Gmail or SMTP email integration in n8n n8n Desktop or a hosted n8n instance How It Works Trigger:** Listens for new Typeform submissions. Extract Data:** Parses the answers from the form. Generate Contract:** Fills a contract template using form inputs. Create PDF:** Exports the filled contract as a PDF. Send Email:** Sends the PDF to the client’s email address provided in the form. Nodes Used Typeform Trigger** – Triggers on form submission. Set Node** – Maps form answers into variables. Google Docs (or HTTP Request)** – Uses a template to generate the contract. Google Drive / PDF Converter** – Converts to PDF (if needed). Email (Gmail/SMTP)** – Sends the completed contract to the recipient. Tips Replace the Google Docs template ID with your own. Ensure the variable placeholders (like {{client_name}}) match your document. Use the Cron node instead of Typeform Trigger if you want to poll periodically.

Description: Accelerate VIP support handling with this n8n workflow template that automatically identifies high-priority customers and ensures their tickets get instant attention. This automation pulls customer ticket data from Google Sheets, checks for the VIP tag, and seamlessly creates a priority task in ClickUp, while sending an instant Telegram alert to your team. What This Template Does: 🔍 Detects VIP-tagged customers in real time 📝 Creates high-priority ClickUp tasks for their tickets 📱 Sends Telegram alerts with ticket details (subject + requester email) 📊 Organizes VIP workload for easy tracking in ClickUp Built-in logic ensures: • Only VIP-tagged customers are escalated • Priority tasks are auto-assigned without delays • Teams receive instant notifications for fast response • No missed high-value customer interactions Requirements: • Google Sheets API credentials • ClickUp API credentials • Telegram Bot token & Chat ID • n8n instance (self-hosted or cloud) Perfect For: Customer support teams, sales organizations, and service-based businesses who need to prioritize VIP tickets instantly and streamline customer experience.

Overview This n8n template tracks GitHub Trending repositories (daily/weekly/monthly), parses the trending page into structured data (rank, repo name, stars, language, etc.), and stores results in Google Sheets with automatic deduping. It’s designed for teams who want a simple “trending feed” for engineering research, developer tooling discovery, and weekly reporting. Who is this for? Developers, PMs, DevRel, and tooling teams who want a lightweight trend radar Anyone building a curated list of fast-rising open source projects Teams who want Sheets-based tracking without manual copy/paste What problems it solves Automatically collects GitHub Trending data on a schedule Prevents duplicate rows using a stable dedupe_key Updates existing rows when values change (rank/stars/score) How it works A schedule triggers the workflow. Inputs define the trending window (daily, weekly, or monthly) and optional languages. ScrapeOps fetches the GitHub Trending HTML reliably. The workflow parses repositories and ranks from the HTML. Cleaned rows are written to Google Sheets using Append or Update Row matching on dedupe_key. Setup steps (~5–10 minutes) 1) ScrapeOps Register & get an API key: https://scrapeops.io/app/register/n8n Read the n8n overview: https://scrapeops.io/docs/n8n/overview/ (Optional) Learn ScrapeOps Proxy API features: https://scrapeops.io/docs/n8n/proxy-api/ 2) Google Sheets Duplicate this sheet/create a Sheet and add a trending_raw tab. Add columns used by the workflow (e.g. captured_at, since, source_url, rank_on_page, full_name, repo_url, stars_total, forks_total, stars_in_period, score, dedupe_key). In the Google Sheets node, choose Append or Update Row and set Column to match on = dedupe_key. 3) Customize Change since to daily/weekly/monthly in the Inputs node. Add languages via languages_csv (example: any,python,go,rust). Adjust delay if needed. Pre-conditions ScrapeOps account + API key configured in n8n Google Sheets credentials connected in n8n A Sheet tab named trending_raw with matching columns Disclaimer This template uses ScrapeOps as a community node. You are responsible for complying with GitHub’s Terms of Service, robots directives, and applicable laws in your jurisdiction. Scraping targets can change at any time; you may need to update wait times and parsing logic accordingly. Use responsibly for legitimate business purposes.