Webhook and Redis integration

AI-Powered WhatsApp Assistant for Restaurant & Delivery – Automate Orders, Calculate Delivery Fees & Enhance Customer Service with n8n 📌 Optimize your restaurant's delivery process with AI-powered automation! This n8n workflow enables an intelligent WhatsApp assistant for restaurants, burger joints, and delivery businesses. The AI chatbot efficiently handles orders, calculates delivery fees based on distance, manages customer interactions, and seamlessly integrates with your CRM and database for streamlined operations. ⚠️ Important Notice: This template is only compatible with self-hosted n8n instances as it uses community nodes. Ensure secure credential management when configuring APIs. 🔹 Key Features ✅ AI-Powered Order Processing – Automatically receive and confirm orders via WhatsApp. ✅ Real-Time Distance Calculation – Determines the delivery distance and calculates the fee dynamically. ✅ Automated Customer Interaction – Engages customers with intelligent conversation and order updates. ✅ WhatsApp Integration – Processes messages, saves customer details, and retrieves past interactions. ✅ Secure Customer Data Storage – Saves order history, customer preferences, and location details in a database. ✅ Seamless CRM & POS System Integration – Sync orders and customer data with your existing platforms. 📌 How It Works 1️⃣ A customer sends a message via WhatsApp to start an order. 2️⃣ The AI assistant guides them through the menu, recommends items, and confirms their choices. 3️⃣ The system retrieves and saves customer details (name, phone number, and address). 4️⃣ The AI calculates the delivery distance and applies the appropriate delivery fee. 5️⃣ The order details are saved and forwarded to the restaurant’s system for preparation. 6️⃣ The assistant keeps the customer updated about the order status. ⚙️ Setup & Customization 🔧 Webhook for WhatsApp – Capture and process customer messages automatically. 🔧 OpenAI-Powered AI Assistant – Configure conversation flows for natural and engaging interactions. 🔧 Delivery Fee Calculation – Set your delivery price per kilometer and adjust base rates. 🔧 Database & CRM Integration – Store customer details, order history, and location data. 🔧 Customizable Order Flow – Adapt the workflow for different restaurant models. 🔧 Secure Credential Management – Store API keys safely to prevent unauthorized access. 💡 Requirements: This template is recommended for users with basic knowledge of n8n. If you need custom development or setup assistance, contact us via WhatsApp: +55 17 99155-7874. 🚀 Automate order processing, reduce manual tasks, and improve customer satisfaction with AI-powered WhatsApp automation! Assistente de WhatsApp com IA para Restaurantes & Delivery – Automatize Pedidos, Calcule Taxas de Entrega e Melhore o Atendimento ao Cliente com n8n 📌 Otimize o processo de entrega do seu restaurante com automação baseada em IA! Este fluxo para n8n permite criar um atendente virtual inteligente no WhatsApp, ideal para hamburguerias, restaurantes e serviços de delivery. O chatbot baseado em IA recebe pedidos, calcula a taxa de entrega com base na distância, interage com os clientes e integra-se ao seu CRM para operações mais eficientes. ⚠️ Aviso Importante: Este template é compatível apenas com instâncias auto-hospedadas do n8n, pois utiliza nós da comunidade. Certifique-se de gerenciar credenciais de forma segura ao configurar APIs. 🔹 Principais Funcionalidades ✅ Processamento Inteligente de Pedidos – Recebe e confirma pedidos automaticamente via WhatsApp. ✅ Cálculo Dinâmico da Taxa de Entrega – Mede a distância e aplica a taxa correta automaticamente. ✅ Atendimento Automatizado ao Cliente – Interage com clientes de forma natural e profissional. ✅ Integração com WhatsApp – Captura mensagens, armazena dados e recupera histórico de pedidos. ✅ Armazenamento Seguro de Dados do Cliente – Salva pedidos, preferências e endereços de entrega. ✅ Sincronização com CRM e Sistema de PDV – Conecta-se ao seu sistema de gestão para um fluxo contínuo. 📌 Como Funciona 1️⃣ O cliente envia uma mensagem via WhatsApp para iniciar um pedido. 2️⃣ O assistente de IA apresenta o menu, sugere itens e confirma a escolha do cliente. 3️⃣ O sistema captura e salva os dados do cliente (nome, telefone e endereço). 4️⃣ A IA calcula a distância de entrega e aplica a taxa de acordo com a localização. 5️⃣ Os detalhes do pedido são registrados e enviados para a cozinha. 6️⃣ O assistente atualiza o cliente sobre o status do pedido. ⚙️ Configuração e Personalização 🔧 Webhook para WhatsApp – Configuração para capturar e processar pedidos automaticamente. 🔧 Assistente de IA com OpenAI – Configuração de fluxos conversacionais naturais e envolventes. 🔧 Cálculo de Taxa de Entrega – Definição de valores por quilômetro e ajustes de tarifas base. 🔧 Banco de Dados & CRM – Armazena dados de clientes, histórico de pedidos e localização. 🔧 Fluxo de Pedidos Personalizável – Adapte para diferentes tipos de restaurantes e serviços de delivery. 🔧 Gerenciamento Seguro de Credenciais – Proteja suas chaves de API contra acessos não autorizados. 💡 Requisitos: Este template é recomendado para usuários que já possuem conhecimentos básicos em n8n. Se precisar de personalização ou suporte para instalação, entre em contato pelo WhatsApp: +55 17 99155-7874. 🚀 Automatize o processamento de pedidos, reduza tarefas manuais e melhore a satisfação dos clientes com um WhatsApp automatizado e inteligente!

