Webhook and Telegram integration

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. **🌸 Graceful Deliveries — Service Scheduling & Route Planner (Notion + Telegram) What this template does** Turn new bookings into a graceful, automated delivery plan—with geocoded addresses, a one-tap Google Maps route, owner alerts on Telegram, and sweet pre-arrival updates to your clients (email/SMS). Optional Notion/Sheets logging gives you a beautiful “Delivery Day Planner” you can filter by day or status. Perfect for: florists, mobile dog groomers, massage therapists, cleaners, and any home-visit service that loves systems with a feminine touch. ✨ 💗 Warm: on-brand, human copy clients adore 🧭 Clear logistics: route links, timing, and notes—without chaos 🧰 No-code friendly: plug-and-play nodes, optional storage 🔐 Safe: no API keys in JSON; credentials live in n8n Requirements n8n account (self-hosted or cloud) Telegram Bot (for owner alerts) Email (Gmail OAuth2 or SMTP) for client messages (Optional) Notion or Google Sheets for storing bookings Geocoding: OpenStreetMap Nominatim (no API key required) Setup (5–10 minutes) Import the JSON into n8n. Open Webhook (Bookings) → copy its Test URL (then Production URL when ready). In your booking tool (Calendly, Tally/Typeform/Airtable, Google Forms via Apps Script), POST bookings to the webhook with the fields below. Add Telegram credential to “Telegram → Owner Alert.” Add Email credential to “Email → Client (Pre-arrival).” (Optional) Connect Notion or Google Sheets and add a “Create Page / Append Row” step. Sample Payload (copy for testing) { "name": "Sarah Bloom", "email": "[email protected]", "phone": "+1 555-1234", "address": "123 Maple St, Austin, TX 78701", "datetime": "2025-09-01T10:30:00-05:00", "service": "Mobile Grooming – Full Bath", "notes": "Max is shy; prefers lavender shampoo", "pet_name": "Max", "pet_photo_url": "https://example.com/max.jpg" } Fallbacks supported: client_name, full_name, appointment, date + time, booking_type, special_notes, street/line1 + city + state + zip. How it works (flow) Webhook (Bookings): receives the booking payload. Parse Booking (Function): normalizes fields, derives ISO datetime if possible. Geocode (HTTP → OSM Nominatim): looks up lat/lng (no API key). Format Geocode (Function): extracts coordinates. Merge Data: combines parsed booking + coordinates. Build Summary & Links (Function): Creates a Google Maps route link Calculates pre-arrival time = 1 hour before datetime Composes the owner alert text Telegram → Owner Alert: sends “🚗 Route ready!” with map link. Wait until 1h before: schedules pre-arrival message. Email → Client (Pre-arrival): warm, on-brand message with ETA + route link. Respond to Webhook: returns status + route to your booking tool. Optional: Notion / Google Sheets schema Notion DB: Delivery Day Planner Date (Date), Client (Title), Email (Email), Phone (Phone), Address (Rich Text), Service (Select), Notes (Rich Text), Lat (Number), Lng (Number), Status (Select: Planned / On the way / Done) Google Sheets columns: DateTime, Client, Email, Phone, Address, Service, Notes, Lat, Lng, Status Customize (ideas) ✉️ Swap Email for Twilio SMS (or add both). 🗂️ Log every booking to Notion/Sheets for day and route views. 🧾 Generate a Driver PDF (Google Docs API → export PDF). 🧮 Multi-stop routes: add a Function node (nearest-neighbor) to sort stops. 🎨 Keep copy on-brand (Playfair Display + Lato; Blush #F7D6DC, Gold #F5E1A4, Taupe #D8CFC4, Slate #4A4A4A). Testing In Webhook node, click Test and POST the sample JSON. Confirm Telegram alert arrives with the route link. Set a near-future datetime to quickly test the Wait → Email path. If datetime missing/invalid, the pre-arrival node sends immediately (intended fallback). Troubleshooting & Rate Limits No Telegram message? Start a chat with your bot first; bots can’t initiate. Check you used the correct chat ID. Email didn’t send? Ensure credential is attached to the Email node and the “to” address is valid. Geocode failed? Try a more complete address (street, city, state, ZIP). OSM is free but rate-limited—avoid rapid bulk tests. Timezone drift? datetime should include timezone if possible (e.g., 2025-09-01T10:30:00-05:00). Keywords (SEO) service scheduling, delivery route planner, booking automation, n8n workflow, Notion CRM, mobile business, florist delivery, pet grooming, client reminders, Telegram alerts, pre-arrival updates, geocoding, Google Maps link Made with love by The Workflow Muse 💖 Elegant automation for those who run heart-led businesses.

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Deliver seamless, AI-driven customer support on Telegram and WhatsApp—powered by GPT-4 Turbo and n8n. 🌟 Key Features Unified Messaging:** Receive and normalize messages from both Telegram (via Bot Trigger) and WhatsApp (via Webhook). Contextual AI Responses:** Build customer context from Google Sheets, then craft personalized replies with GPT-4 Turbo. Smart Routing:** Automatically detect platform and send replies with platform-appropriate formatting (HTML for Telegram, plain for WhatsApp). Intent Detection & Escalation:** Flag orders, appointments or complex queries and trigger Slack notifications for human handoff. Comprehensive Logging:** Append every interaction to a “conversations” sheet and upsert customer profiles in a “customers” sheet. 📋 Prerequisites n8n instance (self-hosted or n8n Cloud) Credentials: OpenAI API key Telegram Bot Token WhatsApp Business API credentials (WHATSAPP_PHONE_ID) Google Sheets service-account credentials Slack Incoming Webhook URL Google Sheets Setup: customers sheet with columns: user_id, user_name, previousOrders, lastInteraction, preferences, conversationHistory conversations sheet with columns: user_id, user_name, platform, message, ai_response, timestamp, needs_escalation, is_order, is_appointment 🚀 Setup & Usage Import the provided JSON into your n8n editor. Configure each node’s credentials in n8n’s Credentials panel. Set the following Workflow Variables: GOOGLE_SHEET_ID WHATSAPP_PHONE_ID Activate the Telegram Bot Trigger and WhatsApp Webhook nodes. Test by messaging your bot on Telegram and WhatsApp. 🔍 How It Works Trigger: Listens for new Telegram updates or WhatsApp webhook calls. Normalize Message: Standardizes payload into { user_id, user_name, message_text, platform, chat_id, timestamp }. Get Customer Data: Reads from “customers” sheet to fetch past history and order count. Build AI Context: Merges incoming message with customer info and history. AI Assistant: Sends context to GPT-4 Turbo (temperature 0.8, maxTokens 800). Process Response: Cleans formatting, identifies intents (order, appointment), and sets escalation flags. Platform Router: Routes reply to the appropriate “Send Telegram” or “Send WhatsApp” node. Log Conversation: Appends each message and response to the “conversations” sheet. Update Customer: Increments previousOrders, updates last interaction timestamp, and saves a snippet of the latest message. Escalation: If flagged, posts a formatted alert to your Slack channel for immediate attention. Empower your business with 24/7 AI-powered support—save time, increase conversions, and ensure no customer inquiry goes unanswered.

-- Disclaimer: This workflow uses a community node and therefore only works for self-hosted n8n users -- Transform YouTube videos into comprehensive summaries and structured analysis instantly. This n8n workflow automatically extracts, processes, and analyzes video transcripts to deliver clear, organized insights without watching the entire video. Time-Saving Features 🚀 Instant Processing Simply provide a YouTube URL and receive a structured summary within seconds, eliminating the need to watch lengthy videos. Perfect for research, learning, or content analysis. 🤖 AI-Powered Analysis Leverages GPT-4o-mini to analyze video transcripts, organizing key concepts and insights into a clear, hierarchical structure with main topics and essential points. Smart Processing Pipeline 📝 Automated Transcript Extraction Supports public YouTube video Handles multiple URL formats Extracts complete video transcripts automatically 🧠 Intelligent Content Organization Breaks down content into main topics Highlights key concepts and terminology Maintains technical accuracy while improving clarity Structures information logically with markdown formatting Perfect For 📚 Researchers & Students Quick comprehension of educational content and lectures without watching entire videos. 💼 Business Professionals Efficient analysis of industry talks, presentations, and training materials. 🎯 Content Creators Rapid research and competitive analysis of video content in your niche. Technical Implementation 🔄 Workflow Components Webhook endpoint for URL submission YouTube API integration for video details Transcript extraction system GPT-4 powered analysis engine Telegram notification system (optional) Transform your video content consumption with an intelligent system that delivers structured, comprehensive summaries while saving hours of viewing time.

Healthcare Clinic Assistant with WhatsApp and Telegram Integration Version: 1.1.0 n8n Version: 1.88.0+ License: MIT 📋 Description A comprehensive and modular automation workflow designed for healthcare clinics. It manages patient communication, appointment scheduling, confirmations, rescheduling, internal tasks, and media processing by integrating WhatsApp, Telegram, Google Calendar, and Google Tasks, combined with AI-powered agents for maximum efficiency. This system guarantees proactive communication with patients, streamlined internal clinic management, and consistent data synchronization across platforms. 🌟 Key Features 🤖 AI-Powered Specialized Agents: Distinct agents handle WhatsApp patient support, appointment confirmations, and internal rescheduling tasks. 📱 Omnichannel Communication: Handles patient interactions via WhatsApp and staff commands via Telegram. 📅 Google Calendar Appointment Management: Full synchronization for creating, updating, canceling, and confirming appointments. 📋 Task Management with Google Tasks: Manages shopping lists and administrative tasks efficiently through staff Telegram requests. 🔔 Automated Appointment Reminders: Daily-triggered system proactively sends WhatsApp confirmations to patients for next-day appointments. 🖼️ Intelligent Media Processing: Transcribes audios, extracts text from images, and processes documents using OpenAI and OpenRouter AI models. 🛡️ Escalation to Human Support: Automatically detects sensitive or urgent cases and escalates them to a human agent when needed. 🏥 Use Cases Patient Communication:** Respond to inquiries, schedule, reschedule, and confirm appointments seamlessly via WhatsApp. Internal Clinic Operations:** Allow staff to modify appointments or add shopping list reminders directly from Telegram. Appointment Confirmation System:** Automatically contacts patients one day prior to appointments for confirmation or rescheduling. Task and Reminder Management:** Keeps clinic operations organized through automatic task management with Google Tasks. 🛠️ Technical Implementation WhatsApp Patient Interaction Flow Webhook Reception:** Incoming WhatsApp messages captured via Evolution API webhook. Message Classification:** Intelligent routing of messages based on content type (text, image, audio, document). Media Content Processing:** Audios: Download, convert, and transcribe via OpenAI Whisper. Images: Analyze and extract text/descriptions with OpenAI Vision model. Patient Request Handling:** Specialized WhatsApp assistant responds appropriately using AI prompts. Outbound Message Formatting:** Ensures messages comply with WhatsApp format standards. Message Delivery:** Sends responses back via Evolution API. Telegram Staff Management Flow Telegram Webhook Reception:** Captures messages from authorized staff accounts. Internal Assistant Processing:** Appointment Rescheduling: Identifies and updates appointments through MCP Google Calendar. Task Creation: Adds new entries to the clinic's shopping list using Google Tasks. Notifications and Confirmations:** Sends confirmations back to staff through Telegram. Appointment Reminder System Daily Trigger Activation:** Fires every weekday at 08:00 AM. Calendar Scraping:** Lists next day's appointments from Google Calendar. Patient Contact:** Sends WhatsApp confirmation messages for each appointment. Response Management:** Redirects confirmation or rescheduling replies to appropriate agents. ⚙️ Setup Instructions Import the Workflow n8n → Workflows → Import from File → Upload this JSON file. Configure Credentials Evolution API (WhatsApp Communication) Telegram Bot API (Staff Communication) Google Calendar OAuth2 (Appointment Management) Google Tasks OAuth2 (Task Management) OpenAI and OpenRouter APIs (AI Agents) PostgreSQL Database (Chat Memory) Set Sensitive Variables Replace placeholder values: {sua instância aqui} → Evolution API instance name {número_whatsapp} → WhatsApp numbers {url_do_servidor} → Server URLs {a sua apikey aqui} → API keys {seu_calendario} → Google Calendar ID Customize AI Prompts Adjust system prompts to fit your clinic’s tone, service style, and patient communication guidelines. Set clinic operating hours, escalation rules, and cancellation procedures in AI prompts. Activate and Test Simulate patient messages via WhatsApp. Test Telegram commands from staff members. Validate daily appointment reminders using the scheduled trigger. 🏷️ Tags Healthcare Clinic Management WhatsApp Integration Telegram Bot Appointment Scheduling Google Calendar Google Tasks AI Agents n8n Automation 📚 Technical Notes PostgreSQL is used for persistent chat memory across sessions. Multiple AI Models Used: OpenAI GPT-4.1-nano OpenAI GPT-4.1-mini Google Gemini 2.0 and 2.5 Full media content processing supported (audio, image, text). Compliant escalation workflows ensure patient safety and proper handoff to human staff when necessary. All sensitive patient data are securely stored inside calendar event descriptions for easy retrieval by agents. 📜 License This workflow is provided under the MIT License. Feel free to adapt and customize it for your clinic’s specific needs.

This n8n automation lets you build a complete AI-powered task management system that integrates Telegram, Google Sheets, and GPT-4o mini to help users easily manage to-do lists and receive daily task reminders. Users can interact with the system via Telegram, while the AI assistant (powered by GPT-4o mini) processes commands naturally, updates a central Google Sheet, and ensures scheduled reminders are sent for pending tasks. ✨ Key Features ✅ Add, list, update, complete, or delete tasks via Telegram ✅ AI-powered conversational responses using GPT-4o ✅ All tasks stored and synced in Google Sheets ✅ Daily scheduled task summary and pending reminders sent to Telegram ✅ Friendly, human-like assistant responses ✅ Fully configurable and easy to set up 🛠️ Workflow Functionality Breakdown User Interacts on Telegram Sends commands like: add buy groceries list tasks complete submit report delete dentist appointment AI-Powered Processing A GPT-4o agent processes user messages Ensures clear, friendly responses Determines task intent: add, update, delete, list, complete Google Sheets Sync Every operation is logged to Google Sheets Google Sheets acts as the master task database Sheet structure includes: Task Status (pending or done) Created At (timestamp) Due Date (optional) Notes (optional) Scheduled Daily Task Summary At 9 PM daily, the workflow: Fetches tasks from Google Sheets Generates a warm, conversational summary via GPT-4o Sends the summary to the user on Telegram Automated Reminders Checks for pending tasks due today Sends reminder messages to Telegram ✅ Prerequisites Before setting up the workflow, ensure you have: ✔️ An n8n instance (Cloud or self-hosted) ✔️ A Telegram Bot Token ✔️ Access to Google Sheets API (OAuth2 credentials) ✔️ An OpenAI API Key with GPT-4o access ✔️ A Google Sheet structured as per the specification below 📝 Google Sheet Structure Your Google Sheet should have the following columns: | Column Name | Description | | -------------- | ---------------------------------------------------- | | Task | Short task description | | Status | pending or done | | Created At | Date & time task was created (YYYY-MM-DD HH:mm:ss) | | Due Date | (Optional) When task is due (YYYY-MM-DD HH:mm:ss) | | Notes | (Optional) Additional details | Important: The first row should be the header row with these exact column names. 🔧 Setup Instructions Telegram Bot Setup Create a bot via BotFather Obtain the Bot Token Connect Telegram Trigger and Telegram Send nodes using your Bot Token in n8n Google Sheets API Setup Follow n8n Google Sheets integration guide Set up OAuth2 credentials Provide access to your task Google Sheet OpenAI API Setup Obtain an API key from OpenAI Ensure GPT-4o mini access is enabled Add OpenAI credentials to relevant nodes Sheet Linking Replace the Google Sheet ID in the workflow with your own Confirm sheet names and column structure match exactly Schedule Configuration (Optional) Adjust the daily summary time (Schedule Trigger node) as desired ⚙️ Configuration Options 🔧 Adjust AI prompt instructions for tone/style 🔧 Change reminder times in the schedule trigger 🔧 Customize Google Sheet columns if needed (update mappings accordingly) 🔧 Add multi-user support with chat ID checks (advanced) 📂 Files Included Full n8n JSON workflow ready to import 💡 Tips You can extend this with Slack, WhatsApp, or Email reminders Combine with Notion, ClickUp, or CRM integrations for more powerful task management Consider adding a "Priority" column for advanced sorting Ready to stay organized with AI-powered task management? Import this workflow, link your accounts, and your Telegram assistant is good to go! 🚀

🤖 This n8n workflow creates an intelligent Telegram bot that processes multiple types of messages and provides automated responses using AI capabilities. The bot serves as a personal assistant that can handle text, voice messages, and images through a sophisticated processing pipeline. Core Components Message Reception and Validation 📥 🔄 Implements webhook-based message reception for real-time processing 🔐 Features a robust user validation system that verifies sender credentials 🔀 Supports both testing and production webhook endpoints for development flexibility Message Processing Pipeline ⚡ 🔄 Uses a smart router to detect and categorize incoming message types 📝 Processes three main message formats: 💬 Text messages 🎤 Voice recordings 📸 Images with captions AI Integration 🧠 🤖 Leverages OpenAI's GPT-4 for message classification and processing 🗣️ Incorporates voice transcription capabilities for audio messages 👁️ Features image analysis using GPT-4 Vision API for processing visual content Technical Architecture Webhook Management 🔌 🌐 Maintains separate endpoints for testing and production environments 📊 Implements automatic webhook status monitoring ⚡ Provides real-time webhook configuration updates Error Handling ⚠️ 🔍 Features comprehensive error detection and reporting 🔄 Implements fallback mechanisms for unprocessable messages 💬 Provides user feedback for failed operations Message Classification System 📋 🏷️ Categorizes incoming messages into tasks and general conversation 🔀 Implements separate processing paths for different message types 🧩 Maintains context awareness across message processing Security Features User Authentication 🔒 ✅ Validates user credentials against predefined parameters 👤 Implements first name, last name, and user ID verification 🚫 Restricts access to authorized users only Response System Intelligent Responses 💡 🤖 Generates contextual responses based on message classification

This automation template is an AI-powered booking agent that schedules property viewings and reserves restaurant tables for you, all coordinated through Telegram. It checks your calendar to avoid conflicts, places the calls on your behalf, negotiates times, confirms details, and delivers a crisp summary back to Telegram—hands-free. Note: This workflow uses a voice-calling provider for outbound calls, your calendar for availability, and Telegram for notifications. Usage costs depend on your telephony provider, call duration, and any API usage.* Who Is This For? Home Buyers & Renters:** Queue up and confirm viewings without calling around. Real Estate Agents & Property Managers:** Automate client viewing scheduling and confirmations. Relocation Specialists & Assistants:** Coordinate multi-property tours with calendar-aware logic. Busy Professionals:** Let AI handle restaurant bookings and post-viewing meals. Concierge & Ops Teams:** Standardize bookings with structured logs and Telegram updates. What Problem Does This Workflow Solve? Scheduling property viewings and restaurant tables often means endless calls, conflicts, and coordination. This workflow removes the friction by: AI Phone Calls on Your Behalf:** Natural voice calls to agents/venues to secure slots. Calendar-Aware Booking:** Checks your real-time availability and avoids overlaps. Preference Handling:** Location, budget, party size, time windows, language, and notes. Instant Telegram Summaries:** Clear outcomes (confirmed, waitlist, action needed) and quick next steps. Scalable Coordination:** Handles multiple properties and dining options with fallback logic. How It Works Intent Capture (Telegram): You send a simple message (e.g., “Viewings tomorrow 17:00–20:00, Eixample, 2-bed; table for 4 at 21:30 near there”). Calendar Check: Reads free/busy blocks and suggests viable windows or alternatives. AI Calling: Places outbound calls to listing agents/restaurants, negotiates slots, and confirms. Result Parsing: Extracts confirmed time, address, contact name, reservation name, and special instructions. Telegram Delivery: Sends a concise recap plus optional quick-reply buttons (confirm/cancel/map/nav). Optional Calendar Hold: Adds confirmed bookings to your calendar and blocks time. Logging (Optional): Writes outcomes to a sheet/database for tracking and analytics. Setup Telephony Provider: Connect your AI calling service (API key). Configure voice/language. Calendar Access: Link Google Calendar (or similar). Grant read (and optionally write) access. Telegram Bot: Create a bot with BotFather and add the bot token to credentials. Environment/Credentials: Store calling API token, calendar credentials, Telegram token in n8n. Preferences: Set defaults for viewings (areas, price range, time windows) and dining (party size, cuisine, budget). Test Run: Trial a single booking to verify calling, calendar sync, and Telegram delivery. Requirements Accounts:** n8n, telephony provider, calendar account, Telegram bot. API Keys:** Telephony API token, Calendar credentials, Telegram bot token. Permissions:** Calendar read (and write if auto-blocking); outbound calls enabled. Budget:** Telephony per-minute fees and minor API costs where applicable. Features Dual-Domain Booking:** Property viewings + restaurant tables in one flow. Calendar Intelligence:** Checks conflicts and proposes best-fit time slots. Telegram-Native UX:** Simple prompts, instant confirmations, and quick actions. Preference Profiles:** Time windows, neighborhoods, max budget, language, and notes. Fallbacks & Alternatives:** Suggests nearby times/venues if first choice is unavailable. Multilingual Voice:** Configure voice and language to match region/venue. Structured Logs:** Optional recording of outcomes for reporting and audits. Extensible:** Add CRM, maps, SMS, or payment links as needed. Automate your day from tours to tables: message your intent on Telegram, and let the AI book, confirm, and keep your calendar clean—so you just show up on time.

Telegram Personal Assistant with Long-Term Memory & Note-Taking This n8n workflow transforms your Telegram bot into a powerful personal assistant that handles voice, photo, and text messages. The assistant uses AI to interpret messages, save important details as long-term memories or notes in a Baserow database, and recall information for future interactions. 🌟 How It Works Message Reception & Routing Telegram Integration: The workflow is triggered by incoming messages on your Telegram bot. Dynamic Routing: A switch node inspects the message to determine whether it's voice, text, or photo (with captions) and routes it for the appropriate processing. Content Processing Voice Messages: Audio files are retrieved and sent to an AI transcription node to convert spoken words into text. Text Messages: Text is directly captured and prepared for analysis. Photos: If an image is received, the bot fetches the file (and caption, if provided) and uses an AI-powered image analysis node to extract relevant details. AI-Powered Agent & Memory Management The core AI agent (powered by GPT-4o-mini) processes the incoming message along with any previous conversation history stored in PostgreSQL memory buffers. Long-Term Memory: When a message contains personal or noteworthy information, the assistant uses a dedicated tool to save this data as a long-term memory in Baserow. Note-Taking: For specific instructions or reminders, the assistant saves concise notes in a separate Baserow table. The AI agent follows defined rules to decide which details are saved as memories and which are saved as notes. Response Generation After processing the message and updating memory/notes as needed, the AI agent crafts a contextual and personalized response. The response is sent back to the user via Telegram, ensuring smooth and natural conversation flow. 🚀 Key Features Multimodal Input:** Seamlessly handles voice, photo (with captions), and text messages. Long-Term Memory & Note-Taking:** Uses a Baserow database to store personal details and notes, enhancing conversational context over time. AI-Driven Contextual Responses:** Leverages an AI agent to generate personalized, context-aware replies based on current input and past interactions. User Security & Validation:** Incorporates validation steps to verify the user's Telegram ID before processing, ensuring secure and personalized interactions. Easy Baserow Setup:** Comes with a clear setup guide and sample configurations to quickly integrate Baserow for managing memories and notes. 🔧 Setup Guide Telegram Bot Setup: Create your bot via BotFather and obtain the Bot Token. Configure the Telegram webhook in n8n with your bot's token and URL. Baserow Database Configuration: Memory Table: Create a workspace titled "Memories and Notes". Set up a table (e.g., "Memory Table") with at least two fields: Memory (long text) Date Added (US date format with time) Notes Table: Duplicate the Memory Table and rename it to "Notes Table". Change the first field's name from "Memory" to "Notes". n8n Workflow Import & Configuration: Import the workflow JSON into your n8n instance. Update credentials for Telegram, Baserow, OpenAI, and PostgreSQL (for memory buffering) as needed. Adjust node settings if you need to customize AI agent prompts or memory management rules. Testing & Deployment: Test your bot by sending various message types (text, voice, photo) to confirm that the workflow processes them correctly, updates Baserow, and returns the appropriate response. Monitor logs to ensure that memory and note entries are correctly stored and retrieved. ✨ Example Interactions Voice Message Processing:** User sends a voice note requesting a reminder. Bot Response: "Thanks for your message! I've noted your reminder and saved it for future reference." Photo with Caption:** User sends a photo with the caption "Save this recipe for dinner ideas." Bot Response: "Got it! I've saved this recipe along with the caption for you." Text Message for Memory Saving:** User: "I love hiking on weekends." Bot Response: "Noted! I’ll remember your interest in hiking." Retrieving Information:** User asks: "What notes do I have?" Bot Response: "Here are your latest notes: [list of saved notes]." 🛠️ Resources & Next Steps Telegram Bot Configuration:** Telegram BotFather Guide n8n Documentation:** n8n Docs Community Forums:** Join discussions and share your customizations! This workflow not only streamlines message processing but also empowers users with a personal AI assistant that remembers details over time. Customize the rules and responses further to fit your unique requirements and enjoy a more engaging, intelligent conversation experience on Telegram!

This n8n workflow template is designed to integrate a DeepSeek AI agent with Telegram, incorporating long-term memory capabilities for personalized and context-aware responses. Here's a detailed breakdown: Core Features Telegram Integration Uses a webhook to receive messages from Telegram users. Validates user identity and message content before processing. AI-Powered Responses Employs DeepSeek's AI models for conversational interactions. Includes memory capabilities to personalize responses based on past interactions. Error Handling Sends an error message if the input cannot be processed. Model Options 🧠 DeepSeek-V3 Chat**: Handles general conversational tasks. DeepSeek-R1 Reasoning**: Provides advanced reasoning capabilities for complex queries. Memory Buffer Window**: Maintains session context for ongoing conversations. Quick Setup 🛠️ Telegram Webhook Configuration Set up a webhook using the Telegram Bot API: https://api.telegram.org/bot{my_bot_token}/setWebhook?url={url_to_send_updates_to} Replace {my_bot_token} with your bot's token and {url_to_send_updates_to} with your n8n webhook URL. Verify the webhook setup using: https://api.telegram.org/bot{my_bot_token}/getWebhookInfo DeepSeek API Configuration Base URL: https://api.deepseek.com Obtain your API key from the DeepSeek platform. Implementation Details 🔧 User Validation The workflow validates the user's first name, last name, and ID using data from incoming Telegram messages. Only authorized users proceed to the next steps. Message Routing Routes messages based on their type (text, audio, or image) using a switch node. Ensures appropriate handling for each message format. AI Agent Interaction Processes text input using DeepSeek-V3 or DeepSeek-R1 models. Customizable system prompts define the AI's behavior and rules, ensuring user-centric and context-aware responses. Memory Management Retrieves long-term memories stored in Google Docs to enhance personalization. Saves new memories based on user interactions, ensuring continuity across sessions.

🚀 ExamForge AI Automated PDF to Structured Exam Generator (MCQ + Essay + Answer Key) Generate structured exams automatically from text-based PDF materials using AI. ExamForge AI is a production-ready n8n workflow that transforms educational content into multiple-choice and essay questions with customizable difficulty and automatic answer key generation. ✨ Features 📄 Upload PDF via Webhook ✅ File size validation (default: max 5MB) 🧹 Automatic text cleaning 📏 Token length estimation & safety control 🎯 Customizable MCQ & Essay count 🧠 Difficulty selection (easy / medium / hard) 🌍 Language selection 📦 Structured JSON AI output 📝 Separate Exam PDF & Answer Key PDF 📲 Telegram delivery support (optional) 🔒 Parameter validation with structured error responses 🧠 What This Workflow Does Accepts PDF upload via Webhook Validates file size Extracts and cleans text content Estimates text length to prevent token overflow Validates required parameters: mcq_count essay_count difficulty language Sends structured prompt to OpenAI Parses JSON response Formats exam and answer key separately Converts both into PDF Sends results via Telegram or Webhook response ⚙️ Requirements Accounts Required OpenAI account (API key required) Telegram Bot (optional) PDF Munk (API key required) Environment n8n (self-hosted or cloud) Node version compatible with your n8n installation 🔑 Credentials Setup 1️⃣ OpenAI Add OpenAI credentials inside n8n Insert your API key Select preferred model (e.g., GPT-4o / GPT-4) 2️⃣ Telegram (Optional) Create a Telegram Bot via BotFather Insert Bot Token into Telegram node Add your Chat ID 🛠 Webhook Configuration Method: POST Content-Type: multipart/form-data Required Parameters | Parameter | Type | Required | Description | |--------------|--------|----------|-------------| | file | File | Yes | PDF document | | mcq_count | Number | Yes | Number of multiple-choice questions | | essay_count | Number | Yes | Number of essay questions | | difficulty | String | Yes | easy / medium / hard | | language | String | Yes | Output language | 📥 Example Request curl -X POST https://your-n8n-domain/webhook/examforge \ -F "[email protected]" \ -F "mcq_count=20" \ -F "essay_count=5" \ -F "difficulty=medium" \ -F "language=Indonesian"

Complete Video Documentation: https://youtu.be/O-bKlX3G7_4 Explanation WITH clean Video timestamps: Prerequisites: You need a rental agreement document, a BoldSign account (which has a free tier for testing) [00:44], a Google Sheet, and an n8n instance. BoldSign Setup: How to upload your agreement as a template, drag-and-drop the signature and text fields [01:13], get your API key [01:57], and set up a webhook to notify n8n when the agreement is signed or completed [02:13]. Workflow Logic: The video walks through the two main flows: Form Submission: A tenant fills out a form, which triggers n8n to save the details to Google Sheets and then call the BoldSign API to send the agreement to both the owner and tenant [03:01]. Completion: When both parties sign, BoldSign sends an event to the n8n webhook, which then filters for the "Completed" event and updates the Google Sheet [09:12]. Bonus: It also covers the Telegram bot setup, which lets an owner ask an AI about the status of agreements [11:52]. Prerequisites Before you build this, you'll need a few things: An n8n Instance: This can be on n8n.cloud or self-hosted. A Google Sheet: Create a new sheet with columns like Tenant Name, Tenant Email, Property, Estimated Rent per month, contract expiry, and agreement status. A BoldSign Account: An API Key. [01:57] A prepared rental agreement document (like a PDF or .docx). A BoldSign Template created from that document. You'll need to drag and drop the required fields (like signatures, dates, text boxes) onto the template. [01:13] A Telegram Bot (Optional): If you want the AI status checker, you'll need to create a bot with Telegram's BotFather to get an API token. A Google Gemini API Key (Optional): For the AI agent. In BoldSign, you would replace the {{...}} and [Date] parts with draggable form fields. Understanding the BoldSign API Node The key to sending the agreement is the Send aggrement to Tenant's Email node. This is a standard HTTP Request node, not a special BoldSign node. Method: POST URL: https://api.boldsign.com/v1/template/send?templateId=enter-your-template-id This is the official BoldSign API endpoint for sending a document based on a template. You must replace enter-your-template-id with the actual ID of the template you created in BoldSign [07:04]. Authentication: Header Auth BoldSign uses an API key in the header. You would create a credential in n8n where the Name is X-API-KEY and the Value is the secret API key you got from your BoldSign account [07:16]. Body: The jsonBody is the most important part [08:02]. It's a JSON object that tells BoldSign who to send the agreement to and what data to pre-fill. title: Sets the document title, like "Rental Agreement - 123 Main St". roles: This array defines the signers. One role is for the "Owner", dynamically filling their name and email from the form data. The second role is for the "Tenent" (Tenant), also filling their name and email. existingFormFields & mergeFields: This is where you dynamically insert data into the document. You map the data from your n8n form (like {{ $('Retrive Data from submitted form').item.json.address }}) to the id of the fields you created in your BoldSign template [08:16]. Workflow Explanation (From Scratch) This workflow is actually three separate flows that work together. Flow 1: New Tenant Onboarding (Form to Agreement) This is the main flow that kicks everything off when a new tenant is interested. Node: Tenant Form (Form Trigger) What it is: This node creates a public web form [03:10]. This is the starting point. From Scratch: You'd drag in a Form Trigger node. You add fields for "Your Name" (tenant's name) and "Your Email" (tenant's email). This Workflow: It also cleverly uses hidden fields [03:18] to store the owner's details, the property address, and the rent. This is a simple way to manage a single property. For multiple properties, you might use a database or a Google Sheet lookup. Node: Retrive Data from submitted form (Set) What it is: This node takes the messy data from the form and organizes it into clean, named variables (like tenant_name, address, estimated_rent) [05:25]. From Scratch: It's good practice to do this so the rest of your workflow is easy to read. It also calculates the expiry_date as one year from today. Node: Save the tenant Details (Google Sheets) What it is: This logs the new tenant in your Google Sheet before the agreement is sent [05:51]. From Scratch: You'd set this to "Append or Update" mode. It maps the variables ( tenant_name, tenant_email, etc.) to the correct columns in your sheet. Node: Send aggrement to Tenant's Email (HTTP Request) What it is: This is the BoldSign API call we just detailed. It takes all the data and sends the official signing request to both the owner's and tenant's email addresses [06:47]. Node: Update Agreement Status (Google Sheets) What it is: After the email is successfully sent, this node finds the row you just created (using the tenant's email as a key) and updates the agreement status column to "Pending Signing" [08:55]. This is great for tracking. Flow 2: Handling Signed Agreements (Webhook) This flow listens for activity. It doesn't run on a schedule; it waits for BoldSign to tell it something happened. Node: Webhook (Webhook Trigger) What it is: This node generates a unique URL [02:45]. You copy this URL and paste it into your BoldSign account's webhook settings [09:28]. From Scratch: Now, any time an event happens in BoldSign (like the document is viewed, signed, or completed), BoldSign will send a data packet to this URL, triggering the workflow. Node: If (If) What it is: This is a filter. The webhook gets all events, but we only care about the final one [10:49]. From Scratch: It's set to check the incoming data from the webhook. It looks at a header called x-boldsign-event and only continues if the value equals "Completed" [11:02]. This means it will ignore the "Signed" event (when just one person signs) and only proceed when both parties have signed. Node: Retrieve Tenant Email (Set) What it is: This node digs into the large JSON data packet from the webhook to find the tenant's email [11:17]. From Scratch: It uses a JavaScript .find() function to look through the signerDetails and pull the email for the person whose role was "Tenent" (Tenant). This gives us the unique key to update our spreadsheet. Node: Update Agreement Status as completed (Google Sheets) What it is: The final step\! Just like in Flow 1, this node finds the correct row in the Google Sheet (using the tenant's email) and updates the agreement status column to "Completed" [11:32]. Flow 3: AI-Powered Status Bot (Telegram) This is a bonus flow that lets the owner "chat" with the Google Sheet. Node: Telegram Trigger What it is: This listens for any new message sent to your Telegram bot [11:52]. Node: AI Agent (Langchain Agent) What it is: This is the "brain". It takes the message.text from the Telegram user [12:30]. From Scratch: Its prompt tells it to be a helpful assistant for rental agreements and to use the tools it's given. Node: Google Gemini Chat Model (Google Gemini) What it is: This is the Large Language Model (LLM) that the agent uses to think and form sentences. Node: Fetch Rental Agreements (Google Sheets Tool) What it is: This is not a regular node, but a Tool plugged into the AI Agent [12:35]. From Scratch: You give the AI agent this "tool" and tell it: "This tool, named 'Fetch Rental Agreements', can get all the data from the Google Sheet." When the user asks, "What's the status of Jane Doe's agreement?", the AI knows it must use this tool to get the sheet data before it can answer. Node: Send a text message (Telegram) What it is: This takes the final output from the AI Agent and sends it as a reply to the user in Telegram.

🧠 Automated Resume & Cover Letter Generator This project is an automation workflow that generates a personalized resume and cover letter for each job listing. 🚀 Features Automated Resume Crafting Generates an HTML resume from your data. Hosts it live on GitHub Pages. Converts it to PDF using Gotenberg and saves it to Google Drive. Automated Cover Letter Generation Uses an LLM to create a tailored cover letter for each job listing. Simple Input Database Agent Stores your experience in an n8n Data Table with the following fields: role, summary, task, skills, tools, industry. The main agent pulls this data using RAG (Retrieval-Augmented Generation) to personalize the outputs. One-Time GitHub Setup Initializes a blank GitHub repository to host HTML files online, allowing Gotenberg to access and convert them. 🧩 Tech Stack Gotenberg** – Converts HTML to PDF GitHub Pages** – Hosts live HTML files n8n** – Handles data tables and workflow automation LLM (OpenAI / Cohere / etc.)** – Generates cover letters Google Drive** – Stores the final PDFs ⚙️ Installation & Setup Create a GitHub Repository This repo will host your HTML resume through GitHub Pages. Set the Webhook URL In the notify-n8n.yml file, replace: role | summary | task | skills | tools | industry Create the n8n Data Table Add the following columns: role | summary | task | skills | tools | industry Create a Google Spreadsheet Add these columns: company | cover_letter | resume Install Gotenberg Follow the installation instructions on the Gotenberg GitHub repository: https://github.com/thecodingmachine/gotenberg Customize the HTML Template Modify the HTML resume to your liking. You can use an LLM to locate and edit specific sections. Add Authentication and Link Your GitHub Repo Ensure your workflow has permission to push updates to your GitHub Pages branch. Run the Workflow Once everything is connected, trigger the workflow to automatically generate and save personalized resumes and cover letters. 📝 How to Use Copy and paste the job listing description into the Telegram bot. Wait for the "Done" notification before submitting another job. Do not use the bot again until the notification appears. The process usually takes a few minutes to complete. ✅ Notes This workflow is designed to save time and personalize your job applications efficiently. By combining n8n automation, LLMs, and open-source tools like Gotenberg, you can maintain full control over your data while generating high-quality resumes and cover letters for every job opportunity.

This workflow automates plant care reminders and records using Google Sheets, Telegram, and OpenWeather API. It checks when each plant needs watering or fertilizing, sends a personalized reminder, and lets you confirm the task with a single button. When confirmed, it updates your Google Sheet and shows a confirmation HTML page. Who is it for? Home gardeners who want to automate watering and fertilizing schedules. Anyone managing a plant collection, greenhouse, or garden and wanting a lightweight, no-code reminder system. How it works Schedule Trigger starts the workflow once per day. Read Settings (Google Sheets) checks if vacation_mode is active. Read Plants (Google Sheets) retrieves all plants with columns such as id, plant, last_water, water_freq, etc. DecideDue (Code Node) compares today’s date with the last watering/fertilizing date and marks which plants are due. OpenWeather Request (optional) fetches local forecast for plants with coordinates and weather_delay = true. WeatherGate (Code Node) skips or delays watering if it recently rained or if rain is expected soon. Telegram Send Message sends a reminder for each due task. The message contains an inline button “Mark as done” linking to your webhook URL (opens confirmation window). Webhook – Confirm Done receives the click, update dates on Google Sheets, appends an optional log entry, and returns an HTML confirmation page. Setup steps Principal Workflow Spreadsheet- Create a Google Sheets document with: plants sheet: (id, plant, last_water, water_freq, last_fert, fert_freq, lat, lon, weather_delay , indoor, thirst_level) settings sheet: (vacation_mode, timezone) log sheet: (ts, plant_id, action message_id) Connect your Google account Configure the Schedule Trigger Enable weather integration (Get a free OpenWeather API key) and add it to the HTTP Request node parameters appid. https://openweathermap.org/api Configure Telegram with your credential and your chat id on {YOUR_CHAT_ID}. Configure "Send Dues" node with your custom url https://{YOUR_PROJECT_URL}.app.n8n... Setup steps Sub-Workflow (Webhook) Trigger: Configure your custom Path. Google Sheets: Connect your Google Account and Map sheets and columns. Requirements · A Google account with access to Google Sheets. . A spreadsheet containing three sheets with headers matching the field names used in the workflow. . A telegram bot. . OpenWeather API key for climate-aware watering. How to customise it Add plant photos: Include a photo URL column and show it in the Telegram message. Extend actions: Add pruning, repotting or any other periodic task by duplicating the existing logic.

Automated Invoice Creation & Team Notification with Jotform, Xero, Outlook, and Telegram This workflow automates the entire process of receiving a product/service order, checking or creating a customer in Xero, generating an invoice, emailing it, and notifying the sales team for example after sometime if no action has been taken yet (via Telegram) — all triggered by a form submission (via Jotform). How It Works Receive Submission Triggered when a user submits a form. Collects data like customer details, selected product/service, etc. Check If Customer Exists Searches Xero to determine if the customer already exists. ✅ If Customer Exists: Update customer details. ❌ If Customer Doesn’t Exist: Create a new customer in Xero. Create The Invoice Generates a new invoice for the customer using the item selected. Send The Invoice Automatically sends the invoice via email to the customer. Wait For Sometime Now we will wait for 30 seconds (by default, you can change it) and then get the invoice details from Xero Notify The Team Notifies the sales team for example via Telegram in case no action has been taken on the invoice and thus the team can act fast. Who Can Benefit from This Workflow? Freelancers** Service Providers** Consultants & Coaches** Small Businesses** E-commerce or Custom Product Sellers** Requirements Jotform webhook setup, more info here Xero credentials, more info here Make sure that products/services values in Jotform are exactly the same as your item Code in your Xero account Email setup, update email node (Send email), more info about Outlook setup here LLM model credentials Telegram credentials, more info here

Overview This workflow is an AI-powered Dental Appointment Assistant that automates appointment booking, rescheduling, and cancellations through Telegram or a Webhook. It uses intelligent agents to understand user intent, gather details, manage Google Calendar events, update records in Google Sheets, and send confirmation emails — creating a fully automated and customizable booking system suitable for any business, not just dental clinics. How It Works User Interaction The workflow can be triggered via Telegram, Webhook, and can easily be extended to WhatsApp or Facebook Messenger. The Planning Agent starts the conversation and collects essential details like: Appointment type (book, update, or delete) Date and time preference Service type or reason for visit Personal details (name, email, etc.) Based on the user’s intent, it routes the conversation to the appropriate booking flow. Booking Flow The Booking Agent handles the actual scheduling logic. It interacts with Google Calendar to: Create new events for fresh appointments Update existing events for reschedules Delete events for cancellations It ensures proper validation (availability, overlaps, etc.) before confirming any calendar changes. Post-Booking Actions Once the booking action is completed: The Mail and Sheet Entry Agent updates the Google Sheet with user details such as: Name Email Appointment date & time Status (booked/updated/cancelled) Short description of the appointment Sends an email confirmation to the user (for all actions — create, update, or delete). Sends a final message via Telegram (or chosen platform) confirming the status of the appointment. How to Use Trigger the workflow via Telegram or a Webhook URL. The AI assistant will guide the user step-by-step through booking, updating, or cancelling an appointment. Once confirmed, the system: Updates Google Calendar automatically Logs the appointment details in Google Sheets Sends an email and chat confirmation message to the user Requirements To deploy this workflow, you’ll need: n8n account** (self-hosted or cloud) Telegram Bot Token**, or other chat integrations (WhatsApp / Facebook) OpenAI or OpenRouter API Key** (for AI conversation agents) Google Calendar API access** (to manage events) Google Sheets API access** (to store booking records) Gmail / SMTP credentials** (to send confirmation emails)

🏥 AI secretary for scheduling with WhatsApp and Telegram > ⚠️ Community Disclaimer > This workflow is community-maintained and self-hosted. > It is not officially affiliated with or supported by n8n GmbH, OpenAI, or Google. > Users are responsible for their own configuration, security, and data compliance (e.g., HIPAA, LGPD, GDPR). > Always secure API keys and ensure compliance with your local privacy regulations. 🧠 Description This template deploys an AI-powered virtual medical secretary that automates appointment scheduling, rescheduling, and cancellations for clinics and healthcare professionals. It seamlessly integrates OpenAI for natural language understanding, Google Calendar for real-time booking, and Evolution API (WhatsApp) or Telegram for patient communication. Patients can chat naturally via WhatsApp or Telegram, receiving empathetic, professional, and human-like responses — while your calendar stays automatically synchronized in real time. 💡 What Problem Does This Solve? Managing appointments manually is time-consuming and error-prone, often requiring staff to handle repetitive tasks like checking availability, confirming times, or rescheduling. Traditional systems lack conversational capabilities, forcing patients to call or text staff directly. This template solves that by creating a conversational AI assistant that interacts with patients through familiar messaging channels, reducing administrative workload and ensuring accurate real-time scheduling through Google Calendar. ⚙️ Key Features 📅 Google Calendar Integration — Real-time synchronization of consultations and exams 🤖 AI Assistant Powered by OpenAI — Understands patient intent and replies naturally 💬 Multi-Channel Support — Works with WhatsApp (via Evolution API) and Telegram 🔄 Automated Workflow — Handles booking, rescheduling, and cancellations 🏥 Healthcare-Focused Design — Tailored for clinics, doctors, and medical secretaries ✅ Customizable Responses — Modify prompts, message flows, and confirmation texts ⏰ Reminders & Follow-ups — Reduce no-shows with automated notifications 🧩 Setup Instructions (Step-by-Step) Obtain Required Credentials: OpenAI API Key Google Calendar API Credentials (OAuth or Service Account) Evolution API Token (for WhatsApp) Telegram Bot Token (if using Telegram) Configure n8n Environment: Add your credentials under Settings → Credentials. Ensure your n8n instance has internet access to the APIs. Configure Node “Variables Config” & Update Nodes: Set nm_Clinic → Name of the clinic Set nm_Agent → Name of the AI agent Set ds_Address_Clinic → Address of the clinic Set nm_Health_Plan → Name of the health insurance provider Set nm_Evolution_Instance → Name of your Evolution API instance Set nm_City_Clinic → City where the clinic is located Customize the Conversation Flow: Edit OpenAI prompt nodes to match your clinic’s tone of voice. Update Google Calendar event templates with your preferred titles and descriptions. Deploy and Test: Test both WhatsApp and Telegram channels. Verify that appointments appear correctly in Google Calendar. Review conversation logs to fine-tune the responses. 🚀 Suggested Use Cases Ideal for: Clinics and medical offices wanting 24/7 automated appointment management Healthcare professionals reducing manual scheduling and follow-ups Multi-channel (WhatsApp + Telegram) patient interaction Reducing no-shows with reminders and confirmations Clinics seeking to modernize patient communication and optimize staff time This assistant ensures every patient request is handled naturally — while Google Calendar remains the single source of truth for scheduling.

Proxmox AI Agent with n8n and Generative AI Integration This template automates IT operations on a Proxmox Virtual Environment (VE) using an AI-powered conversational agent built with n8n. By integrating Proxmox APIs and generative AI models (e.g., Google Gemini), the workflow converts natural language commands into API calls, enabling seamless management of your Proxmox nodes, VMs, and clusters. Buy My Book: Mastering n8n on Amazon Full Courses & Tutorials: http://lms.syncbricks.com Watch Video on Youtube How It Works Trigger Mechanism The workflow can be triggered through multiple channels like chat (Telegram, email, or n8n's built-in chat). Interact with the AI agent conversationally. AI-Powered Parsing A connected AI model (Google Gemini or other compatible models like OpenAI or Claude) processes your natural language input to determine the required Proxmox API operation. API Call Generation The AI parses the input and generates structured JSON output, which includes: response_type: The HTTP method (GET, POST, PUT, DELETE). url: The Proxmox API endpoint to execute. details: Any required payload parameters for the API call. Proxmox API Execution The structured output is used to make HTTP requests to the Proxmox VE API. The workflow supports various operations, such as: Retrieving cluster or node information. Creating, deleting, starting, or stopping VMs. Migrating VMs between nodes. Updating or resizing VM configurations. Response Formatting The workflow formats API responses into a user-friendly summary. For example: Success messages for operations (e.g., "VM started successfully"). Error messages with missing parameter details. Extensibility You can enhance the workflow by connecting additional triggers, external services, or AI models. It supports: Telegram/Slack integration for real-time notifications. Backup and restore workflows. Cloud monitoring extensions. Key Features Multi-Channel Input**: Use chat, email, or custom triggers to communicate with the AI agent. Low-Code Automation**: Easily customize the workflow to suit your Proxmox environment. Generative AI Integration**: Supports advanced AI models for precise command interpretation. Proxmox API Compatibility**: Fully adheres to Proxmox API specifications for secure and reliable operations. Error Handling**: Detects and informs you of missing or invalid parameters in your requests. Example Use Cases Create a Virtual Machine Input: "Create a VM with 4 cores, 8GB RAM, and 50GB disk on psb1." Action: Sends a POST request to Proxmox to create the VM with specified configurations. Start a VM Input: "Start VM 105 on node psb2." Action: Executes a POST request to start the specified VM. Retrieve Node Details Input: "Show the memory usage of psb3." Action: Sends a GET request and returns the node's resource utilization. Migrate a VM Input: "Migrate VM 202 from psb1 to psb3." Action: Executes a POST request to move the VM with optional online migration. Pre-Requisites Proxmox API Configuration Enable the Proxmox API and generate API keys in the Proxmox Data Center. Use the Authorization header with the format: PVEAPIToken=<user>@<realm>!<token-id>=<token-value> n8n Setup Add Proxmox API credentials in n8n using Header Auth. Connect a generative AI model (e.g., Google Gemini) via the relevant credential type. Access the Workflow Import this template into your n8n instance. Replace placeholder credentials with your Proxmox and AI service details. Additional Notes This template is designed for Proxmox 7.x and above. For advanced features like backup, VM snapshots, and detailed node monitoring, you can extend this workflow. Always test with a non-production Proxmox environment before deploying in live systems. Start with n8n Learn n8n with Amjid Get n8n Book What is Proxmox

Video Guide I prepared a detailed guide that demonstrates the complete process of building a trading agent automation using n8n and Telegram, seamlessly integrating various functions for stock analysis. Youtube Link Who is this for? This workflow is perfect for traders, financial analysts, and developers looking to automate stock analysis interactions via Telegram. It’s especially valuable for those who want to leverage AI tools for technical analysis without needing to write complex code. What problem does this workflow solve? Many traders desire real-time analysis of stock data but lack the technical expertise or tools to perform in-depth analysis. This workflow allows users to easily interact with an AI trading agent through Telegram for seamless stock analysis, chart generation, and technical evaluation, all while eliminating the need for manual interventions. What this workflow does This workflow utilizes n8n to construct an end-to-end automation process for stock analysis through Telegram communication. The setup involves: Receiving messages via a Telegram bot. Processing audio or text messages for trading queries. Transcribing audio using OpenAI API for interpretation. Gathering and displaying charts based on user-specified parameters. Performing technical analysis on generated charts. Sending back the analyzed results through Telegram. Setup Prepare Airtable: Create simple table to store tickers. Prepare Telegram Bot: Ensure your Telegram bot is set up correctly and listening for new messages. Replace Credentials: Update all nodes with the correct credentials and API keys for services involved. Configure API Endpoints: Ensure chart service URLs are correctly set to interact with the corresponding APIs properly. Start Interaction: Message your bot to initiate analysis; specify ticker symbols and desired chart styles as required.

Transform simple queries into comprehensive, well-structured content with this n8n workflow that leverages Perplexity AI for research and GPT-4 for content transformation. Create professional blog posts and HTML content automatically while maintaining accuracy and depth. Intelligent Research & Analysis 🚀 Automated Research Pipeline Harnesses Perplexity AI's advanced research capabilities Processes complex topics into structured insights Delivers comprehensive analysis in minutes instead of hours 🧠 Smart Content Organization Automatically structures content with clear hierarchies Identifies and highlights key concepts Maintains technical accuracy while improving readability Creates SEO-friendly content structure Content Transformation Features 📝 Dynamic Content Generation Converts research into professional blog articles Generates clean, responsive HTML output Implements proper semantic structure Includes metadata and categorization 🎨 Professional Formatting Responsive Tailwind CSS styling Clean, modern HTML structure Proper heading hierarchy Mobile-friendly layouts Blockquote highlighting for key insights Perfect For 📚 Content Researchers Save hours of manual research by automating the information gathering and structuring process. ✍️ Content Writers Focus on creativity while the workflow handles research and technical formatting. 🌐 Web Publishers Generate publication-ready HTML content with modern styling and proper structure. Technical Implementation ⚡ Workflow Components Webhook endpoint for query submission Perplexity AI integration for research GPT-4 powered content structuring HTML transformation engine Telegram notification system (optional) Transform your content creation process with an intelligent system that handles research, writing, and formatting while you focus on strategy and creativity.

Description This workflow automates document processing using LlamaParse to extract and analyze text from various file formats. It intelligently processes documents, extracts structured data, and delivers actionable insights through multiple channels. How It Works Document Ingestion & Processing 📄 Monitors Gmail for incoming attachments or accepts documents via webhook Validates file formats against supported LlamaParse extensions Uploads documents to LlamaParse for advanced text extraction Stores original documents in Google Drive for reference Intelligent Document Analysis 🧠 Automatically classifies document types (invoices, reports, etc.) Extracts structured data using customized AI prompts Generates comprehensive document summaries with key insights Converts unstructured text into organized JSON data Invoice Processing Automation 💼 Extracts critical invoice details (dates, amounts, line items) Organizes financial data into structured formats Calculates tax breakdowns, subtotals, and payment information Maintains detailed records for accounting purposes Multi-Channel Delivery 📱 Saves extracted data to Google Sheets for tracking and analysis Sends concise summaries via Telegram for immediate review Creates searchable document archives in Google Drive Updates spreadsheets with structured financial information Setup Steps Configure API Credentials 🔑 Set up LlamaParse API connection Configure Gmail OAuth for email monitoring Set up Google Drive and Sheets integrations Add Telegram bot credentials for notifications Customize AI Processing ⚙️ Adjust document classification parameters Modify extraction templates for specific document types Fine-tune summary generation prompts Customize invoice data extraction schema Test and Deploy 🚀 Test with sample documents of various formats Verify data extraction accuracy Confirm notification delivery Monitor processing pipeline performance

Network Vulnerability Scanner (used NMAP as engine) with Automated CVE Report Workflow Overview This n8n workflow provides comprehensive network vulnerability scanning with automated CVE enrichment and professional report generation. It performs Nmap scans, queries the National Vulnerability Database (NVD) for CVE information, generates detailed HTML/PDF reports, and distributes them via Telegram and email. Key Features Automated Network Scanning**: Full Nmap service and version detection scan CVE Enrichment**: Automatic vulnerability lookup using NVD API CVSS Scoring**: Vulnerability severity assessment with CVSS v3.1/v3.0 scores Professional Reporting**: HTML reports with detailed findings and recommendations PDF Generation**: Password-protected PDF reports using Prince XML Multi-Channel Distribution**: Telegram and email delivery Multiple Triggers**: Webhook API, web form, manual execution, scheduled scans Rate Limiting**: Respects NVD API rate limits Comprehensive Data**: Service detection, CPE matching, CVE details with references Use Cases Regular security audits of network infrastructure Compliance scanning for vulnerability management Penetration testing reconnaissance phase Asset inventory with vulnerability context Continuous security monitoring Vulnerability assessment reporting for management DevSecOps integration for infrastructure testing Setup Instructions Prerequisites Before setting up this workflow, ensure you have: System Requirements n8n instance (self-hosted) with command execution capability Alpine Linux base image (or compatible Linux distribution) Minimum 2 GB RAM (4 GB recommended for large scans) 2 GB free disk space for dependencies Network access to scan targets Internet connectivity for NVD API Required Knowledge Basic networking concepts (IP addresses, ports, protocols) Understanding of CVE/CVSS vulnerability scoring Nmap scanning basics External Services Telegram Bot (optional, for Telegram notifications) Email server / SMTP credentials (optional, for email reports) NVD API access (public, no API key required but rate-limited) Step 1: Understanding the Workflow Components Core Dependencies Nmap: Network scanner Purpose: Port scanning, service detection, version identification Usage: Performs TCP SYN scan with service/version detection nmap-helper: JSON conversion tool Repository: https://github.com/net-shaper/nmap-helper Purpose: Converts Nmap XML output to JSON format Prince XML: HTML to PDF converter Website: https://www.princexml.com Version: 16.1 (Alpine 3.20) Purpose: Generates professional PDF reports from HTML Features: Password protection, print-optimized formatting NVD API: Vulnerability database Endpoint: https://services.nvd.nist.gov/rest/json/cves/2.0 Purpose: CVE information, CVSS scores, vulnerability descriptions Rate Limit: Public API allows limited requests per minute Documentation: https://nvd.nist.gov/developers Step 2: Telegram Bot Configuration (Optional) If you want to receive reports via Telegram: Create Telegram Bot Open Telegram and search for @BotFather Start a chat and send /newbot Follow prompts: Bot name: Network Scanner Bot (or your choice) Username: network_scanner_bot (must end with 'bot') BotFather will provide: Bot token: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz (save this) Bot URL: https://t.me/your_bot_username Get Your Chat ID Start a chat with your new bot Send any message to the bot Visit: https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates Find your chat ID in the response Save this chat ID (e.g., 123456789) Alternative: Group Chat ID For sending to a group: Add bot to your group Send a message in the group Check getUpdates URL Group chat IDs are negative: -1001234567890 Add Credentials to n8n Navigate to Credentials in n8n Click Add Credential Select Telegram API Fill in: Access Token: Your bot token from BotFather Click Save Test connection if available Step 3: Email Configuration (Optional) If you want to receive reports via email: Add SMTP Credentials to n8n Navigate to Credentials in n8n Click Add Credential Select SMTP Fill in: Host: SMTP server address (e.g., smtp.gmail.com) Port: SMTP port (587 for TLS, 465 for SSL, 25 for unencrypted) User: Your email username Password: Your email password or app password Secure: Enable for TLS/SSL Click Save Gmail Users: Enable 2-factor authentication Generate app-specific password: https://myaccount.google.com/apppasswords Use app password in n8n credential Step 4: Import and Configure Workflow Configure Basic Parameters Locate "1. Set Parameters" Node: Click the node to open settings Default configuration: network: Input from webhook/form/manual trigger timestamp: Auto-generated (format: yyyyMMdd_HHmmss) report_password: Almafa123456 (change this!) Change Report Password: Edit report_password assignment Set strong password: 12+ characters, mixed case, numbers, symbols This password will protect the PDF report Save changes Step 5: Configure Notification Endpoints Telegram Configuration Locate "14/a. Send Report in Telegram" Node: Open node settings Update fields: Chat ID: Replace -123456789012 with your actual chat ID Credentials: Select your Telegram credential Save changes Message customization: Current: Sends PDF as document attachment Automatic filename: vulnerability_report_<timestamp>.pdf No caption by default (add if needed) Email Configuration Locate "14/b. Send Report in Email with SMTP" Node: Open node settings Update fields: From Email: [email protected] → Your sender email To Email: [email protected] → Your recipient email Subject: Customize if needed (default includes network target) Text: Email body message Credentials: Select your SMTP credential Save changes Multiple Recipients: Change toEmail field to comma-separated list: [email protected], [email protected], [email protected] Add CC/BCC: In node options, add: cc: Carbon copy recipients bcc: Blind carbon copy recipients Step 6: Configure Triggers The workflow supports 4 trigger methods: Trigger 1: Webhook API (Production) Locate "Webhook" Node: Path: /vuln-scan Method: POST Response: Immediate acknowledgment "Process started!" Async: Scan runs in background Trigger 2: Web Form (User-Friendly) Locate "On form submission" Node: Path: /webhook-test/form/target Method: GET (form display), POST (form submit) Form Title: "Add scan parameters" Field: network (required) Form URL: https://your-n8n-domain.com/webhook-test/form/target Users can: Open form URL in browser Enter target network/IP Click submit Receive confirmation Trigger 3: Manual Execution (Testing) Locate "Manual Trigger" Node: Click to activate Opens workflow with "Pre-Set-Target" node Default target: scanme.nmap.org (Nmap's official test server) To change default target: Open "Pre-Set-Target" node Edit network value Enter your test target Save changes Trigger 4: Scheduled Scans (Automated) Locate "Schedule Trigger" Node: Default: Daily at 1:00 AM Uses "Pre-Set-Target" for network To change schedule: Open node settings Modify trigger time: Hour: 1 (1 AM) Minute: 0 Day of week: All days (or select specific days) Save changes Schedule Examples: Every day at 3 AM: Hour: 3, Minute: 0 Weekly on Monday at 2 AM: Hour: 2, Day: Monday Twice daily (8 AM, 8 PM): Create two Schedule Trigger nodes Step 7: Test the Workflow Recommended Test Target Use Nmap's official test server for initial testing: Target**: scanme.nmap.org Purpose**: Official Nmap testing server Safe**: Designed for scanning practice Permissions**: Public permission to scan Important: Never scan targets without permission. Unauthorized scanning is illegal. Manual Test Execution Open workflow in n8n editor Click Manual Trigger node to select it Click Execute Workflow button Workflow will start with scanme.nmap.org as target Monitor Execution Watch nodes turn green as they complete: Need to Add Helper?: Checks if nmap-helper installed Add NMAP-HELPER: Installs helper (if needed, ~2-3 minutes) Optional Params Setter: Sets scan parameters Execute Nmap Scan: Runs scan (5-30 minutes depending on target) Parse NMAP JSON to Services: Extracts services (~1 second) CVE Enrichment Loop: Queries NVD API (1 second per service) 8-10. Report Generation: Creates HTML/PDF reports (~5-10 seconds) Convert to PDF: Generates password-protected PDF (~10 seconds) 14a/14b. Distribution: Sends reports Check Outputs Click nodes to view outputs: Parse NMAP JSON**: View discovered services CVE Enrichment**: See vulnerabilities found Prepare Report Structure**: Check statistics Read Report PDF**: Download report to verify Verify Distribution Telegram: Open Telegram chat with your bot Check for PDF document Download and open with password Email: Check inbox for report email Verify subject line includes target network Download PDF attachment Open with password How to Use Understanding the Scan Process Initiating Scans Method 1: Webhook API Use curl or any HTTP client and add "network" parameter in a POST request. Response: Process started! Scan runs asynchronously. You'll receive results via configured channels (Telegram/Email). Method 2: Web Form Open form URL in browser: https://your-n8n.com/webhook-test/form/target Fill in form: network: Enter target (IP, range, domain) Click Submit Receive confirmation Wait for report delivery Advantages: No command line needed User-friendly interface Input validation Good for non-technical users Method 3: Manual Execution For testing or one-off scans: Open workflow in n8n Edit "Pre-Set-Target" node: Change network value to your target Click Manual Trigger node Click Execute Workflow Monitor progress in real-time Advantages: See execution in real-time Debug issues immediately Test configuration changes View intermediate outputs Method 4: Scheduled Scans For regular, automated security audits: Configure "Schedule Trigger" node with desired time Configure "Pre-Set-Target" node with default target Activate workflow Scans run automatically on schedule Advantages: Automated security monitoring Regular compliance scans No manual intervention needed Consistent scheduling Scan Targets Explained Supported Target Formats Single IP Address: 192.168.1.100 10.0.0.50 CIDR Notation (Subnet): 192.168.1.0/24 # Scans 192.168.1.0-255 (254 hosts) 10.0.0.0/16 # Scans 10.0.0.0-255.255 (65534 hosts) 172.16.0.0/12 # Scans entire 172.16-31.x.x range IP Range: 192.168.1.1-50 # Scans 192.168.1.1 to 192.168.1.50 10.0.0.1-10.0.0.100 # Scans across range Multiple Targets: 192.168.1.1,192.168.1.2,192.168.1.3 Hostname/Domain: scanme.nmap.org example.com server.local Choosing Appropriate Targets Development/Testing: Use scanme.nmap.org (official test target) Use your own isolated lab network Never scan public internet without permission Internal Networks: Use CIDR notation for entire subnets Scan DMZ networks separately from internal Consider network segmentation in scan design Understanding Report Contents Report Structure The generated report includes: Executive Summary: Total hosts discovered Total services identified Total vulnerabilities found Severity breakdown (Critical, High, Medium, Low, Info) Scan date and time Target network Overall Statistics: Visual dashboard with key metrics Severity distribution chart Quick risk assessment Detailed Findings by Host: For each discovered host: IP address Hostname (if resolved) List of open ports and services Service details: Port number and protocol Service name (e.g., http, ssh, mysql) Product (e.g., Apache, OpenSSH, MySQL) Version (e.g., 2.4.41, 8.2p1, 5.7.33) CPE identifier Vulnerability Details: For each vulnerable service: CVE ID**: Unique vulnerability identifier (e.g., CVE-2021-44228) Severity**: CRITICAL / HIGH / MEDIUM / LOW / INFO CVSS Score**: Numerical score (0.0-10.0) Published Date**: When vulnerability was disclosed Description**: Detailed vulnerability explanation References**: Links to advisories, patches, exploits Recommendations: Immediate actions (patch critical/high severity) Long-term improvements (security processes) Best practices Vulnerability Severity Levels CRITICAL (CVSS 9.0-10.0): Color: Red Characteristics: Remote code execution, full system compromise Action: Immediate patching required Examples: Log4Shell, EternalBlue, Heartbleed HIGH (CVSS 7.0-8.9): Color: Orange Characteristics: Significant security impact, data exposure Action: Patch within days Examples: SQL injection, privilege escalation, authentication bypass MEDIUM (CVSS 4.0-6.9): Color: Yellow Characteristics: Moderate security impact Action: Patch within weeks Examples: Information disclosure, denial of service, XSS LOW (CVSS 0.1-3.9): Color: Green Characteristics: Minor security impact Action: Patch during regular maintenance Examples: Path disclosure, weak ciphers, verbose error messages INFO (CVSS 0.0): Color: Blue Characteristics: No vulnerability found or informational Action: No action required, awareness only Examples: Service version detected, no known CVEs Understanding CPE CPE (Common Platform Enumeration): Standard naming scheme for IT products Used for CVE lookup in NVD database Workflow CPE Handling: Nmap detects service and version Nmap provides CPE (if in database) Workflow uses CPE to query NVD API NVD returns CVEs associated with that CPE Special case: nginx vendor fixed from igor_sysoev to nginx Working with Reports Accessing HTML Report Location: /tmp/vulnerability_report_<timestamp>.html Viewing: Open in web browser directly from n8n Click "11. Read Report for Output" node Download HTML file Open locally in any browser Advantages: Interactive (clickable links) Searchable text Easy to edit/customize Smaller file size Accessing PDF Report Location: /tmp/vulnerability_report_<timestamp>.pdf Password: Default: Almafa123456 (configured in "1. Set Parameters") Change in workflow before production use Required to open PDF Opening PDF: Receive PDF via Telegram or Email Open with PDF reader (Adobe, Foxit, Browser) Enter password when prompted View, print, or share Advantages: Professional appearance Print-optimized formatting Password protection Portable (works anywhere) Preserves formatting Report Customization Change Report Title: Open "8. Prepare Report Structure" node Find metadata object Edit title and subtitle fields Customize Styling: Open "9. Generate HTML Report" node Modify CSS in <style> section Change colors, fonts, layout Add Company Logo: Edit HTML generation code Add `` tag in header section Include base64-encoded logo or URL Modify Recommendations: Open "9. Generate HTML Report" node Find Recommendations section Edit recommendation text Scanning Ethics and Legality Authorization is Mandatory: Never scan networks without explicit written permission Unauthorized scanning is illegal in most jurisdictions Can result in criminal charges and civil liability Scope Definition: Document approved scan scope Exclude out-of-scope systems Maintain scan authorization documents Notification: Inform network administrators before scans Provide scan window and source IPs Have emergency contact procedures Safe Targets for Testing: scanme.nmap.org: Official Nmap test server Your own isolated lab network Cloud instances you own Explicitly authorized environments Compliance Considerations PCI DSS: Quarterly internal vulnerability scans required Scan all system components Re-scan after significant changes Document scan results HIPAA: Regular vulnerability assessments required Risk analysis and management Document remediation efforts ISO 27001: Vulnerability management process Regular technical vulnerability scans Document procedures NIST Cybersecurity Framework: Identify vulnerabilities (DE.CM-8) Maintain inventory Implement vulnerability management License and Credits Workflow: Created for n8n workflow automation Free for personal and commercial use Modify and distribute as needed No warranty provided Dependencies: Nmap**: GPL v2 - https://nmap.org nmap-helper**: Open source - https://github.com/net-shaper/nmap-helper Prince XML**: Commercial license required for production use - https://www.princexml.com NVD API**: Public API by NIST - https://nvd.nist.gov Third-Party Services: Telegram Bot API: https://core.telegram.org/bots/api SMTP: Standard email protocol Support For Nmap issues: Documentation: https://nmap.org/book/ Community: https://seclists.org/nmap-dev/ For NVD API issues: Status page: https://nvd.nist.gov Contact: https://nvd.nist.gov/general/contact For Prince XML issues: Documentation: https://www.princexml.com/doc/ Support: https://www.princexml.com/doc/help/ Workflow Metadata External Dependencies**: Nmap, nmap-helper, Prince XML, NVD API License**: Open for modification and commercial use Security Disclaimer This workflow is provided for legitimate security testing and vulnerability assessment purposes only. Users are solely responsible for ensuring they have proper authorization before scanning any network or system. Unauthorized network scanning is illegal and unethical. The authors assume no liability for misuse of this workflow or any damages resulting from its use. Always obtain written permission before conducting security assessments.

This Workflow simulates an AI-powered phone agent with RetellAI with two main functions: 📅 Appointment Booking – It can schedule appointments directly into Google Calendar. 🧠 RAG-based Information Retrieval – It provides answers using a Retrieval-Augmented Generation (RAG) system. For example, it can respond to questions such as store opening hours, return policies, or product details. The guide also explains how to purchase a dedicated phone number (with a +1 prefix) and link it to the AI agent. This setup is cost-effective, as it uses a FREE $10 credit to operate without additional charges in the beginning. ✨ Advantages 🕐 24/7 Availability** – The AI agent can answer calls and assist customers at any time. 🤖 Automation** – It reduces the workload on human staff by handling repetitive tasks like appointment scheduling and FAQ responses. 🔌 Easy Integration** – Built with n8n, it’s flexible and customizable for various platforms and tools. 💸 Low-cost Setup** – Using the free credit, businesses can get started without an upfront investment. 📦 Use Cases 🛍 E-commerce** – Answer common product questions or order inquiries. 🏬 Retail Stores** – Provide store hours, address info, and return policies. 🍽 Restaurants** – Take reservations or share menu information. 💼 Service Providers** – Book appointments or consultations. 📞 Any Local Business** – Offer phone support without needing a live operator. How It Works This Workflow simulates an AI-powered phone agent with two primary functions: Appointment Booking The workflow captures call events (e.g., call_ended or call_analyzed) and extracts key details (transcript, caller info, duration, etc.). Using OpenAI, it summarizes the conversation and parses structured data (e.g., names, contact info, dates). For scheduling, it converts user-provided dates into Google Calendar-compatible formats and creates events automatically. RAG-Based Information Retrieval When a query is received (e.g., store hours, product details), the workflow retrieves relevant information from a Qdrant vector store. An AI agent processes the query using the retrieved data and responds via a webhook, ensuring accurate, context-aware answers. Set Up Steps Prepare Qdrant Vector Store Create/refresh a Qdrant collection (via HTTP requests). Upload and vectorize documents (e.g., from Google Drive) using OpenAI embeddings. Configure RetellAI Agent Sign up for RetellAI, create an agent, and set the webhook URLs (n8n_call for call events, n8n_rag_function for RAG queries). Purchase a Twilio phone number and link it to the agent. n8n Workflow Setup Connect OpenAI, Qdrant, Google Calendar, and Telegram nodes with credentials. Customize prompts for summarization, date parsing, and RAG responses. Test the workflow to ensure data flows from call events → processing → actions (e.g., calendar bookings, Telegram alerts). Deploy Trigger the workflow via RetellAI webhooks during calls. Monitor outputs (e.g., call summaries in Telegram, calendar events). Note: Replace placeholders (e.g., QDRANTURL, COLLECTION, CHAT_ID) with actual values. 👉 Subscribe to my new YouTube channel. Here I’ll share videos and Shorts with practical tutorials and FREE templates for n8n. Need help customizing? Contact me for consulting and support or add me on Linkedin.

Automated n8n workflow: Receives videos via form, dubs/translates them to the selected languages, and—upon completion—uploads them to multiple social media channels and cloud drives, including Box, Dropbox, and YouTube, Telegram, Postiz (Facebook, Instagram, Tiktok, Reddit etc.) Workflows Via n8n form select files to dub for desired languages. Listen webhook and whenever dubbing finishes upload to desired platforms Used Stacks DubLab App (ApiKey, Webhook Setup Required) Optional (Upload) Telegram (Token Required) Box (Oauth2 Required) Dropbox (Oauth2 Required) Youtube (Oauth2 Required) Postiz (ApiKey Required)

Graceful Client Onboarding Concierge — Pro A warm, reliable onboarding system for small businesses and studios. Captures a form submission via webhook, creates a Client record in Notion, sends a concierge-style welcome email (with scheduler + optional contract link), optionally pings the owner on Telegram, mirrors the lead to Airtable/HubSpot, places a temporary Google Calendar hold, and includes a double opt-in confirmation link. Made for: coaches, designers, boutique agencies, e-commerce and service providers who want consistent follow-up without manual busywork. What it does (flow) Trigger:** Form ➜ POST /client-intake (or Manual Trigger for instant demo) Normalize & Score:** Map fields, auto-generate optInToken, compute score and tier Create in Notion:** Clients page (Name, Email, Package, Notes, Status, Score, Tier, OptInToken, Consent=false) Welcome Email:** industry-tuned copy + scheduler link (+ contract link for Growth/Pro/Custom packages) Owner Notify (optional):** Telegram ping with tier + score CRM Mirrors (optional):** Create Airtable row and/or HubSpot contact Calendar Hold (optional):** 30-min “Intro Hold” event (e.g., now + 48h) Double Opt-In:** /optin-confirm?token=...&email=... sets Consent=true & Status=Confirmed in Notion Error Handling:** On failure, send an email to the owner flowchart TD A[Form → Webhook /client-intake] --> B[Map Intake + Score Lead] B --> C[Notion: Create Client] B --> D[Build Welcome Email] D --> E[Email: Send Welcome] D --> F{Optional actions} F -->|Telegram| G[Telegram: Notify Owner] F -->|Airtable| H[Airtable: Create Row] F -->|HubSpot| I[HubSpot: Create Contact] F -->|Calendar Hold| J[Google Calendar: Create Hold] K[GET /optin-confirm] --> L[Find Notion by OptInToken] --> M[Update: Consent=true, Status=Confirmed] ER[Error Trigger] --> EH[Email Owner] Prerequisites Notion* database Clients* with properties: Name (title), Email (email), Package (select), Notes (rich text), Status (select), Score (number), Tier (select), OptInToken (text), Consent (checkbox) (CSV header provided in the Sticky note on canvas.) Email** (SMTP or Gmail OAuth) Optional:** Telegram Bot + Chat ID, Airtable (Base ID + Table), HubSpot (Contacts), Google Calendar (Calendar ID) Configuration (Set these in Set: User Config) NOTION_DB_ID = your Notion Clients DB ID FROM_EMAIL = sender address for welcome email OWNER_EMAIL = where error notifications go SCHEDULER_URL = booking link (Calendly, Once, etc.) BASE_URL = your public n8n domain (for opt-in link) CONTRACT_BASE_URL = (optional) proposal/contract URL base ENABLE_TELEGRAM = true|false TELEGRAM_CHAT_ID = (if enabled) ENABLE_AIRTABLE = true|false AIRTABLE_BASE_ID = (if enabled) AIRTABLE_TABLE = (if enabled) ENABLE_HUBSPOT = true|false ENABLE_CAL_HOLD = true|false CALENDAR_ID = "primary" or calendar ID HOLD_HOURS_FROM_NOW = number of hours (default 48) INDUSTRY = coaching | design_studio | ecommerce | services Credentials: Attach in node credentials panels (no secrets in JSON). How to use Import the workflow JSON. Open Set: User Config and fill required values (see above). Attach credentials: Notion + Email; optional Telegram/Airtable/HubSpot/Google Calendar. Run Manual Trigger to simulate an intake and verify: Notion page created Welcome email received Optional Telegram/CRM/Calendar actions Switch your form to the Production Webhook URL shown in the Client Intake Webhook node. Sample JSON (for testing the live webhook): {"name":"Ava Laurent","email":"[email protected]","package":"Growth","message":"Excited to begin!"} Double opt-in: The welcome email includes a link like https://YOUR-N8N-DOMAIN/webhook/optin-confirm?token=...&email=... Clicking it sets Consent=true and Status=Confirmed on the Notion record. Industry-tuned welcome copy Set INDUSTRY to control phrasing automatically: coaching – gentle goals/blocks framing design_studio – asset handoff + milestone language ecommerce – store link + quick-win focus services – general service language Submission compliance ✅ Manual Trigger path for instant demo ✅ Markdown sticky notes with clear H2 sections (README, Prereqs + CSV, Setup, Testing, Compliance, Changelog) ✅ No hardcoded API keys (credentials only) ✅ Timezone-safe ISO times for calendar hold ✅ Clear placeholders and copy-paste CSV headers included Troubleshooting (quick) No email:** attach Email creds; ensure FROM_EMAIL is allowed by your provider. No Notion page:** verify NOTION_DB_ID and property names; check Notion permissions. Webhook issues:* ensure your form sends JSON*; adapt mapping for form-encoded payloads. Opt-in link fails:** BASE_URL must be your public n8n domain; workflow must be active. Calendar hold not created:** set ENABLE_CAL_HOLD=true, attach Google Calendar creds, confirm CALENDAR_ID. Tags: onboarding, notion, email, crm, telegram, airtable, hubspot, calendar, double-opt-in, small business, concierge, women-led brands Version: v3 (see Changelog sticky on canvas)

This workflow integrates iOS Shortcuts with n8n to create a simple, automatic location-based reminder system. When the user arrives at a specified location, an automation in the Shortcuts app sends a webhook trigger to n8n. If the trigger matches predefined date and time conditions, n8n sends a Telegram message reminder to the user. This is perfect for repetitive weekly tasks like taking out the bins, customized with conditions for day and time. Key Features Location-Based Trigger: Uses iOS Shortcuts automation to start the workflow upon arrival at a specific location. Time and Day Validation: Logic in n8n checks current weekday and time to ensure reminders are sent only when appropriate. Telegram Integration: Sends reminders directly to your Telegram account using your bot. Minimal Setup: Uses native iOS and simple webhook setup in n8n. How It Works iOS Shortcut Trigger: When the user arrives at a designated location, the iOS shortcut sends a GET request to the n8n webhook. n8n Webhook Node: Receives the request and triggers the workflow. Conditional Check: An IF node checks if the current time is after 4:00 PM and it's a Wednesday (or any other configured condition). Telegram Node: If the condition passes, n8n sends a message like "Don't forget to take the bins out." to your Telegram bot. Setup Instructions Create a Telegram Bot: Use @BotFather to create a bot and obtain your bot token. Add Telegram API credentials in n8n with your bot token. Setup iOS Shortcut: Open the Shortcuts app on your iPhone. Go to the Automation tab → Tap + → Create Personal Automation. Choose Arrive → Select a location. Add action: Get Contents of URL. Method: GET, URL: your n8n Webhook URL (e.g. https://n8n.yourdomain.com/webhook/your-path). Save the automation. (You can also test the automation by pressing the Play button) Import Workflow into n8n: Load the provided workflow JSON. Set your webhook path and Telegram credentials. Adjust the logic in the IF node to your usecase. In my case, I check if today is Wednesday and after 4 PM until Midnight. Expose n8n Publicly: Ensure your n8n instance is publicly accessible via HTTPS so the shortcut can reach it. Customization Guidance Change Reminder Message: Modify the text inside the Telegram node to suit different reminders. Add More Conditions: Extend the logic to support more days, hours, or different trigger messages. Add Multi-Channel Output: Send reminders via email, SMS, or Slack in addition to Telegram. Use More Triggers: Expand to other types of shortcut triggers (e.g. NFC tag, leaving location, time of day). Security and Implementation Webhook Protection: Avoid using easily guessable webhook URLs. Secure Telegram Token: Store your bot token securely in n8n credentials, not in plain workflow text. Limit Shortcut Scope: Only trigger the shortcut at trusted locations or with secure iCloud sync. Automation Permissions: Ensure your iPhone allows shortcut automations to run without confirmation. Benefits Automates repetitive location-based reminders without user interaction. Provides a lightweight, native solution using iOS and n8n with no extra apps. Keeps you on track for routine tasks like garbage days, medicine reminders, or arrival-based tasks. Easily extendable for multiple locations or trigger conditions.

Automated Blog Post Review and Multi-Platform Publishing Workflow with RSS Feeds Description This workflow automates the process of generating, reviewing, and publishing blog posts across multiple platforms, now enhanced with support for RSS Feeds as a content source. It streamlines the management of blog posts by fetching content from RSS Feeds, formatting, storing, reviewing, templating, and publishing to platforms like LinkedIn and WordPress. The workflow is split into three key flows: Initial Flow**: Fetches content from RSS Feeds, prepares and stores blog post data, sends a review email with approval/rejection links. Approval Flow**: Handles review actions via a webhook to update the status in Google Sheets. Status Update Flow**: Monitors status changes and publishes approved posts. Target Audience Content creators, bloggers, and digital marketers. Teams managing multi-platform content publishing. Users familiar with n8n, Google Sheets, LinkedIn, and RSS Feeds. Problem Solved Manually managing blog posts, especially when sourcing content from RSS Feeds, can be time-consuming and error-prone This workflow addresses: Content Sourcing**: Fetches blog posts from RSS Feeds for automated processing Content Formatting**: Automatically formats and stores blog posts. Review Process**: Simplifies approval with email notifications and webhook triggers. Multi-Platform Publishing**: Publishes to LinkedIn, WordPress and optionally Medium) with delays to avoid rate limits Status Tracking**: Tracks approval and publishing status in Google Sheets. Setup Instructions Prerequisites n8n Instance**: Ensure you have an active n8n instance RSS Feed URL**: Identify an RSS Feed URL (e.g., a blog’s feed like https://example.com/feed) Google Sheets**: Create a spreadsheet with columns: Title, Blogpost, Publication Date, Keywords, Status, Published, Featured Image, articleUrl, Rendered Blog. Sheet Name: Posts Initial Add a dropdown for Status: Pending, Approved, Rejected. Gmail Account**: For sending review and notification emails. LinkedIn Account**: For publishing posts (OAuth credentials needed). Optional**: WordPress.com or Medium account for additional publishing. Customization Guidance Below is a detailed breakdown of each flow and node, including setup instructions. 🔹 Initial Flow: Fetch from RSS Feeds, Prepare, and Send for Review. Purpose: Fetches blog posts from an RSS Feed, formats them, extracts images, stores data, and sends a review email. Fetch from RSS Feed Type: RSS Feed Purpose: Retrieves blog posts from an RSS Feed Configuration: URL: https://example.com/feed (replace with your RSS Feed URL) Limit: 1 (or adjust based on your needs) Setup: Ensure the RSS Feed URL is valid and accessible; test the node to verify it fetches posts Set Fields Type: Set Purpose: Maps RSS Feed data to blog post fields Setup: Adjust field mappings based on your RSS Feed’s structure Format Blog Post for Storage Type: Code Purpose: Cleans up the blog post content. Extract Featured Image Type: Code Purpose: Extracts or generates a featured image URL. Setup: Ensure originalHtml contains image data; otherwise, it uses a placeholder. Store Blog Posts Initial Type: Google Sheets Purpose: Stores initial blog post data Setup: Ensure Google Sheets credentials are set up and the spreadsheet has the required columns. Set Fields for Email Type: Set Purpose: Prepares fields for the review email. Setup: Replace https://your-n8n-instance with your n8n instance URL. Prepare Email HTML Type: Code Purpose: Generates HTML email content with conditional image display Setup: No additional configuration needed Notify for Review (Gmail) Type: Gmail Purpose: Sends a review email with approval/rejection links 🔹 Approval Flow: Handle Review Actions Purpose: Updates the blog post status based on approval/rejection Webhook Trigger Type: Webhook Purpose: Triggers on approval/rejection link clicks Configuration: HTTP Method: GET Path: approve-post Response Code: 200 Response Data: {"message": "Status updated"} Setup: Ensure the webhook URL matches the one in Set Fields for Email Find Row to Update Type: Google Sheets Purpose: Retrieves all rows to find the matching blog post Filter Row by Title Type: Code Purpose: Filters the row matching the blog post title Setup: No additional configuration needed Update Status on Approval Type: Google Sheets Purpose: Updates the status to Approved or Rejected 🔹 Status Update Flow: Publish Approved Posts Purpose: Monitors status changes and publishes approved posts Google Sheets Trigger (Fetch Row) Type: Google Sheets Trigger Purpose: Triggers when a row’s status is updated Configuration: Event: Update Sheet Name: Posts Initial Output Fields: title, status, published, featuredImage, articleUrl Setup: Ensure Google Sheets credentials are set up Router (Check Status) Type: Router Purpose: Routes based on status and published state Configuration: Route 1: Approved and Not Published Condition: status equals Approved AND published equals NO Route 2: Rejected Condition: status equals Rejected Route 3: Pending Condition: status equals Pending Setup: No additional configuration needed Apply Blog Template Store Blog Posts Final Type: Google Sheets Purpose: Stores the final HTML content Configuration: Operation: Update Row Setup: Ensure the Rendered Blog column exists Loop Over Blog Posts Type: Split in Batches Purpose: Processes each blog post individually Configuration: Default settings Setup: No additional configuration needed Delay Between Posts Type: Wait Purpose: Adds a delay to avoid rate limits Configuration: Wait Type: Delay Amount: 1 second Setup: Adjust delay as needed for LinkedIn rate limits Publish to LinkedIn Type: LinkedIn Purpose: Publishes the blog post to LinkedIn Configuration: Operation: Share Post Author: urn:li:person:YOUR_PERSONAL_URN Setup: Set up LinkedIn OAuth credentials and replace YOUR_PERSONAL_URN with your LinkedIn URN Update Published State Type: Google Sheets Purpose: Updates the published status Configuration: Operation: Update Row Setup: Ensure the Published column exists Notify Team Type: Gmail Purpose: Notifies the team of successful publishing Configuration: The blog post "{{ $json.title }}" has been successfully published Setup: Set up Gmail credentials; replace [Link] with the LinkedIn URL if captured Notify Rejection (Gmail) (Route 2) Type: Gmail Purpose: Notifies on rejection The blog post "{{ $json.title }}" has been rejected Suggestions: Rewrite with more engaging content, adjust keywords, or verify facts Please update the status in Google Sheets if you wish to revise and resubmit Setup: Set up Gmail credentials Wait for Status Update (Route 3) Type: Wait Purpose: Delays for status recheck Configuration: Wait Type: Delay Duration: 24h Setup: Adjust delay as needed Conclusion This workflow streamlines blog post management with RSS Feeds, making it ideal for busy content creators and teams. Customize it by adding more platforms adjusting delays, or enhancing notifications. Share your feedback in the n8n community to help others benefit from this automation.

📌 AI Agent Template with Bright Data MCP Tool Integration This template enables natural-language-driven automation using Bright Data MCP tools. It extracts all available tools from MCP, processes the user’s query through an AI agent, then dynamically selects and executes the appropriate tool. ❓ Problem It Solves Traditional automation often requires users to understand APIs, interfaces, or scripts to perform backend tasks. The Bright Data MCP integration solves this by allowing natural language interaction, intelligently classifying user intent, and managing context-aware execution of complex operations—ideal for data extraction, customer support, and workflow orchestration. 🧰 Pre-requisites Before deploying this template, make sure you have: An active N8N instance (self-hosted or cloud). A valid OpenRouter API key (or another compatible AI model). Telegram bot and its API token Access to the Bright Data MCP API with credentials. Basic familiarity with N8N workflows and nodes. ⚙️ Setup Instructions Setup and obtain API token and other necessary information from Bright Data In your Bright Data account, obtain the following information: API token Web Unlocker zone name (optional) Browser Zone name (optional) Host SSE server from STDIO command The methods below will allow you to receive SSE (Server-Sent Events) from Bright Data MCP via a local Supergateway or Smithery ** Method 1: Run Supergateway in a separate web service (Recommended) This method will work for both cloud version and self-hosted N8N. Signup to any cloud services of your choice (DigitalOcean, Heroku, Hetzner, Render, etc.). For NPM based installation: Create a new web service. Choose Node.js as runtime environment and setup a custom server without repository. In your server’s settings to define environment variables or .env file, add: `API_TOKEN=your_brightdata_api_token WEB_UNLOCKER_ZONE=optional_zone_name BROWSER_ZONE=optional_browser_zone_name` Paste the following text as a start command: npx -y supergateway --stdio "npx -y @brightdata/mcp" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message Deploy it and copy the web server URL, then append /sse into it. Your SSE server should now be accessible at: https://your_server_url/sse For Docker based installation: Create a new web service. Choose Docker as the runtime environment. Set up your Docker environment by pulling the necessary images or creating a custom Dockerfile. In your server’s settings to define environment variables or .env file, add: `API_TOKEN=your_brightdata_api_token WEB_UNLOCKER_ZONE=optional_zone_name BROWSER_AUTH=optional_browser_auth` Use the following Docker command to run Supergateway: `docker run -it --rm -p 8000:8000 supercorp/supergateway \ --stdio "npx -y @brightdata/mcp /" \ --port 8000` Deploy it and copy the web server URL, then append /sse into it. Your SSE server should now be accessible at: https://your_server_url/sse For more installation guides, please refer to https://github.com/supercorp-ai/supergateway.git. ** Method 2: Run Supergateway in the same web service as the N8N instance This method will only work for self-hosted N8N. a. Set Required Environment Variables In your server's settings to define environment variables or .env file, add: API_TOKEN=your_brightdata_api_token WEB_UNLOCKER_ZONE=optional_zone_name BROWSER_ZONE=optional_browser_zone_name b. Run Supergateway in Background npx -y supergateway --stdio "npx -y @brightdata/mcp" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message Use the command above to execute it through the cloud shell or set it as a pre-deploy command. Your SSE server should now be accessible at: http://localhost:8000/sse For more installation guides, please refer to https://github.com/supercorp-ai/supergateway.git. Method 3: Configure via Smithery.ai (Easiest) If you don't want additional setup and want to test it right away, follow these instructions: Visit https://smithery.ai/server/@luminati-io/brightdata-mcp/tools to: Signup (if you are new to Smithery) Create an API key Define environment variables via a profile Retrieve your SSE server HTTP URL Import the Workflow Open N8N. Import the JSON workflow file included with this template. Update any nodes referencing external services (e.g., OpenRouter, Telegram). Setup Telegram Integration If you haven't setup a bot in Telegram, below is the instruction how to create one using BotFather: Search for @BotFather in Telegram and start a conversation with it. Send the command /newbot to create a new bot. You'll be prompted to enter a name and a unique username for your bot. BotFather will provide you with an access token, which you'll need to use to interact with the bot's API. Edit the HTTP Request node in the workflow. Configure the URL as follows: https://api.telegram.org/bot+your_telegram_bot_token+/setWebhook?url=+your_webhook_url Replace +your_telegram_bot_token+ with your actual Telegram bot token. Replace +your_webhook_url+ with the URL from the Webhook Trigger node in the workflow. This will set up Telegram to forward messages to your n8n agent. 🔄 Workflow Functionality (Summary) The user submits a message via chat. Memory** nodes retain context for multi-turn conversations. The mapped tool is executed and results are returned contextually. 🧠 Optional memory buffers and memory manager nodes keep the interaction context-aware. 🧩 Use Cases Data Scraping on Demand**: Launch scraping tasks via chat. Lead Generation Bots**: Enrich or validate leads with MCP tools. AI-Powered Customer Support**: Classify and answer queries with real-time data tools. Workflow Assistants**: Let teams run backend processes like lookups or report generation using plain language. 🛠️ Customization Classifier Prompt & Logic**: Tweak the AI’s prompt and tool-matching schema to better fit your use case. Memory Configuration**: Adjust retention policies and context depth. Tool Execution Sub-Workflow**: Extend for retries, logging, or chaining actions. Omni-Channel Support**: Connect via webhooks to chat interfaces like Slack, WhatsApp, Telegram, or custom UIs. ✅ Summary This template equips you with a powerful no-code/low-code AI agent that translates conversation into real-world action. Using Bright Data’s MCP tools through natural language, it enables teams to automate and scale data-driven tasks effortlessly.

Description This n8n workflow automates the entire process of creating and publishing AI-generated videos, triggered by a simple message from a Telegram bot (YTAdmin). It transforms a text prompt into a structured video with scenes, visuals, and voiceover, stores assets in MongoDB, renders the final output using Creatomate, and uploads the video to YouTube. Throughout the process, YTAdmin receives real-time updates on the workflow’s progress. This is ideal for content creators, marketers, or businesses looking to scale video production using automation and AI. You can see a video demonstrating this template in action here: https://www.youtube.com/watch?v=EjI-ChpJ4xA&t=200s How it Works Trigger: Message from YTAdmin (Telegram Bot) The flow starts when YTAdmin sends a content prompt. Generate Structured Content A Mistral language model processes the input and outputs structured content, typically broken into scenes. Split & Process Content into Scenes The content is split into categorized parts for scene generation. Generate Media Assets For each scene: Images: Generated using OpenAI’s image model. Voiceovers: Created using OpenAI’s text-to-speech. Audio files are encoded and stored in MongoDB. Scene Composition Assets are grouped into coherent scenes. Render with Creatomate A complete payload is generated and sent to the Creatomate rendering API to produce the video. Progress messages are sent to YTAdmin. The flow pauses briefly to avoid rate limits. Render Callback Once Creatomate completes rendering, it sends a callback to the flow. If the render fails, an error message is sent to YTAdmin. If the render succeeds, the flow proceeds to post-processing. Generate Title & Description A second Mistral prompt generates a compelling title and description for YouTube. Upload to YouTube The rendered video is retrieved from Creatomate. It’s uploaded to YouTube with the AI-generated metadata. Final Update A success message is sent to YTAdmin, confirming upload completion. Set Up Steps (Approx. 10–15 Minutes)Step 1: Set Up YTAdmin Bot Create a Telegram bot via BotFather and get your API token. Add this token in n8n's Telegram credentials and link to the "Receive Message from YTAdmin" trigger. Step 2: Connect Your AI Providers Mistral: Add your API key under HTTP Request or AI Model nodes. OpenAI: Create an account at platform.openai.com and obtain an API key. Use it for both image generation and voiceover synthesis. Step 3: Configure Audio File Storage with MongoDB via Custom API Receives the Base64 encoded audio data sent in the request body. Connects to the configured MongoDB instance (connection details are managed securely within the API- code below). Uses the MongoDB driver and GridFS to store the audio data. Returns the unique _id (ObjectId) of the stored file in GridFS as a response. This _id is crucial as it will be used in subsequent steps to generate the download URL for the audio file. My API code can be found here for reference: https://github.com/nanabrownsnr/YTAutomation.git Step 4: Set Up Creatomate Create a Creatomate account, define your video templates, and retrieve your API key. Configure the HTTP request node to match your Creatomate payload requirements. Step 5: Connect YouTube In n8n, add OAuth2 credentials for your YouTube account. Make sure your Google Cloud project has YouTube Data API enabled. Step 6: Deploy and Test Send a message to YTAdmin and monitor the flow in n8n. Verify that content is generated, media is created, and the final video is rendered and uploaded. Customization Options Change the AI Prompts Modify the generation prompts to adjust tone, voice, or content type (e.g., news recaps, product videos, educational summaries). Switch Messaging Platform Replace Telegram (YTAdmin) with Slack, Discord, or WhatsApp by swapping out the trigger and response nodes. Add Subtitles or Effects Integrate Whisper or another speech-to-text tool to generate subtitles. Add overlay or transition effects in the Creatomate video payload. Use Local File Storage Instead of MongoDB Swap out MongoDB upload http nodes with filesystem or S3-compatible storage. Repurpose for Other Platforms Swap YouTube upload with TikTok, Instagram, or Vimeo endpoints for broader publishing. **Need Help or Want to Customize This Workflow? If you'd like assistance setting this up or adapting it for a different use case, feel free to reach out to me at [email protected]. I'm happy to help!**

Transcribe audio messages from Telegram using Google Gemini for free. Send an audio file to your Telegram bot and get a full transcription using Gemini’s free model. Who is this template for? Anyone who needs quick and accurate transcriptions of audio messages. Perfect for: Creators and podcasters Coaches or educators People who receive a lot of audio on Telegram You can also adapt this workflow to transcribe audio from other sources, like WhatsApp, Google Drive, or direct uploads. How it works You send an audio file to your Telegram bot n8n downloads the file and converts it to text using Google Gemini The transcript is sent back to you on Telegram How to set up You’ll just need: A Telegram bot token A Google Gemini API key (free tier supported) The rest works out by itself. Check out my other templates 👉 https://n8n.io/creators/solomon/

🎬 Hollywood-Style Ads in Seconds (Fal.ai Sora-2 Version) Turn a single product image + short text description into a cinematic 8-second ad using Fal.ai’s Sora-2 Image-to-Video model. Perfect for ad agencies, marketing teams, and UGC creators who want to produce high-quality video ads instantly without editors or camera crews. 🧩 Problem It Solves Producing ad videos usually requires writers, editors, equipment, and several review cycles. This workflow replaces that process with a fully automated pipeline that generates studio-quality ads on demand. 🏢 Real Use Cases Ad Agencies Deliver Hollywood-style ads to clients instantly from a simple image upload. UGC Creators Create multiple ad variations in minutes instead of spending hours filming. SMB Marketing Generate product promo videos for websites, social media, and email campaigns. ⚙️ How It Works Your frontend sends image + text to the workflow webhook. Image is resized to 1280×720. GPT-5 Mini writes a cinematic Sora-2 compatible prompt. Fal.ai Sora-2 generates a realistic 8-second lifestyle ad. Workflow polls status and retrieves the final video. Sends the video URL back to your frontend. Optional: Sends a Telegram notification. 🧪 Requirements Fal.ai API Key Cloudinary Account (optional, for image storage) n8n (latest recommended version) Frontend (Lovable / AI Studio / Bubble / React) 🎨 Template Metadata Template Author: Sandeep Patharkar Category: Content Generation / Video Ads Difficulty: Intermediate Setup Time: 10–12 minutes 📬 Connect With Me LinkedIn → www.linkedin.com/in/sandeeppatharkar YouTube → https://www.youtube.com/@fasttrackaimastery Website → https://fasttrackaimastery.com Skool Community → https://www.skool.com/aic-plus

Promo Seeker automatically finds, verifies, and delivers active promo codes to users via Telegram or email using SerpAPI + Gemini (OpenRouter). Saves hours of manual searching and deduplicates results into an n8n Data Table for fast reuse. Why Use This Workflow? Time Savings: Reduces manual promo hunting from 2 hours to 5 minutes per query. Cost Reduction: Cuts reliance on paid scraping tools or manual services — potential savings of $50–$200/month. Error Prevention: Cross-references sources and enforces a 30‑day recency filter to reduce expired-code hits by ~60% vs single-source checks. Scalability: Handles hundreds of queries per day with Data Table upserts and optional scheduling for continuous discovery. Ideal For Marketing / Growth Managers:** Quickly discover competitor or partner discounts to promote in campaigns. Customer Support / Operations:** Respond to user requests with verified promo codes via Telegram or email. Affiliate / Content Teams:** Aggregate and maintain a clean promo feed for newsletters or site widgets. How It Works Trigger: Incoming request via Webhook, Telegram message, Google Form submission, or scheduled run. Data Collection: The LangChain agent uses SerpAPI search results and Gemini (OpenRouter) to locate recent promo codes. Processing: Filter for recency (last 30 days), extract code, value, terms, and expiry. Intelligence Layer: Gemini 2.5 Pro (OpenRouter) + LangChain agent structure and verify results, outputting a standardized JSON. Output & Delivery: If a code exists in the Data Table, notify the requester via Telegram and Gmail; otherwise, return results and upsert them into the Data Table. Storage & Logging: Results stored/upserted in an n8n Data Table to prevent duplicates and enable fast lookups. Setup Guide Prerequisites | Requirement | Type | Purpose | |-------------|------|---------| | n8n instance | Essential | Execute the workflow — import JSON to your n8n instance | | SerpAPI account | Essential | Web search results for promo code discovery | | OpenRouter (Gemini) account | Essential | Language model (Gemini 2.5 Pro) for extraction and verification | | Telegram Bot (BotFather) | Essential | Receive queries and send promo notifications | | Gmail OAuth2 | Essential | Send rich email notifications | | n8n Data Tables | Essential | Store and deduplicate promo code records | Get your n8n instance here: n8n instance — import the JSON and begin configuration. (Repeat link for convenience) n8n instance Installation Steps Import the JSON workflow into your n8n instance. Configure credentials (use n8n's Credentials UI — do NOT paste keys into nodes): SerpAPI: paste your SerpAPI API Key from your SerpAPI dashboard. OpenRouter API: paste your OpenRouter API Key (for Gemini 2.5 Pro). Telegram API: create bot via @BotFather, then add Bot Token to Telegram credentials. Gmail OAuth2: use n8n's Gmail OAuth2 credential flow and authorize the account. Update environment-specific values: Webhook path: /v1/promo-seeker (configured in the Webhook node) or replace with your preferred path. Data Table ID: point to your own Data Table Form/webhook recipient fields (email/chatId mappings). Customize settings: Adjust the LangChain agent prompt (Promo Seeker Agent) for different recency windows or regional focus. Change max results/limit on the Data Table node (default limit = 3). Test execution: Trigger via Telegram or a POST to the webhook with sample payload: { "platform":"example.com", "email":"[email protected]" } Confirm notifications arrive and Data Table rows are upserted. Technical Details Core Nodes | Node | Purpose | Key Configuration | |------|---------|-------------------| | SerpAPI | Fetch web search results | Provide credential; adjust search params in agent prompt | | Gemini 2.5Pro (OpenRouter) | Extract & verify promo details | Use OpenRouter credential; model google/gemini-2.5-pro | | Promo Seeker Agent (LangChain) | Orchestrates search + parsing | System prompt enforces 30‑day recency & result format | | Structured Output Parser | Validates agent output | JSON schema example for platform/code/value/terms/validUntil | | Data Table (Get row(s)) | Lookup existing promos | Filters by platform; limit = 3 | | If (Code Exist?) | Branching logic | Checks existence of platform field | | Data Table (Upsert row(s)) | Insert or update promo | Mapping from agent output to Data Table columns | | Telegram Trigger / Telegram | Receive queries & notify users | Webhook-based trigger; parse_mode = HTML for messages | | Gmail | Send rich HTML emails | Uses Gmail OAuth2 credential | | Webhook / Form Trigger | Alternate inputs | Webhook path /v1/promo-seeker and Form trigger for manual submissions | Workflow Logic On trigger, the Platform Set node normalizes the incoming query and receiver. Get row(s) checks Data Table for existing promos. If found: notify via Telegram and send Gmail (email template included). If not found: the Promo Seeker Agent runs SerpAPI searches, parses structured output, then Upsert row(s) saves results and notifications are sent. Structured Output Parser enforces correct JSON to avoid bad upserts. Customization Options Basic Adjustments Recency window: change the agent prompt to 7/14/30 days. Result limit: increase Data Table Get limit or change Upsert batch size. Advanced Enhancements Add Slack or Microsoft Teams notifications (moderate complexity). Add caching layer (Redis) to reduce repeated SerpAPI calls (advanced). Parallelize searches across multiple search engines (higher API usage & complexity). Performance & Optimization | Metric | Expected Performance | Optimization Tips | |--------|----------------------|-------------------| | Execution time | 8–30s per new search (depends on SerpAPI + LM response) | Reduce SerpAPI page depth; cache recent results | | API calls | 3–10 SerpAPI calls per complex query | Batch queries; use higher-quality search params | | Error handling | Agent retries on malformed output | Use retry nodes and set onError strategy for downstream nodes | Troubleshooting | Problem | Cause | Solution | |---------|-------|----------| | No results returned | Query too vague or rate-limited API | Improve query specificity; check SerpAPI quota | | Gmail send fails | OAuth scope not granted or token expired | Reconnect Gmail OAuth2 credential in n8n | | Telegram webhook not firing | Incorrect bot token or webhook setup | Recreate Telegram credential and check bot permissions | | Duplicate rows | Upsert mapping mismatch | Ensure promoCode mapping in Upsert matches structured output | | Agent returns malformed JSON | LM prompt too permissive | Tighten the agent system prompt and validate with Structured Output Parser | Created by: khaisa Studio Category: Marketing Automation Tags: promo-codes, coupons, serpapi, telegram, gmail, openrouter, data-tables Need custom workflows or help adapting this template? Contact us

Flexible News Curator - Multi-Sources, AI Analysis, Summaries, Translation, and Settable Channels 🎬 Overview The Flexible News Curator workflow can automate the collection, filtering, AI-driven analysis, and summarization of news from diverse sources of your interest. Using customizable search themes, RSS feeds, and (optional) video descriptions, it delivers concise, quality news summaries via configurable channels. This workflow is designed to help reduce information overload and keep you updated effortlessly. Click the image below to watch the video guide: ✨ Features Multi-Source News Aggregation**: Collect news from customizable RSS feeds, SerpAPI, and Video Channel Feeds (if enabled). AI-Powered News Selection \& Summarization**: Uses advanced AI agents (Mistral Cloud Chat Model by default) to select, analyze, and summarize top news. Quality Assurance Step**: Optional AI-powered filtering to improve news selection quality before analysis. Multi-Language Translation \& Tone Customization**: Translate summaries and customize tone for localized or tailored consumption. Multi-Channel Delivery**: Send outputs via Email, Telegram, WhatsApp, Webhook, or save to disk. Advanced Filtering**: Regex-based filtering on URLs, titles, and content to exclude unwanted articles. Sub-Workflow Architecture**: Modular handling of video transcripts, content retrieval, multi-theme searching, and more. Flexible Scheduling \& Trigger Options**: Supports schedule-based triggering, email (IMAP) triggers, and webhook-based activation. (Optional) Video Search**: Video content descriptions via Video Channel Feeds. 👤 Who is this for? This workflow benefits professionals, researchers, marketers, and anyone who needs to stay informed about specific news themes without wasting time on irrelevant information or reading too many news to select the most interesting ones. 💡 What problem does this solve? The workflow tackles the challenge of information overload by automatically filtering, summarizing, and delivering the essential news tailored to your interests and preferences. It integrates various data sources and channels for comprehensive yet efficient news consumption. Ideal use-cases include: Monitoring breakthroughs in research fields Receiving daily business opportunity updates (e.g., real estate) Lower the cognitive load required to follow your favorite news Translating news summaries to your chosen language 🔍 What this workflow does The workflow gathers news from RSS feeds, search engines, and social media, then: Filters duplicates and irrelevant content via custom regex filters and date ranges. Applies optional AI-powered Quality Assurance for headline evaluation. Selects top news articles with AI analysis focused on user-defined criteria and audience. Summarizes individual articles using AI summarization agents, ensuring structured, consistent outputs. Optionally translates and adjusts the tone of summaries. Distributes summaries through configured channels such as email, social media, messaging apps, or webhook calls. 🔄 Workflow Steps News Gathering Fetch news using RSS feeds, SerpAPI search, and optionally video channel feeds. Standardize output structures for seamless merging. Employ sub-workflows for video transcript retrieval and looping over custom RSS feed lists. Filtering Remove duplicates and news outside the specified date range. Exclude articles matching user-defined keywords via regex filters in URLs, titles, and content. Limit the number of news articles for AI analysis. News Selection Optionally invoke an AI Quality Assurance agent to pre-filter headlines. Aggregate news for AI analysis. Select and summarize top news articles with AI agents using customizable criteria. Parse AI responses into defined JSON structures to ensure consistent data. News Summarization Prepare individual article content. Summarize content with AI agents and validate structured output. Sender Preparation Combine general summaries with selected top news summaries. Format final summaries as text and HTML suitable for delivery. Optionally apply translation and tone adjustment. Sending Deliver summaries through selected channels (Email, Telegram, WhatsApp, Webhook). Optionally save the output to disk as JSON. 📌 Expected Input / Configuration The workflow is primarily configured via the Configure Workflow Args node or the Global Variables custom node, with these key parameters: | Parameter | Description | Type | | :-- | :-- | :-- | | search_themes | List of keywords/themes to search in SerpAPI | List of strings | | datetime_delta | Number of days back to include news from; e.g., 0 = today | Integer | | link_censor | Regex to exclude unwanted URLs | Regex string | | title_censor | Regex to exclude unwanted titles | Regex string | | content_censor | Regex to exclude unwanted content | Regex string | | use_qa | Flag to enable AI Quality Assurance for headline filtering | Boolean | | max_news_analysis | Max number of articles sent to News Analyzer | Integer | | qa_max_news | Number of headlines the QA Agent analyzes | Integer | | qa_max_top_news | Number of headlines selected by QA Agent | Integer | | qa_check_criteria | Criteria used by QA Agent to discard low-quality headlines | List of strings | | qa_select_criteria | Criteria used by QA Agent to rank/select the best headlines | List of strings | | news_focus | What the News Analyzer should focus on while selecting news | String | | news_target_audience | Target audience description for the News Analyzer | String | | news_criteria | Instructions for the News Analyzer to identify relevant news | List of strings | | language | Language for news summaries; triggers translation if not English | String | | translator_tone | Tone for translation (e.g., casual, professional) | String | | translator_notes | Additional instructions for the translator | String | | email_sender | Email address used for sending (via SMTP) | String | | email_recipients | Recipient email addresses (comma-separated) | String | | email_subject | Email subject line | String | | telegram_chat_id | Telegram chat ID for sending notifications | String | | phone_number | Phone number for WhatsApp messages | String | | rss_feeds | Custom list of RSS feeds (objects with link and needs_content_search properties) | JSON array of objects | | video_rss_feeds | Custom list of video RSS feeds | JSON array of objects | | enable_video_search | Enable/disable video search functionality | Boolean | | enabled_senders | List of enabled delivery channels (email, telegram, whatsapp, webhook, save-to-disk) | List of strings | Hint: To add or combine keywords in censors, use the pattern "keyword1|keyword2|keyword3". 📦 Expected Output Structured JSON containing a general news summary, top news with summaries, and metadata, suitable for your preferred channel delivery. 📌 Example An example that includes workflow parameters is provided in a note within the workflow. ⚙️ n8n Setup Used n8n version:** 1.100.1 n8n-nodes-serpapi:** 0.1.6 n8n-nodes-globals:** 1.1.0 LLM Model:** mistral-small-latest (API) IMAP:** imap.gmail.com (Port 993) Platform:** Podman 4.3.1 on Linux Date:** 2025-07-15 ⚡ Requirements to Use / Setup Self-hosted n8n instance. (This workflow contains community nodes that are only compatible with the self-hosted version of n8n.) Install necessary custom nodes: n8n-nodes-serpapi n8n-nodes-globals (or use Edit Field (Set) node instead) Configure all sub-workflows bundled within this template (see Sub-Workflows Guide). Provide valid credentials to nodes for SerpAPI, Telegram, WhatsApp, Mistral Cloud Chat API, and SMTP (for email). Custom RSS feed list must be set by you in the workflow args. You must either install the SerpAPI custom node or deactivate it. ⚠️ Notes, Assumptions \& Warnings The workflow timeout is set to 30 minutes by default; adjust depending on your setup and workload. Duplicate removal is applied, but occasional overlaps might still appear depending on feed sources. This workflow assumes familiarity with n8n, RSS feeds, API key management and regex expressions. Video search only works for configured video channels; remember to respect the rights of these channels. Using AI agents (Mistral or substitute LLMs) requires access to their API services and keys. Out-of-the-box customization is done via the Global Variables node or direct workflow argument edits. ℹ️ About Us This workflow was developed by the Hybroht team of AI enthusiasts and developers dedicated to enhancing the capabilities of AI through collaborative processes. Our goal is to create tools that harness the possibilities of AI technology and more. For questions, support, or feature requests, reach out via [email protected]. ❓ Questions & Issues We will answer any questions, provided they are related to this workflow. Please contact us if there is any bug/issue with this workflow. We will assist you. ⚖️ Warranty & Legal Notice You can view the full license terms here. Please review them before making your purchase. By purchasing this product, you agree to these terms.

Multi-Platform AI Sales Agent with RAG, CRM Logging & Appointment Booking This workflow acts as a 24/7 sales agent, engaging leads across WhatsApp, Instagram, Facebook, Telegram, and your website. It intelligently transcribes audio messages, answers questions using a knowledge base, and uses modular sub-workflows to manage your CRM in Airtable and book appointments in Google Calendar. Who Is It For? This solution is designed for service-based businesses that require a sophisticated, multi-channel lead management and appointment booking system. Agencies, consultants, and clinics** looking to automate lead qualification and booking across text and voice messages. Sales teams** needing a robust system that separates CRM and calendar logic for easier management and scalability. Advanced n8n users** who want a powerful, agent-based framework that can be easily customized and extended. Key Features & Workflow This system is composed of a parent workflow that orchestrates the conversation and calls specialized sub-workflows (agents) to perform specific tasks. Omni-Channel Engagement:* Greets and converses with leads naturally on Website Chat, WhatsApp, Instagram, Facebook, and Telegram*. Voice Message Transcription:* Automatically transcribes incoming audio/voice notes from WhatsApp and Telegram* into text, allowing the AI to understand and respond without manual intervention. RAG-Powered Intelligence:* The AI agent draws answers from your dedicated PostgreSQL Knowledge Base (RAG)*, providing accurate information about your services, pricing, and process. A built-in tool allows you to load new knowledge documents from Google Drive. Modular CRM Agent (Sub-Workflow):* When the conversation requires CRM actions (like creating a contact or updating an opportunity), the main agent calls a dedicated Airtable CRM sub-workflow* to handle the task. Modular Calendar Agent (Sub-Workflow):* To book appointments, the main agent calls a separate Google Calendar sub-workflow*, which manages event creation, updates, and deletions. What You'll Need This workflow framework requires credentials for the following services: An AI provider (OpenAI is used for the main agent, transcription, and embeddings). PostgreSQL** database with the pgvector extension (for RAG and chat memory). Airtable** account (for the CRM sub-workflow). Google Calendar** account (for the Calendar sub-workflow). Telegram Bot** credentials. A Meta Developer Account (for WhatsApp, Instagram & Facebook). (Optional) Google Drive for loading knowledge documents. (Optional) Google Gemini for embeddings. How to Set It Up This is a modular system. You must set up the sub-workflows first. Deploy Sub-Workflows: Create two new, separate workflows using the provided templates for the CRM Agent and the Calendar Agent. Configure the credentials (Airtable, Google Calendar) within those workflows, then save and activate them. Link Sub-Workflows in Main Workflow: Return to this main workflow. In the "CRM Agent" and "Consultation Agent" tool nodes, select the new workflows you just created from the dropdown list. Configure Main Credentials: Securely add the remaining credentials (OpenAI, PostgreSQL, Telegram, and your Meta App) in this main workflow. Personalize the AI Agent: In the "Update Agent Details" node, fill in your business name, the agent's persona name, and your key services to customize the AI's personality. Load Your Knowledge (Optional): To populate the RAG database, use the manual trigger path starting with "When clicking ‘Execute workflow’" to download a document from Google Drive and insert it into your PostgreSQL vector store. Activate: Configure your channel-specific details (e.g., Phone Number ID in WhatsApp nodes), save the workflow, and activate it. Demo CRM Table: View on Airtable

What this workflow does This n8n workflow collects client feedback through a form (Tally, Typeform, or Google Forms) and uses AI to analyze it. It automatically generates a summary of the positive points, highlights areas for improvement, and drafts a short social media post based on the feedback. Ideal for: Freelancers Customer support teams Online service providers Coaches and educators Setup steps Connect your form tool to the Webhook node (POST method) and make sure it sends a feedback field. Add your DeepSeek (or other GPT-compatible) API key to the AI request node. Configure the email node with your SMTP credentials and desired recipient address. Replace the Telegram node with Slack, Buffer, or another integration if you prefer. (Optional) Customize the prompt in the function node for different tone/language. 🕐 Estimated setup time: ~15 minutes 💬 Sticky notes are included and clearly positioned to guide you. Technologies used n8n Webhook node n8n Function node DeepSeek Chat or compatible AI API Email node (SMTP) Telegram node (or other integration) Sticky Notes for setup guidance Use cases Analyze feedback from onboarding or satisfaction surveys Create ready-to-publish social media content from real customer praise Help support or marketing teams act on feedback immediately

Summarize YouTube Videos & Chat About Content with GPT-4o-mini via Telegram Description This n8n workflow automates the process of summarizing YouTube video transcripts and enables users to interact with the content through AI-powered question answering via Telegram. It leverages the GPT-4o-mini model to generate summaries and provide insights based on the video’s transcript. How It Works Input: The workflow starts by receiving a YouTube video URL. This can be submitted through: A Telegram chat message. A webhook (e.g., triggered by a shortcut on Apple devices). Transcript Extraction: The URL is processed to extract the video transcript using the custom youtubeTranscripter community node (available here). The transcript is concatenated into a single text and stored in a Google Docs document. Summarization: The GPT-4o-mini AI model analyzes the transcript and generates a structured summary, including: A general overview. Key moments. Instructions (if applicable). The summary is then sent back to the user via Telegram. Interactive Q&A: Users can ask questions about the video content via Telegram. The AI retrieves the stored transcript from Google Docs and provides accurate, context-based answers, which are sent back through Telegram. Setup Instructions To configure this workflow, follow these steps: Import the Workflow: Download the provided JSON template and import it into your n8n instance. Install the Community Node: Install the youtubeTranscripter community node via npm: npm install n8n-nodes-youtube-transcription-kasha Important: This node requires a self-hosted n8n instance due to its external dependencies. Configure Nodes: Webhook: Set up the webhook to receive YouTube URLs. Alternatively, configure the Telegram node if using Telegram as the input method. Google Docs: Provide valid credentials to enable writing the transcript to a Google Docs document. AI Model: Set up the GPT-4o-mini model for summarization and Q&A functionality. Test the Workflow: Send a YouTube URL via your chosen input method (Telegram or webhook) and confirm that the summary is generated and delivered correctly. Customization Language**: Adjust the AI prompts to generate summaries and answers in any desired language. Output Format**: Modify the summary structure by editing the prompt in the summarization node. Input Methods**: Replace the Telegram node with another messaging or input node to adapt the workflow to different platforms. Who Can Benefit? This template is perfect for: Content Creators**: Quickly summarize video content for repurposing or review. Students and Researchers**: Extract key insights from educational or informational videos efficiently. General Users**: Interact with video content via AI without needing to watch the full video. Problem Solved This workflow simplifies video content consumption by: Automating the extraction and summarization of key points. Enabling interactive Q&A to address specific questions without rewatching the video. Additional Notes Disclaimer**: The youtubeTranscripter community node is required and only works on self-hosted n8n instances due to its reliance on external services. Apple Users**: Enhance your experience with a custom shortcut to share YouTube videos directly to the workflow. Download the shortcut here.

🤖 Generate images via Telegram using an AI bot with a credit system and S3 storage A complete, production-ready Telegram bot for AI-powered image generation and editing, featuring a built-in credit system, payment integration, and cloud storage. ✨ Features 🎨 AI Image Generation Text-to-Image: Generate stunning images from text prompts using the **Nano Banana Pro Ultra model via WaveSpeed API Image-to-Image Editing**: Edit existing images by sending a photo with a caption describing the desired changes Multiple Resolutions: Support for both **4K and 8K output quality Flexible Aspect Ratios**: Choose from 10 different aspect ratios (1:1, 3:2, 2:3, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9, 21:9) 💳 Credit Management System Per-generation billing**: Different costs for 4K vs 8K resolution Balance tracking**: Real-time credit balance displayed to users Initial credits**: New users receive starter credits automatically Insufficient balance handling**: Graceful messages when credits run out Here's the adjusted payment section: 💰 Payment Integration (Mercado Pago PIX) > About PIX: PIX is Brazil's instant payment system, launched by the Central Bank of Brazil in 2020. It allows instant money transfers 24/7, 365 days a year, using QR codes or copy-paste codes. It has become the most popular payment method in Brazil due to its speed and zero fees for individuals. This workflow includes a fully integrated PIX payment flow as a reference implementation. You can adapt it to your local payment provider. Features: Multiple deposit options**: Pre-configured credit packages (R$ 3, R$ 6, R$ 10) QR Code generation**: Automatic PIX QR code sent directly to users via Telegram Copy-paste code**: PIX code provided for manual payment Webhook confirmation**: Real-time payment status updates via Mercado Pago webhooks Auto credit top-up**: Credits added automatically upon payment approval Payment status handling**: Supports approved, pending, and rejected states > 💡 Tip: To adapt this for other regions, replace the Mercado Pago nodes with your preferred payment gateway (Stripe, PayPal, etc.) while keeping the same credit update logic. ⚙️ User Configuration Resolution settings**: Users can set their preferred default resolution Aspect ratio preferences**: Save preferred aspect ratio for future generations Custom default prompts**: Set a default prompt that's automatically appended to all generations Persistent settings**: All preferences stored in n8n Data Tables 📦 Cloud Storage (S3/MinIO) Automatic upload**: Generated images are automatically uploaded to S3-compatible storage Persistent URLs**: Images remain accessible via permanent links Edit from storage**: Reference previously uploaded images for editing 🛠️ Tech Stack | Component | Technology | |-----------|------------| | Bot Platform | Telegram Bot API | | AI Generation | WaveSpeed API (Nano Banana Pro) | | Storage | S3-compatible (MinIO/AWS S3) | | Database | n8n Data Tables | | Payments | Mercado Pago PIX | | Automation | n8n | 📋 Prerequisites Before using this workflow, you'll need: Telegram Bot Token - Create a bot via @BotFather WaveSpeed API Key - Sign up at WaveSpeed S3-compatible Storage - MinIO, AWS S3, or any S3-compatible service Mercado Pago Account (optional) - For payment integration n8n Data Table - Create a table with the required schema 📊 Data Table Schema Create a Data Table with the following columns: | Column | Type | Description | |--------|------|-------------| | chat_id | String | Telegram chat ID (primary key) | | username | String | Telegram username | | status | String | Current user state in the flow | | credits | String | User's credit balance | | resolution | String | Preferred resolution (4k/8k) | | aspect_ratio | String | Preferred aspect ratio | | user_default_prompt | String | Custom default prompt | | number_images | Number | Total images generated | | number_videos | Number | Total videos generated | | demo_sended | Boolean | Welcome demo sent flag | ⚡ Quick Setup Import the workflow into your n8n instance Configure the Global Environment node with your settings: botName: Your bot's display name botToken: Your Telegram bot token dataTableId: Your n8n Data Table ID bucketName: Your S3 bucket name initialCredits: Credits given to new users generateImageCost4k: Cost per 4K image generateImageCost8k: Cost per 8K image Set up credentials: Telegram API credentials WaveSpeed API credentials S3 credentials Mercado Pago credentials (if using payments) Activate the workflow 🎮 Bot Commands | Command | Description | |---------|-------------| | /start | Initialize bot and receive welcome message | | menu | Return to main menu | | config | Open settings menu | | Any text | Generate image from prompt (when in generation mode) | | Photo + caption | Edit the photo based on the caption | 🔄 Workflow Flow User Message → Telegram Trigger → Route by Status ↓ ┌───────────────────┼───────────────────┐ ↓ ↓ ↓ New User Generate Image Edit Image ↓ ↓ ↓ Welcome Flow Check Credits Check Credits ↓ ↓ ↓ Create User Submit to WaveSpeed Upload to S3 ↓ ↓ ↓ Show Menu Poll for Result Submit Edit ↓ ↓ Download Image Poll for Result ↓ ↓ Send to User ←←←←←←←←←←←←←┘ 📝 Notes The workflow uses polling to check generation status - WaveSpeed processes may take up to 1 minute Credits are deducted when the task is submitted and refunded if generation fails All user states are managed through the Data Table for persistence across restarts 📄 License Free to use and modify. Attribution appreciated but not required.

How it works This workflow creates an intelligent document assistant called "Mookie" that can answer questions based on your uploaded documents. Here's how it operates: Document Ingestion:** The system can automatically load PDF files from Google Drive or accept PDFs uploaded directly through Telegram, then processes and stores them in a PostgreSQL vector database using Mistral embeddings Smart Retrieval:** When users ask questions via Telegram or a web chat interface, the AI agent searches through the stored documents to find relevant information using vector similarity matching Contextual Responses:** Using GPT-4 and the retrieved document context, Mookie provides accurate answers based solely on the ingested documents, avoiding hallucination by refusing to answer questions not covered in the stored materials Memory & Conversation:** The system maintains conversation history for each user, allowing for natural follow-up questions and contextual discussions Set up steps Estimated setup time: 30-45 minutes You'll need to configure several external services and credentials: Set up a PostgreSQL database with PGVector extension for document storage Create accounts and API keys for Azure OpenAI (GPT-4), Mistral Cloud (embeddings), and Google Drive access Connect your own LLM's if you don't have these credentials. Configure a Telegram bot and obtain API credentials for chat functionality Update webhook URLs throughout the workflow to match your n8n instance Test the document ingestion pipeline with sample PDFs Verify the chat interfaces (both Telegram and web) are responding correctly >The workflow includes approval mechanisms for PDF ingestion and handles both automated bulk processing from Google Drive and real-time document uploads through Telegram. Read the sticky notes provided in the template code for clear instructions.

🧠 Gwen – The AI Voice Marketing Agent Gwen is your intelligent voice-powered marketing assistant built in n8n. She combines the power of OpenAI, ElevenLabs, and automation workflows to handle content creation, image generation, and voice delivery — all from a single agent interface. This template shows a graphical illustration of how Gwen will work with subworkflows. These subworkflows are modular placeholders and need to be linked into Gwen for full deployment. ✨ What Gwen Can Do 📝 Generate Voice-Optimized Blog Posts Tailored for your target audience with engaging intros, real-time research, and polished structure. 🖼️ Create AI-Generated Visuals From simple concepts to detailed image prompts and Google Drive uploads. 🧑‍🎨 Edit Images On Demand Modify past images with a few words — powered by OpenAI's image editing API. 🔍 Search Image Database Quickly find past content using title or intent. 🧠 Think Tool Gwen uses this to clarify uncertain tasks or analyze complex requests. 🔊 Deliver Results in Natural Voice With ElevenLabs, Gwen transforms all responses into human-like audio, perfect for marketing, social content, or voice interfaces. 🛠️ Setup Instructions Estimated Time: 15–30 mins ✅ Step 1: Subworkflows Import These Workflows Blog Post, Create Image, Edit Image, Search Images Connect Them to Gwen Assign as tools inside the Gwen agent node (Langchain AI Agent in n8n). 🎙️ Step 2: Enable ElevenLabs Voice Agent Sign up or log in: https://try.elevenlabs.io Copy your API key In the ElevenLabs interface, create a new tool: Method: POST URL: https://your-n8n-domain/webhook/042cc868-28b7-42a2-ab65-bc2944fc5a54 Under Body Parameters, add: prompt → value type: LLM Prompt sessionId → value type: Dynamic variable, name: system__conversation_id Save and connect this tool to your ElevenLabs agent Run a test and check n8n execution logs to confirm Gwen’s voice integration is active 🔐 Step 3: Credentials to Set OpenAI – For text and image generation ElevenLabs – For voice output Tavily – For real-time research in blog generation Telegram – For sending content to users Google Sheets – To log all outputs like blogs and images

This n8n workflow captures Partnerstack events via a webhook, logs the event data into a Google Sheet, and sends a Telegram notification. How it Works: Webhook Node (Trigger): Listens for incoming POST requests. When an event occurs in Partnerstack (e.g., a new referral signs up), the workflow is triggered, capturing the event data. Append Row in Sheets Node: Takes the received Partnerstack event data and appends it as a new row to a designated Google Sheet. This creates a historical log of all captured events. Set Chat ID Node: Defines the specific Telegram chat ID where notifications will be sent. Send Notification Node (Telegram): Sends a message to the specified Telegram chat. The message content includes details from the Partnerstack event, providing real-time alerts. Setup Requirements: Partnerstack Postback: Configure a postback in Partnerstack (My account > Postbacks > Create a postback). Paste the URL provided by n8n's **Webhook node. Select the Partnerstack events you wish to track. Google Sheets Authentication**: Provide n8n with Google credentials that have write access to your target Google Sheet. Specify the sheet name. Telegram Integration**: You'll need a Telegram bot token (from BotFather) and the specific chat ID for the destination Telegram chat/channel. Additional Notes: This workflow efficiently automates logging of Partnerstack activities and provides immediate team awareness through Telegram notifications, streamlining event monitoring and response. 👉 Need Help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.

Notion Status-Based Alert Template Who is this for? Teams that live in Notion and want an instant ping to the right person when a task changes state. Perfect for content creators, project managers, or any small team that tracks work in a Notion database and prefers Slack / Telegram / Discord / e-mail notifications over manually checking a board. What problem does this solve? Polling Notion or checking a kanban board is slow and error-prone. This workflow watches a Notion database and routes an alert to specific people based on the item’s Status. One central map decides who gets pinged for “On Deck”, “In Progress”, “Ready for Review”, or “Ready to Publish”. How it works Trigger – choose either method Polling (Notion Trigger) – fires every minute. Push (Webhook) – register the production URL in a Notion automation and disable polling. Set Notion Page Info – copies Title, Status, URL, etc. into top-level fields. Switch (Status router) – routes the item down a branch that matches its Status. Set-Mention nodes – one per Status. Each node sets a single field mention (e.g. <@U123456>). Add or edit these nodes to map new statuses or recipients. Build Message – assembles a rich text block: Task title Status: <@UserIDs> <Notion URL|Open in Notion> Send nodes – Slack (active) + optional Telegram / WhatsApp / Discord / Email (disabled by default). All reuse the same {{$json.message}}. Setup steps Import this template into n8n. Connect credentials Notion API token Slack OAuth (and any other channels you enable) Edit the Status → Mention map Open each Set-Mention node and replace the placeholder with the real Slack ID / chat ID / phone / email. Copy a node for every extra Status you use, wire it to a new Switch output, and update the value. Set environment variables (recommended) NOTION_DB_ID, SLACK_CHANNEL, EMAIL_FROM, etc. Pick your trigger style Keep polling enabled or disable it and enable the Webhook, then register the webhook URL in Notion. Test – change a task’s Status in Notion → watch Slack for the ping. Example output > Title: “Draft blog post – AI productivity” > Status: Ready for Review > Slack message: > > Draft blog post – AI productivity > Status: Ready for Review > <@U789012> > <https://www.notion.so/…|Open in Notion> > Extending the flow Wire additional channels after Build Message—they all consume the same {{$json.message}}. Add richer logic (e.g. due-date reminders) in the Set Notion Page Info node. Verify Notion webhook signatures in a Function node if you rely on push triggers. This template is the leanest possible setup: one table of statuses → direct pings to the right people. Swap the IDs, flip on your favourite channels, and ship.

This workflow is designed for e-commerce store owners, operations managers, and developers who use Shopify as their e-commerce platform and want an automated way to track and analyze their order data. It is particularly useful for businesses that: Need a centralized view of all Shopify orders Want to analyze order trends without logging into Shopify Need to share order data with team members who don't have Shopify access Want to build custom reports based on order information What Problem Is This Workflow Solving? While Shopify provides excellent order management within its platform, many businesses need their order data available in other systems for various purposes: Data accessibility**: Not everyone in your organization may have access to Shopify's admin interface Custom reporting**: Google Sheets allows for flexible analysis and report creation Data integration**: Having orders in Google Sheets makes it easier to combine with other business data Backup**: Creates an additional backup of your critical order information What This Workflow Does This n8n workflow creates an automated bridge between your Shopify store and Google Sheets: Listens for new order notifications from your Shopify store via webhooks Processes the incoming order data and transforms it into a structured format Stores each new order in a dedicated Google Sheets spreadsheet Sends real-time notifications to Telegram when new orders are received or errors occur Setup Create a Google Sheet Create a new Google Sheet to store your orders Add a sheet named "orders" with the following columns: orderId orderNumber created_at processed processed_at json customer shippingAddress lineItems totalPrice currency Set Up Telegram Bot Create a Telegram bot using BotFather (send /newbot to @BotFather) Save your bot token for use in n8n credentials Start a chat with your bot and get your chat ID (you can use @userinfobot) Configure the Workflow Set your Google Sheet ID in the "Edit Variables" node Enter your Telegram chat ID in the "Edit Variables" node Set up your Telegram API credentials in n8n Configure Shopify Webhook In your Shopify admin, go to: Settings > Notifications > Webhooks Create a new webhook for "Order creation" Set the URL to your n8n webhook URL (from the "Receive New Shopify Order" node) Set the format to JSON How to Customize This Workflow to Your Needs Additional data**: Modify the "Transform Order Data to Standard Format" function to extract more Shopify data Multiple sheets**: Duplicate the Google Sheets node to store different aspects of orders in separate sheets Telegram messages**: Customize the text in Telegram nodes to include more details or rich formatting Data processing**: Add nodes to perform calculations or transformations on order data Additional notifications**: Add more channels like Slack, Discord, or SMS Integrations**: Extend the workflow to send order data to other systems like CRMs, ERPs, or accounting software Final Notes This workflow serves as a foundation that you can build upon to create a comprehensive order management system tailored to your specific business needs.

Fully Automated AI Email System for n8n: Triage, Summarize & Alert—Never Check Your Inbox Again! Fully Automated Email Intelligence: Triage, Summarize, Escalate & Alert—Never Check Your Inbox Again 🚀 Overview Turn every minute you waste in your inbox into revenue‑generating focus time. This is more than a workflow—it’s a profit engine disguised as an email assistant. ⚙️ Eliminate 90 % of inbox noise with AI triage and smart labeling. 🚨 Instantly surface high‑value leads & crises via Telegram push alerts—before they cost you. 📰 Digest newsletters in 60 seconds with bite‑size AI briefs that keep you ahead of the curve. 🤖 Hand off replies, snoozes, and archiving to a tireless autonomous agent that never slips. Set‑up takes 10 minutes. The payoff starts within the first hour—hours reclaimed, opportunities captured, and the calm certainty your inbox is handled perfectly, 24/7. 🎯 Who's It For? Startup Founders & CEOs – Stop wasting hours on inbox cleanup. Automatically surface leads, triage support, and escalate ops issues while you focus on growth. Agencies & Consultants – Instantly prioritize high-value client messages, flag urgent ops threads, and never drop the ball on critical communication. Busy Professionals & Teams – Reclaim 5–10 hours weekly by letting AI handle noise, flag what matters, and summarize newsletters into actionable insights. No-Code Builders & AI Engineers – Plug in, customize, and ship production-ready inbox automation in minutes—no training required. Remote Operators & Virtual Assistants – Delegate inbox management confidently with a system that flags what’s important and handles the rest. 📌 High‑Impact Results What You’re Dealing With → What This System Solves Instantly Inbox Clutter & Constant Noise → 90% Noise Reduction Trivial, low-value messages are automatically triaged and labeled—only high-value threads stay in your spotlight. Missing Critical Emails → Real-Time Telegram Alerts Get instantly notified the moment a client, lead, or ops-critical email lands. Zero lag. Zero drop. Manual Reply Fatigue → AI-Generated Drafts in Seconds Fully contextual, brand-aligned replies ready at a click—cut response time from minutes to seconds. Newsletter Overload → Actionable 60-Second Summaries Dense newsletters converted into digestible, decision-ready highlights. Save hours while staying sharp. Information Chaos → Fully Structured Inbox Intelligence From raw email to labeled insights to escalated alerts—your inbox becomes an automated decision support system. This system doesn’t just "help"—it replaces hours of work per week, prevents costly misses, and ensures you never drown in emails again. ⚙️ Powerful Features 📥 AI Email Triage – Classifies and sorts emails using GPT/Gemini, labeling by intent and urgency. 📰 Newsletter Summarizer – Extracts concise, actionable insights from newsletters into structured summaries. 🚨 Real-Time Priority Alerts – Instantly escalates mission-critical emails via Telegram. 🤖 Autonomous Inbox Agent – Proactively manages email actions: replies, drafts, archives, and thread labeling. 🧠 Persistent Context Memory – Remembers senders, conversation history, and adjusts responses accordingly. 🏅 Why Choose This Solution? Fully Self-Hosted & Secure – Keep full control of your data and privacy. No external storage, no SaaS lock-in—just your infrastructure, your rules. Production-Grade Reliability – Built by a Lead Software Engineer. Tested, trusted, and optimized for uptime by myself. AI-Native Workflow Engine – Smart, adaptive, and deeply embedded in your processes. Automates with context, learns with use, and gets smarter over time. 💰 Pricing Limited Time Launch Price: $29 (One-time payment) 🎯 Lifetime access—pay once, save time forever. ⏱️ Designed to reclaim 5–10 hours per week per inbox. 🚨 One missed priority email could cost more—this system prevents that. ⚡ Launch offer pricing will increase SOON!—lock in early. 📦 What's Included? ✅ Fully documented and annotated n8n workflow (ready-to-import JSON) 📂 Gmail labeling system (production-ready taxonomy) 📲 Telegram integration and alert configuration 🛠 Customizable AI prompt templates for Gemini/GPT 🧠 Custom prompt templates for GPT & Gemini ⚙️ Autonomous email categorization & filtering 📰 Newsletter summarizer with structured JSON output 🤖 Optional AI agent for full inbox management tasks 🚀 Quick Start Setup Import the full workflow into your self-hosted n8n environment. Connect your Gmail, Telegram, and preferred LLMs (OpenAI or Gemini). Deploy Gmail labels using the included taxonomy—ensures proper triage and filtering. Trigger test alerts from real email data to verify AI classification and Telegram escalation. Go live—start receiving summarized insights, escalations, and triaged inbox updates within minutes. ❓ FAQ Q: What kind of ROI can I expect? A: On average, users reclaim 5–10 hours per week per inbox by eliminating low-priority noise, surfacing urgent emails instantly, and automating replies and summaries. For a business leader or agency, that’s hundreds of dollars in time savings weekly—and zero dropped balls. Q: Can it scale for my team? A: Absolutely. It’s architected with modular nodes and reusable components so you can rapidly duplicate, extend, or adapt it across teams, departments, and workflows. Whether you’re a solo founder or managing 20+ inboxes, this system grows with you—without code rewrites. Q: Is my data secure? A: Absolutely!. This system runs entirely in your self-hosted n8n environment, so your data never leaves your control. External LLMs (like OpenAI or Gemini) are only used when needed and receive minimal, context-limited input. You control all API keys and endpoints. No data is stored externally unless you configure it. Made with ❤️ by Bluegrass Digital Advantage

💸 GPT-4o Token Tracker – Measure AI Usage and Cost via WhatsApp or Telegram Hi! I'm Amanda — I create smart, useful AI automations for n8n and Make. This workflow helps you monitor how many tokens are consumed per conversation with AI Agent Tokens, and logs that usage into Google Sheets — so you can track expenses and make smarter decisions about your AI usage. You can connect it to Telegram or WhatsApp (via Evolution API), and it will automatically capture: Prompt and completion tokens Total tokens Time of interaction The user/channel (Optional) Cost estimate in USD 📊 What this workflow does Logs token usage from LangChain agents Calculates token totals for each request Appends the data to a structured Google Sheet Works with WhatsApp (Evolution API) or Telegram bots Ideal for tracking AI Agent Tokens usage over time and controlling costs 🧪 Free Spreadsheet Template You can duplicate and use this template for logging token usage: 👉 Google Sheets Template Includes columns like: Date Input Output Tokens (Prompt / Completion / Total) Tool name or use case Estimated cost 🛠️ Setup Instructions Import the workflow to your n8n (Cloud or self-hosted) Connect your Google Sheets account Choose your trigger: WhatsApp (Evolution API webhook) Telegram (Bot webhook or message input) Fill out: AI Agent model used (e.g. gpt-4o) Cost per 1K tokens (optional, for USD estimation) Update spreadsheet ID and tab name in the Google Sheets node (Optional) Connect as a sub-tool to an AI agent for automatic logging 🧰 Tech Used OpenRouter LangChain Google Sheets Telegram or WhatsApp webhook (Evolution API) Nodes: HTTP Request, Set, If, Google Sheets, Merge ✅ Who This Is For Developers or agencies that want to monitor AI Agent Tokens usage Freelancers managing AI bots for clients Teams that need billing visibility and cost control Anyone who wants transparency in AI token spending ✅ Requirements OpenAI GPT-4o access Google Sheets credential Telegram Bot Token (or Evolution API access for WhatsApp) n8n (Cloud or self-hosted) 🌐 Want this template? ❤️ Buy more workflows at: https://iloveflows.com ☁️ Try n8n Cloud: https://n8n.partnerlinks.io/amanda

What we wanna do? Let's look at the concern. In my experience, some developers don't check their Jira board to find out whether there are new updates on the issues or not or if some Issues need to be addressed as soon as possible. So, the developer or anyone else in other fields needs to be informed about the task as soon as possible, too. One way to send this immediate notification is through the Telegram Bot. Setup Guide so, first of all, you need to register a Telegram Bot in your account and obtain its token, so that we'll be able to send Telegram messages by using this token through our bot; after getting your telegram bot token go to the workflow and click on one of the telegram nodes select the telegram credential or create one through the Credential to connect with field and put the token in the token in the Access Token field. Ok, you're done with the Telegram Side setup. then you need the Jira accounts (team users) accountId and also their telegram chatId for the telegram account node so that it can find the corresponding telegram user from the assignee of the issue, put this data as following guide comments in the telegram account node. Now we go for the Jira side setup, you need to setup some automation rules as your needs. go to the Jira settings and Global automation section, click on the Create Rule button select the Issue Created trigger type in the When step add a Send webhook request action, after selecting it you'll see its settings go back to workflow and from the jira-webhook node copy the Production URL paste it in the Web request URL field in the Jira action setting then set the HTTP method field on POST set Web request body on Issue Data (Automation format) in the header section, add a new header with the name type and value created for the creation event. OK, the Jira side also is done! Now It's time to test! If you've put your Jira accountId and telegram chatId in the telegram account node and of course started the telegram bot, after creating an Issue that is assigned to you, the creation notif will send to you in telegram!