🐶🤖 AI Agent for Pet Shops – Automate Customer Service & Bookings! 🐾💡 Transform Your Pet Shop with AI-Powered Automation! 🚀 Enhance customer experience and optimize operations with this n8n AI Agent designed for pet shops. 📲🐾 Automate client interactions, appointment scheduling, and service recommendations—saving time and increasing revenue! 🔹 Key Features: ✅ Instant WhatsApp responses – AI-powered chatbot handles customer inquiries. 💬 ✅ Automated appointment scheduling – Clients can book services hassle-free. 📅✂️ ✅ Personalized reminders – Reduce no-shows with automated notifications. 📢🐾 ✅ Customer data & service history management – Track interactions effortlessly. 📊📁 ✅ Product & service recommendations – Improve sales with smart suggestions. 🎁🐶 📌 How It Works 1️⃣ The workflow captures customer inquiries via WhatsApp. 2️⃣ AI processes requests, provides information, and offers booking options. 3️⃣ Clients can schedule grooming, vet visits, or other services in seconds. 4️⃣ Automated reminders ensure appointments are remembered. 5️⃣ Customer data is stored for better service personalization. ⚙️ Setup & Customization 🔧 Connect your WhatsApp API (evolution) for instant messaging. 🔧 Integrate with Google Calendar for appointment booking. 🔧 Customize reminders, services, and pricing rules to fit your business. 💡 Reduce manual work, improve customer satisfaction, and scale your pet shop with AI automation! 🐶🤖 [PT-BR] Agente de IA para Pet Shops – Atendimento e Agendamentos Automatizados! 🐾💡 Transforme Seu Pet Shop com Automação Inteligente! 🚀 Otimize o atendimento ao cliente e agilize processos com este Agente de IA para n8n. 📲🐾 Automatize interações, agendamentos e recomendações de serviços—economizando tempo e aumentando as vendas! 🔹 Principais Funcionalidades: ✅ Atendimento automático no WhatsApp – IA responde clientes instantaneamente. 💬 ✅ Agendamento de serviços automatizado – Clientes marcam banho, tosa ou consultas facilmente. 📅✂️ ✅ Lembretes personalizados – Reduza faltas com notificações automáticas. 📢🐾 ✅ Gestão de clientes e histórico de serviços – Controle dados de forma eficiente. 📊📁 ✅ Sugestão de produtos e serviços – Venda mais com recomendações inteligentes. 🎁🐶 📌 Como Funciona 1️⃣ O fluxo recebe perguntas dos clientes via WhatsApp. 2️⃣ A IA processa os pedidos e fornece opções de agendamento. 3️⃣ O cliente escolhe o serviço desejado e agenda em segundos. 4️⃣ Lembretes automáticos garantem que os clientes não esqueçam os horários. 5️⃣ O histórico do cliente é salvo para oferecer um atendimento mais personalizado. ⚙️ Configuração e Personalização 🔧 Conecte sua API do WhatsApp (evolution) para interação automática. 🔧 Integre ao Google Calendar para gerenciar agendamentos. 🔧 Personalize valores, serviços e regras de envio de lembretes conforme sua necessidade. 💡 Automatize processos, melhore a experiência do cliente e escale seu pet shop com IA! 🚀

Purpose This solution enables you to manage all your Notion and Todoist tasks from different workspaces as well as your calendar events in a single place. All tasks can be managed in Todoist and additionally Fantastical can be used to manage scheduled tasks & events all together. Demo & Explanation How it works The realtime sync consists of two workflows, both triggered by a registered webhook from either Notion or Todoist To avoid overwrites by lately arriving webhook calls, every time the current task is retrieved from both sides. Redis is used to prevent from endless loops, since an update in one system triggers another webhook call again. Using the ID of the task, the trigger is being locked down for 15 seconds. Depending on the detected changes, the other side is updated accordingly. Generally Notion is treaded as the main source. Using an "Obsolete" Status, it is guaranteed, that tasks never get deleted entirely by accident. The Todoist ID is stored in the Notion task, so they stay linked together An additional full sync workflow daily fixes inconsistencies, if any of them occurred, since webhooks cannot be trusted entirely. Since Todoist requires a more complex setup, a tiny workflow helps with activating the webhook. Another tiny workflow helps generating a global config, which is used by all workflows for mapping purposes. Mapping (Notion >> Todoist) Name: Task Name Priority: Priority (1: do first, 2: urgent, 3: important, 4: unset) Due: Date Status: Section (Done: completed, Obsolete: deleted) <page_link>: Description (read-only) Todoist ID: <task_id> Current limitations Changes on the same task cannot be made simultaneously in both systems within a 15-20 second time frame Subtasks are not linked automatically to their parent yet Recurring tasks are not supported yet Tasks names do not support URL’s yet Compatibility n8n v2.5.0 and above Updates This templated has been updated to work with the new "combined" Todoist API (v1). The general flow works exactly the same as before. Only the setup of the Todoist Webhook might look a tiny bit different then shown in the setup video, so please also have a look at the yellow sticky notes. Prerequisites Notion A database must already exist (get a basic template here) with the following properties (case matters!): Text: "Name" Status: "Status", containing at least the options "Backlog", "In progress", "Done", "Obsolete" Select: "Priority", containing the options "do first", "urgent", "important" Date: "Due" Checkbox: "Focus" Text: "Todoist ID" Todoist A project must already exist with the same sections like defined as Status in Notion (except Done and Obsolete) Redis Create a Free Redis Cloud instance or self-host Setup The setup involves quite a lot of steps, yet many of them can be automated for business internal purposes. Just follow the video or do the following steps: Setup credentials for Notion (access token), Todoist (access token) and Redis - you can also create empty credentials and populate these later during further setup Clone this workflow by clicking the "Use workflow" button and then choosing your n8n instance - otherwise you need to map the credentials of many nodes. Follow the instructions described within the bundle of sticky notes on the top left of the workflow How to use You can apply changes (create, update, delete) to tasks both in Notion and Todoist which then get synced over within a couple of seconds (this is handled by the differential realtime sync) The daily running full sync, resolves possible discrepancies in Todoist and sends a summary via email, if anything needed to be updated. In case that contains an unintended change, you can jump to the Task from the email directly to fix it manually.

👤 Who is this for? This workflow is great for n8n users who want to prevent duplicate or overlapping workflow runs. If you're a developer, DevOps engineer, or automation enthusiast managing tasks like database updates, syncing tools, or hitting rate-limited APIs, this one’s for you. 🧩 What problem does this solve? In the real world, automations can get triggered at the same time—whether that’s because of multiple webhook calls, overlapping schedules, or retries. And when two workflows try to do the same thing at once (like updating a record or syncing data), it can cause conflicts, data corruption, or wasted API calls. This workflow helps avoid that problem by using Redis as a lock system, so only one instance runs at a time. Think of it like putting up a “🚧 Workflow in Progress” sign while your logic is running. ⚙️ What this workflow does When the workflow starts, it tries to set a Redis key as a lock with a short expiry. If the lock is free: Your main business logic runs. Once it's done, the lock is cleared. If the lock is already taken (i.e., another run is in progress): The workflow will wait and retry a few times. If a duplicate request shows up while one is already being processed: It skips that duplicate to avoid unnecessary work. You can customize both the timeout and retry logic to match your needs. 🛠️ Setup guide To use this template: You’ll need access to a Redis instance (either self-hosted or managed like Upstash, Redis Cloud, etc). Set up your Redis credentials in the n8n Redis node. Swap out the webhook node with your actual trigger or logic. Adjust the lock timeout to match how long your task typically takes. > 💡 Bonus Tip: Use this pattern wherever you need idempotency or want to avoid duplicate processing. 🧪 Example use case Let’s say you have a workflow that syncs ClickUp tickets to Google Sheets. It runs daily at 9 AM and updates tickets, adds notes, and makes sure nothing is missed. But what if two runs start at the same time? Or someone triggers a manual sync while the scheduled one is still working? By wrapping that whole sync inside this Redis locking template, you can make sure it only runs one at a time, saving your APIs (and your sanity).

🔄 AI Video Polling Engine - Long-Running Job Handler for Veo, Sora & Seedance The async backbone that makes AI video generation production-ready ⚡🎬 🎥 See It In Action 🔗 Full Demo: youtu.be/OI_oJ_2F1O0 ⚠️ Must Read First This is a companion workflow for the main AI Shorts Generator: 🔗 Main Workflow: AI Shorts Reactor This workflow handles the "waiting game" so your main bot stays fast and responsive. Think of it as the backstage crew that handles the heavy lifting while your main workflow performs on stage. 🤔 The Problem This Solves Without This Workflow: User sends message ↓ Bot calls AI API ↓ ⏳ Bot waits 2-5 minutes... (BLOCKED) ↓ ❌ Timeout errors ❌ Execution limits exceeded ❌ Users think bot is broken ❌ Can't handle multiple requests With This Workflow: User sends message ↓ Bot calls AI API ↓ ✅ Bot responds instantly: "Video generating..." ↓ 🔄 This webhook polls in background ↓ ⚡ Main bot handles other users ↓ ✅ Video ready → Auto-sends to user Result: Your bot feels instant, scales infinitely, and never times out 🚀 🔁 What This Workflow Does This is a dedicated polling webhook that acts as the async job handler for AI video generation. It's the invisible worker that: 1️⃣ Receives the Job POST /webhook/poll-video { "sessionId": "user_123", "taskId": "veo_abc456", "model": "veo3", "attempt": 1 } 2️⃣ Responds Instantly 200 OK - "Polling started" (Main workflow never waits!) 3️⃣ Polls in Background Wait 60s → Check status → Repeat ⏱️ Waits 1 minute between checks (API-friendly) 🔄 Polls up to 15 times (~15 minutes max) 🎯 Supports Veo, Sora, and Seedance APIs 4️⃣ Detects Completion Handles multiple API response formats: // Veo format { status: "completed", videoUrl: "https://..." } // Market format (Sora/Seedance) { job: { status: "success", result: { url: "..." } } } // Legacy format { data: { video_url: "..." } } (No matter how the API responds, this workflow figures it out) 5️⃣ Delivers the Video Once ready: 📥 Downloads video from AI provider ☁️ Uploads to your S3 storage 💾 Restores user session from Redis 📱 Sends Telegram preview with buttons 🔄 Enables video extension (Veo only) 📊 Logs metadata for analytics ⚙️ Technical Architecture The Flow: Main Workflow Polling Webhook │ │ ├──[Trigger AI Job]──────────┤ │ "Task ID: abc123" │ │ │ ├──[Return Instantly] │ │ "Generating..." │ │ │ ├──[Handle New User] │ │ ├──[Wait 60s] │ │ │ ├──[Check Status] │ │ "Processing..." │ │ │ ├──[Wait 60s] │ │ │ ├──[Check Status] │ │ "Completed!" │ │ │ ├──[Download Video] │ │ │ ├──[Upload to S3] │ │ │ └──[Send to User] │ │ └──────────────────────────────────┘ "Your video is ready!" 🚀 Key Features ⚡ Non-Blocking Architecture Main workflow never waits Handle unlimited concurrent jobs Each user gets instant responses 🔄 Intelligent Polling Respects API rate limits (60s intervals) Auto-retries on transient failures Graceful timeout handling (15 attempts max) 🎯 Multi-Provider Support Handles different API formats: Veo** - record-info endpoint Sora** - Market job status Seedance** - Market job status 🛡️ Robust Error Handling ✅ Missing video URL → Retry with fallback parsers ✅ API timeout → Continue polling ✅ Invalid response → Parse alternative formats ✅ Max attempts reached → Notify user gracefully 💾 Session Management Stores state in Redis Restores full context when video is ready Supports video extension workflows Maintains user preferences 📊 Production Features Detailed logging at each step Metadata tracking (generation time, model used, etc.) S3 storage integration Telegram notifications Analytics-ready data structure 🧩 Integration Points Works Seamlessly With: | Use Case | How It Helps | |----------|--------------| | 🤖 Telegram Bots | Keeps bot responsive during 2-5 min video generation | | 📺 YouTube Automation | Polls video, then triggers auto-publish | | 🎬 Multi-Video Pipelines | Handles 10+ videos simultaneously | | 🏢 Content Agencies | Production-grade reliability for clients | | 🧪 A/B Testing | Generate multiple variations without blocking | Required Components: ✅ Main workflow that triggers video generation ✅ Redis for session storage ✅ S3-compatible storage for videos ✅ KIE.ai API credentials ✅ Telegram Bot (for notifications) 📋 How to Use Step 1: Set Up Main Workflow Import and configure the AI Shorts Reactor Step 2: Import This Webhook Add this workflow to your n8n instance Step 3: Configure Credentials KIE.ai API key Redis connection S3 storage credentials Telegram bot token Step 4: Link Workflows In your main workflow, call this webhook: // After triggering AI video generation const response = await httpRequest({ method: 'POST', url: 'YOUR_WEBHOOK_URL/poll-video', body: { sessionId: sessionId, taskId: taskId, model: 'veo3', attempt: 1 } }); Step 5: Activate & Test Activate this polling webhook Trigger a video generation from main workflow Watch it poll in background and deliver results 🎯 Real-World Example Scenario: User generates 3 videos simultaneously Without This Workflow: User A: "Generate video" → Bot: ⏳ Processing... (BLOCKED 5 min) User B: "Generate video" → Bot: ❌ Timeout (main workflow still processing User A) User C: "Generate video" → Bot: ❌ Never receives request With This Workflow: User A: "Generate video" → Bot: ✅ "Generating! Check back in 3 min" → Polling webhook handles in background User B: "Generate video" → Bot: ✅ "Generating! Check back in 3 min" → Second polling instance starts User C: "Generate video" → Bot: ✅ "Generating! Check back in 3 min" → Third polling instance starts 3 minutes later--- User A: 📹 "Your video is ready!" [Preview] [Publish] User B: 📹 "Your video is ready!" [Preview] [Publish] User C: 📹 "Your video is ready!" [Preview] [Publish] All three users served simultaneously with zero blocking! 🚀 🔧 Customization Options Adjust Polling Frequency // Default: 60 seconds // For faster testing (use credits faster): const waitTime = 30; // seconds // For more API-friendly (slower updates): const waitTime = 90; // seconds Change Timeout Limits // Default: 15 attempts (15 minutes) const maxAttempts = 20; // Increase for longer videos Add More Providers Extend to support other AI video APIs: switch(model) { case 'veo3': // Existing Veo logic case 'runway': // Add Runway ML polling case 'pika': // Add Pika Labs polling } Custom Notifications Replace Telegram with: Discord webhooks Slack messages Email notifications SMS via Twilio Push notifications 📊 Monitoring & Analytics What Gets Logged: { "sessionId": "user_123", "taskId": "veo_abc456", "model": "veo3", "status": "completed", "attempts": 7, "totalTime": "6m 32s", "videoUrl": "s3://bucket/videos/abc456.mp4", "metadata": { "duration": 5.2, "resolution": "1080x1920", "fileSize": "4.7MB" } } Track Key Metrics: ⏱️ Average generation time per model 🔄 Polling attempts before completion ❌ Failure rate by provider 💰 Cost per video (API usage) 📈 Concurrent job capacity 🚨 Troubleshooting "Video never completes" ✅ Check KIE.ai API status ✅ Verify task ID is valid ✅ Increase maxAttempts if needed ✅ Check API response format hasn't changed "Polling stops after 1 attempt" ✅ Ensure webhook URL is correct ✅ Check n8n execution limits ✅ Verify Redis connection is stable "Video downloads but doesn't send" ✅ Check Telegram bot credentials ✅ Verify S3 upload succeeded ✅ Ensure Redis session exists ✅ Check Telegram chat ID is valid "Multiple videos get mixed up" ✅ Confirm sessionId is unique per user ✅ Check Redis key collisions ✅ Verify taskId is properly passed 🏗️ Architecture Benefits Why Separate This Logic? | Aspect | Monolithic Workflow | Separated Webhook | |--------|--------------------|--------------------| | ⚡ Response Time | 2-5 minutes | <1 second | | 🔄 Concurrency | 1 job at a time | Unlimited | | 💰 Execution Costs | High (long-running) | Low (short bursts) | | 🐛 Debugging | Hard (mixed concerns) | Easy (isolated logic) | | 📈 Scalability | Poor | Excellent | | 🔧 Maintenance | Complex | Simple | 🛠️ Requirements Services Needed: ✅ n8n Instance (cloud or self-hosted) ✅ KIE.ai API (Veo, Sora, Seedance access) ✅ Redis (session storage) ✅ S3-compatible Storage (videos) ✅ Telegram Bot (optional, for notifications) Skills Required: Basic n8n knowledge Understanding of webhooks Redis basics (key-value storage) S3 upload concepts Setup Time: ~15 minutes Technical Level: Intermediate 🏷️ Tags webhook polling async-jobs long-running-tasks ai-video veo sora seedance production-ready redis s3 telegram youtube-automation content-pipeline scalability microservices n8n-webhook job-queue background-worker 💡 Best Practices Do's ✅ Keep polling interval at 60s minimum (respect API limits) Always handle timeout scenarios Log generation metadata for analytics Use unique session IDs per user Clean up Redis after job completion Don'ts ❌ Don't poll faster than 30s (risk API bans) Don't store videos in Redis (use S3) Don't skip error handling Don't use this for real-time updates (<10s) Don't forget to activate the webhook 🌟 Success Stories After Implementing This Webhook: | Metric | Before | After | |--------|--------|-------| | ⚡ Bot response time | 2-5 min | <1 sec | | 🎬 Concurrent videos | 1 | 50+ | | ❌ Timeout errors | 30% | 0% | | 😊 User satisfaction | 6/10 | 9.5/10 | | 💰 Execution costs | $50/mo | $12/mo | 🔗 Related Workflows 🎬 Main: AI Shorts Reactor - The full video generation bot 📤 YouTube Auto-Publisher - Publish completed videos 🎨 Video Style Presets - Custom prompt templates 📊 Analytics Dashboard - Track all generations 📜 License MIT License - Free to use, modify, and distribute! ⚡ Make your AI video workflows production-ready. Let the webhook handle the waiting. ⚡ Created by Joe Venner | Built with ❤️ and n8n | Part of the AI Shorts Reactor ecosystem

Purpose This solution enables you to manage all your Notion and Todoist tasks from different workspaces as well as your calendar events in a single place. This is 2 way sync with partial support for recurring How it works The realtime sync consists of two workflows, both triggered by a registered webhook from either Notion or Todoist. To avoid overwrites by lately arriving webhook calls, every time the current task is retrieved from both sides. Redis is used to prevent from endless loops, since an update in one system triggers another webhook call again. Using the ID of the task, the trigger is being locked down for 80 seconds. Depending on the detected changes, the other side is updated accordingly .Generally Notion is treaded as the main source. Using an "Obsolete" Status, it is guaranteed, that tasks never get deleted entirely by accident. The Todoist ID is stored in the Notion task, so they stay linked together An additional full sync workflow daily fixes inconsistencies, if any of them occurred, since webhooks cannot be trusted entirely. Since Todoist requires a more complex setup, a tiny workflow helps with activating the webhook. Another tiny workflow helps generating a global config, which is used by all workflows for mapping purposes. Mapping (Notion >> Todoist) Name: Task Name Priority: Priority (1: do first, 2: urgent, 3: important, 4: unset) Due: Date Status: Section (Done: completed, Obsolete: deleted) <page_link>: Description (read-only) Todoist ID: <task_id> Current limitations Changes on the same task cannot be made simultaneously in both systems within a 15-20 second time frame. Subtasks are not linked automatically to their parent yet. Tasks names do not support URL’s yet. Credentials Follow the video: Setup credentials for Notion (access token), Todoist (access token) and Redis. Todoist Follow this video to get Todoist to obtain API Token. Todoist Credentials.mp4 Notion Follow this video to get Notion Integration Secret. Redis Follow this video to get Redis Setup The setup involves quite a lot of steps, yet many of them can be automated for business internal purposes. Just follow the video or do the following steps: Setup credentials for Notion (access token), Todoist (access token) and Redis - you can also create empty credentials and populate these later during further setup Clone this workflow by clicking the "Use workflow" button and then choosing your n8n instance - otherwise you need to map the credentials of many nodes. Follow the instructions described within the bundle of sticky notes on the top left of the workflow How to use You can apply changes (create, update, delete) to tasks both in Notion and Todoist which then get synced over within a couple of seconds (this is handled by the differential realtime sync) The daily running full sync, resolves possible discrepancies in Todoist. This workflow incorporates ideas and techniques inspired by Mario (https://n8n.io/creators/octionic/) whose expertise with specific nodes helped shape parts of this automation. Significant enhancements and customizations have been made to deliver a unique and improved solution.

Purpose This solution enables you to manage all your Notion and Todoist tasks from different workspaces as well as your calendar events in a single place. This is 2 way sync with partial support for recurring How it works The realtime sync consists of two workflows, both triggered by a registered webhook from either Notion or Todoist. To avoid overwrites by lately arriving webhook calls, every time the current task is retrieved from both sides. Redis is used to prevent from endless loops, since an update in one system triggers another webhook call again. Using the ID of the task, the trigger is being locked down for 80 seconds. Depending on the detected changes, the other side is updated accordingly .Generally Notion is treaded as the main source. Using an "Obsolete" Status, it is guaranteed, that tasks never get deleted entirely by accident. The Todoist ID is stored in the Notion task, so they stay linked together An additional full sync workflow daily fixes inconsistencies, if any of them occurred, since webhooks cannot be trusted entirely. Since Todoist requires a more complex setup, a tiny workflow helps with activating the webhook. Another tiny workflow helps generating a global config, which is used by all workflows for mapping purposes. Mapping (Notion >> Todoist) Name: Task Name Priority: Priority (1: do first, 2: urgent, 3: important, 4: unset) Due: Date Status: Section (Done: completed, Obsolete: deleted) <page_link>: Description (read-only) Todoist ID: <task_id> Current limitations Changes on the same task cannot be made simultaneously in both systems within a 15-20 second time frame. Subtasks are not linked automatically to their parent yet. Tasks names do not support URL’s yet. Credentials Follow the video: Setup credentials for Notion (access token), Todoist (access token) and Redis. Todoist Follow this video to get Todoist to obtain API Token. Todoist Credentials.mp4 Notion Follow this video to get Notion Integration Secret. Redis Follow this video to get Redis Setup The setup involves quite a lot of steps, yet many of them can be automated for business internal purposes. Just follow the video or do the following steps: Setup credentials for Notion (access token), Todoist (access token) and Redis - you can also create empty credentials and populate these later during further setup Clone this workflow by clicking the "Use workflow" button and then choosing your n8n instance - otherwise you need to map the credentials of many nodes. Follow the instructions described within the bundle of sticky notes on the top left of the workflow How to use You can apply changes (create, update, delete) to tasks both in Notion and Todoist which then get synced over within a couple of seconds (this is handled by the differential realtime sync) The daily running full sync, resolves possible discrepancies in Todoist. This workflow incorporates ideas and techniques inspired by Mario (https://n8n.io/creators/octionic/) whose expertise with specific nodes helped shape parts of this automation. Significant enhancements and customizations have been made to deliver a unique and improved solution.

How It Works This workflow automates customer feedback processing by analyzing sentiment, identifying key issues, generating personalized responses, and escalating critical cases to support teams when required. Designed for customer success managers, support teams, and product managers, it enables scalable feedback handling without compromising response quality or urgency. The workflow eliminates manual triage and response drafting by normalizing incoming feedback, performing sentiment and topic analysis, generating context-aware AI responses, validating tone and intent, escalating high-risk or negative feedback, logging all interactions for traceability, and delivering automated replies via email. Setup Steps Configure webhook trigger URL for feedback form integration or email parsing Add OpenAI API key for sentiment analysis and response generation Connect Anthropic Claude API for alternative response generation and validation Set up Google Sheets integration for feedback logging and analytics tracking Configure Gmail OAuth2 credentials for automated customer response delivery Integrate support ticket system (Zendesk, Freshdesk) for escalation routing Prerequisites OpenAI API key, Anthropic Claude API key (optional), Google Workspace account (Sheets, Gmail) Use Cases Product feedback management, customer support automation Customization Adjust sentiment scoring thresholds per industry standards, modify response templates Benefits Responds to feedback 95% faster, maintains consistent response quality across all interactions

Build an intelligent WhatsApp assistant that automatically responds to customer messages using AI. This template uses the Evolution API community node for WhatsApp integration and OpenAI for natural language processing, with built-in conversation memory powered by Redis to maintain context across messages. > ⚠️ Self-hosted requirement: This workflow uses the Evolution API community node, which is only available on self-hosted n8n instances. It will not work on n8n Cloud. What this workflow does Receives incoming WhatsApp messages via Evolution API webhook Filters and processes text, audio, and image messages Transcribes audio messages using OpenAI Whisper Analyzes images using GPT-4 Vision Generates contextual responses with conversation memory Sends replies back through WhatsApp Who is this for? Businesses wanting to automate customer support on WhatsApp Teams needing 24/7 automated responses with AI Developers building multimodal chat assistants Companies looking to reduce response time on WhatsApp Setup instructions Evolution API: Install and configure Evolution API on your server. Create an instance and obtain your API key and instance name. Redis: Set up a Redis instance for conversation memory. You can use a local installation or a cloud service like Redis Cloud. OpenAI: Get your API key from platform.openai.com with access to GPT and Whisper models. Webhook: Configure your Evolution API instance to send webhooks to your n8n webhook URL. Customization options Modify the system prompt in the AI node to change the assistant's personality and responses Adjust the Redis TTL to control how long conversation history is retained Add additional message type handlers for documents, locations, or contacts Integrate with your CRM or database to personalize responses Credentials required Evolution API credentials (self-hosted) OpenAI API key Redis connection

Purpose This solution enables you to manage all your Notion and Todoist tasks from different workspaces as well as your calendar events in a single place. This is 2 way sync with partial support for recurring How it works The realtime sync consists of two workflows, both triggered by a registered webhook from either Notion or Todoist. To avoid overwrites by lately arriving webhook calls, every time the current task is retrieved from both sides. Redis is used to prevent from endless loops, since an update in one system triggers another webhook call again. Using the ID of the task, the trigger is being locked down for 80 seconds. Depending on the detected changes, the other side is updated accordingly .Generally Notion is treaded as the main source. Using an "Obsolete" Status, it is guaranteed, that tasks never get deleted entirely by accident. The Todoist ID is stored in the Notion task, so they stay linked together An additional full sync workflow daily fixes inconsistencies, if any of them occurred, since webhooks cannot be trusted entirely. Since Todoist requires a more complex setup, a tiny workflow helps with activating the webhook. Another tiny workflow helps generating a global config, which is used by all workflows for mapping purposes. Mapping (Notion >> Todoist) Name: Task Name Priority: Priority (1: do first, 2: urgent, 3: important, 4: unset) Due: Date Status: Section (Done: completed, Obsolete: deleted) <page_link>: Description (read-only) Todoist ID: <task_id> Current limitations Changes on the same task cannot be made simultaneously in both systems within a 15-20 second time frame. Subtasks are not linked automatically to their parent yet. Tasks names do not support URL’s yet. Credentials Follow the video: Setup credentials for Notion (access token), Todoist (access token) and Redis. Todoist Follow this video to get Todoist to obtain API Token. Todoist Credentials.mp4 Notion Follow this video to get Notion Integration Secret. Redis Follow this video to get Redis Setup The setup involves quite a lot of steps, yet many of them can be automated for business internal purposes. Just follow the video or do the following steps: Setup credentials for Notion (access token), Todoist (access token) and Redis - you can also create empty credentials and populate these later during further setup Clone this workflow by clicking the "Use workflow" button and then choosing your n8n instance - otherwise you need to map the credentials of many nodes. Follow the instructions described within the bundle of sticky notes on the top left of the workflow How to use You can apply changes (create, update, delete) to tasks both in Notion and Todoist which then get synced over within a couple of seconds (this is handled by the differential realtime sync) The daily running full sync, resolves possible discrepancies in Todoist. This workflow incorporates ideas and techniques inspired by Mario (https://n8n.io/creators/octionic/) whose expertise with specific nodes helped shape parts of this automation. Significant enhancements and customizations have been made to deliver a unique and improved solution.

How it Works This workflow transforms natural language queries into research reports through a five-stage AI pipeline. When triggered via webhook (typically from Google Sheets using the companion google-apps-script.js (GitHub gist), it first checks Redis cache for instant results. For new queries, GPT-4o breaks complex questions into focused sub-queries, optimizes them for search, then uses Bright Data's MCP Tool to find the top 5 credible sources (official sites, news, financial reports). URLs are scraped in parallel, bypassing bot detection. GPT-4o extracts structured data from each source: answers, facts, entities, sentiment, quotes, and dates. GPT-4o-mini validates source credibility and filters unreliable content. Valid results aggregate into a final summary with confidence scores, key insights, and extended analysis. Results cache for 1 hour and output via webhook, Slack, email, and DataTable—all in 30-90 seconds with 60 requests/minute rate limiting. Who is this for? Research teams needing automated multi-source intelligence Content creators and journalists requiring fact-checked information Due diligence professionals conducting competitive intelligence Google Sheets power users wanting AI research in spreadsheets Teams managing large research volumes needing caching and rate limiting Setup Steps Setup time: 30-45 minutes Requirements: Bright Data account (Web Scraping API + MCP token) OpenAI API key (GPT-4o and GPT-4o-mini access) Redis instance Slack workspace (optional) SMTP email provider (optional) Google account (optional for Sheets integration) Core Setup: Get Bright Data Web Scraping API token and MCP token Get OpenAI API key Set up Redis instance Configure critical nodes: Webhook Entry: Add Header Auth token Bright Data MCP Tool: Add MCP endpoint with token Parallel Web Scraping: Add Bright Data API credentials Redis Nodes: Add connection credentials All GPT Nodes: Add OpenAI API key (5 nodes) Slack/Email: Add credentials if using Google Sheets Integration: Create Google Sheet Open Extensions → Apps Script Paste the companion google-apps-script.js code Update webhook URL and auth token Save and authorize Test: {"prompt": "What is the population of Tokyo?", "source": "Test", "language": "English"} Customization Guidance Source Count:** Change from 5 to 3-10 URLs per query Cache Duration:** Adjust from 1 hour to 24 hours for stable info Rate Limits:** Modify 60/minute based on usage needs Character Limits:** Adjust 400-char main answer to 200-1000 AI Models:** Swap GPT-4o for Claude or use GPT-4o-mini for all stages Geographic Targeting:** Add more regions beyond us/il Output Channels:** Add Notion, Airtable, Discord, Teams Temperature:** Lower (0.1-0.2) for facts, higher (0.4-0.6) for analysis Once configured, this workflow handles all web research, from fact-checking to complex analysis—delivering validated intelligence in seconds with automatic caching. Built by Daniel Shashko Connect on LinkedIn

Automating WhatsApp replies in Go High Level with Redis and Anthropic Description Integrates GHL + Wazzap with Redis and an AI Agent using ClientInfo to process messages, generate accurate replies, and send them via a custom field trigger. Who’s it for This workflow is for businesses using GoHighLevel (GHL), including the Wazzap plugin for WhatsApp, who want to automate inbound SMS/WhatsApp replies with AI. It’s ideal for teams that need accurate, data-driven responses from a predefined ClientInfo source and want to send them back to customers without paying for extra inbound automations. How it works / What it does Receive message in n8n via Webhook from GHL (Customer Replied (SMS) automation). WhatsApp messages arrive the same way using the Wazzap plugin. Filter message type: If audio → skip processing and send fallback asking for text. If text → sanitize by fixing escaped quotes, escaping line breaks/carriage returns/tabs, and removing invalid fields. Buffer messages in Redis to group multiple messages sent in a short window. Run AI Agent using the ClientInfo tool to answer only with accurate service/branch data. Sanitize AI output before sending back. Update GHL contact custom field (IA_answer) with the AI’s response. Send SMS reply automatically via GHL’s outbound automation triggered by the updated custom field. How to set up In GHL, create: Inbound automation: Trigger on Customer Replied (SMS) → Send to your n8n Webhook. Outbound automation: Trigger when IA_answer is updated → Send SMS to the contact. Create a custom field named IA_answer. Connect Wazzap in GHL to handle WhatsApp messages. Configure Redis in n8n (host, port, DB index, password). Add your AI model credentials (Anthropic, OpenAI, etc.) in n8n. (Optional) Set up the Google Drive Excel Merge sub-workflow to enrich ClientInfo with external data. Requirements GoHighLevel sub-account API key**. Anthropic (Claude)** API key or another supported LLM provider. Redis database** for temporary message storage. GHL automations: one for inbound messages to n8n, one for outbound replies when **IA\_answer is updated. GHL custom field: **IA\_answer to store and trigger replies. Wazzap plugin** in GHL for WhatsApp message handling. How to customize the workflow Add more context or business-specific data to the AI Agent prompt so replies match your brand tone and policies. Expand the ClientInfo dataset with additional services, branches, or product details. Adjust the Redis wait time to control how long the workflow buffers messages before replying.

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

Your Personal RSS Feed of YouTube Videos! This workflow creates an RSS feed containing the most recent videos published by your favorite channels. Use it in combination with your favorite RSS reader and don't miss out on any of your favorite creators' content without all the distractions of YouTube. You can even play the video right from your RSS reader without ever having to visit YouTube itself! Who's it for This workflow is for everyone who likes to keep updated about videos from their favorite creator through their preferred RSS app. How it works The RSS client triggers the webhook of this workflow The RSS feeds from your selected channels are pulled from YouTube The resulting feeds are filtered so only the normal videos (no shorts), posted in the last week, remain For each video, the video player and the full video description are pulled from the YouTube API For each video, an RSS item is created containing this video player and the video description as the content The RSS items are cached in a Redis database to prevent pulling the same information from the YouTube API on each webhook call A full RSS feed is built and returned to the calling webhook How to set up Follow the steps in the red notes (from 1 to 4) to configure the workflow: Set the IDs of the channels you want to watch Configure your Redis credentials Configure your Google/YouTube API credentials Copy the webhook URL and paste it into your RSS reader Don't forget to activate the workflow! Only the nodes inside a red node need configuration; all other nodes are good to go. You are, however, free to change those nodes to your liking! Requirements This workflow has 2 requirements: A Redis database used to cache the RSS items (see the blue note on how to set up a Redis database yourself) Google API credentials to access the YouTube API Customizing this workflow Add any YouTube channel you want by adding their channel ID in the "Set Channels" node at the start of this workflow. If you aren't afraid of some XML RSS code, you can dive into the code blocks and change the resulting RSS feed. You can change the feed's title, description, or image. Or go all in on text processing and process the video description before it is added to the RSS items (such as removing sponsors or links to social media). You can also extend this workflow by adding RSS items from other feeds or sources.

Description 'Elena AI' is a powerful n8n workflow that transforms your automation platform into a full-fledged, multi-agent AI hub. 🤖✨ By combining Redis state management with specialized “tool” sub-workflows, you can build contextual, scalable, and highly personalized conversational automations for WhatsApp, Telegram, email, and more. 🔥 Key Features Unified Ingestion** 📥 • Webhook trigger for text, audio, image, or document messages • Automatic extraction of remoteJid, user ID, and payload metadata Stateful Context** 🔄 • Redis push/get queue to preserve conversation history • Seamless handling of follow-ups and multi-turn dialogs Dynamic Routing** 🔀 • Smart Switch logic directs messages to the right agent workflow • Agents available: 🗓️ Malu: Google Calendar scheduling & reminders 💰 Maria: Expense logging & budget tracking in Baserow 👥 Mafalda: Contact CRUD operations in Baserow 📸 Marcela: Audio transcription & image analysis ✉️ Martina: Gmail send/receive & template replies Bite-Sized Responses** ✂️ • Splits long AI replies into line-by-line messages • Loop node controls rate & order for best UX Flexible Output** 📤 • HTTP Request node to deliver text, media, or files • Customize headers, payloads, and endpoints 🎯 Use Cases AI-powered customer support bots Automated lead qualification & follow-up Intelligent scheduling & reminders Expense approval workflows Multimedia content analysis & response 📋 Requirements n8n ≥ 1.0* with Webhook, *Redis, SplitInBatches, HTTP Request & Workflow nodes Redis** server (connection credentials in n8n) Service accounts / API keys for: Google Calendar (OAuth2) Baserow (API token) Gmail (OAuth2) Messaging API endpoint (HTTP) Environment variables set in n8n: REDIS_HOST, REDIS_PORT, REDIS_PASSWORD GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET BASEROW_API_TOKEN GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET MSG_API_URL, MSG_API_KEY 🚀 Quick Start Import the ElenaAI.json into n8n. Configure credentials and environment variables under Settings → Credentials. Link sub-workflows (Malu, Maria, Mafalda, Marcela, Martina) by updating their Workflow IDs in the main node. Test via Execute node or send a sample webhook payload. Deploy by exposing the Webhook endpoint to your messaging platform. Unlock seamless, AI-driven conversations across any channel—get MavenBot 2.0 running in minutes! 🚀

Build a Redis-Powered CRUD App with HTML Frontend This workflow demonstrates how to use n8n to build a complete, self-contained CRUD (Create, Read, Update, Delete) application without relying on any external server or hosting. It not only acts as the backend, handling all CRUD operations through Webhook endpoints, but also serves a fully functional HTML Single Page Application (SPA) directly via a webhook response. Redis is used as a lightweight data store, providing fast and simple key-value storage with auto-incremented IDs. Because both the frontend (HTML app) and backend (API endpoints) are managed entirely within a single n8n workflow, you can quickly prototype or deploy small tools without additional infrastructure. This approach is ideal for: Rapidly creating no-code or low-code applications Running fully browser-based tools served directly from n8n Teaching or demonstrating n8n + Redis integration in a single workflow Features Add new item with auto-incremented ID Edit existing item Delete specific item Reset all data (clear storage and reset autoincrement id) Single HTML frontend for demonstration (no framework required) Setup Instructions Prerequisites Before importing and running the workflow, make sure you have: A running n8n instance (self-hosted or cloud) A running Redis server (local or remote) API Path Setup For the REST API, use a consistent path. For example, if you choose items as the path: 2a. Get All Items** Method: GET Endpoint: items 2b. Add Item** Method: POST Endpoint: items 2c. Edit Item** Method: PUT Endpoint: items 2d. Delete Item** Method: DELETE Endpoint: items 2e. Reset Items** Method: POST Endpoint: items-reset Configure the API URL Set the API URL in the SET API URL node. Use your n8n webhook URL, for example: https://yourn8n.com/webhook/items Run the HTML App Once everything is set: Open the webhook URL for the HTML app in a browser. The CRUD interface will load and connect to the API endpoints automatically. You can now add, edit, delete, or reset items directly from the web interface. Workflows Render the HTML CRUD App This webhook serves a self-contained HTML Single Page Application (SPA) for basic CRUD operations. The HTML content is returned directly in the webhook response. This setup is ideal for lightweight, browser-based tools without external hosting. How to Use Open the webhook URL in a browser The CRUD interface will load and connect to the data source via API calls Before using, make sure to edit the api_url in the SET API URL node to match your webhook endpoint 2a. REST API: Get All Items This webhook handles retrieving all saved items from Redis. Each item is returned with its corresponding ID and associated data (e.g., name). This endpoint is used by the HTML CRUD App to display the full list of items. Method**: GET Function**: Fetches all items stored in Redis and returns them as a JSON array 2b. REST API: Add Item This webhook handles the Add Item functionality. This endpoint is typically called by the HTML CRUD App when adding a new item. Method**: POST Request Body**: { "name": "item name" } Function**: Generates an auto-incremented ID using Redis and saves the data under that ID 2c. REST API: Edit Item This webhook handles updating an existing item in Redis. Method**: PUT Request Body**: { "id": 1, "name": "Updated Item Name" } Function**: Finds the item by the given id and updates its data in Redis 2d. REST API: Delete Item This webhook handles deleting a specific item from Redis. Method**: DELETE Request Body**: { "id": 1 } Function**: Removes the item with the given id from Redis 2e. REST API: Reset Items This webhook handles resetting all data in the application. Method**: POST Function**: Deletes all stored items from Redis Resets the auto-increment ID by deleting the data in Redis

This workflow demonstrates how to can use Redis to implement rate limits to your API. The workflow uses the incoming API key to uniquely identify the user and use it as a key in Redis. Every time a request is made, the value is incremented by one, and we check for the threshold using the IF node. Duplicate the following Airtable to try out the workflow: https://airtable.com/shraudfG9XAvqkBpF