Most-used Redis workflows
- L&d_agentsai_ativo (93 nodes)
- Camila Ia — n8n Redis workflow (92 nodes)
- Bread-meat-delivery (91 nodes)
- Reagendamiento_v2 — n8n Redis workflow (89 nodes)
- Sync Tasks Between Notion and Todoist in Both Directions with Redis (85 nodes)
- Build a Whatsapp AI Shopping Bot with Virtual Try-on Using Gemini and Gpt — n8n Redis workflow (83 nodes)
- Aura-bot (82 nodes)
- My Workflow 7 — n8n Redis workflow (77 nodes)
- My Workflow 7 (open Ai) (77 nodes)
- AI Personal Assistant with Gpt-4o, RAG & Voice for Whatsapp Using Supabase — n8n Redis workflow (76 nodes)
L&D_AgentsAI_ATIVO. Uses httpRequest, agent, googleCalendarTool, toolSerpApi. Webhook trigger; 93 nodes.
Camila IA. Uses postgres, crypto, redis, agent. Webhook trigger; 92 nodes.
Bread-Meat-Delivery. Uses lmChatOpenAi, agent, httpRequest, redis. Webhook trigger; 91 nodes.
Reagendamiento_v2. Uses executeWorkflowTrigger, redis, httpRequest, n8n-nodes-evolution-api. Event-driven trigger; 89 nodes.
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
📌 Overview
Aura-bot. Uses postgres, lmChatOpenAi, memoryBufferWindow, httpRequest. Webhook trigger; 82 nodes.
My workflow 7. Uses openAi, redis, httpRequest, agent. Webhook trigger; 77 nodes.
My workflow 7. Uses openAi, redis, httpRequest, agent. Webhook trigger; 77 nodes.
Hi! I’m Amanda, a creator of intelligent automations using n8n and Make. I’ve been building AI-powered workflows for over 2 years, always focused on usability and innovation. This one here is very spe
Reagendamiento. Uses executeWorkflowTrigger, redis, n8n-nodes-evolution-api, dataTable. Event-driven trigger; 73 nodes.
⚡AI-Powered YouTube Playlist & Video Summarization and Analysis v2. Uses lmChatGoogleGemini, agent, splitOut, chainLlm. Chat trigger; 72 nodes.
This n8n workflow transforms entire YouTube playlists or single videos into interactive knowledge bases you can chat with. Ask questions and get summaries without needing to watch hours of content. 🔗
Transform your salon/service business with this streamlined WhatsApp automation system featuring Claude integration, zero-setup database management, and intelligent conversation handling. Claude MCP I
This workflow fully automates your team's daily standup process using Slack for communication, Notion for structured data storage, and Redis for real-time session management.
Flux. Uses lmChatOpenAi, agent, googleGemini, httpRequest. Webhook trigger; 67 nodes.
Transform your salon/service business with this streamlined Telegram automation system featuring Claude integration, zero-setup database management, and intelligent conversation handling. Claude MCP I
I originally started to template to ask questions on the "n8n @ scale office-hours" livestream videos but then extended it to include the latest videos on the official channel.
z-Api. Uses httpRequest, openAi, redis, postgres. Webhook trigger; 61 nodes.
Agendamiento. Uses n8n-nodes-evolution-api, redis, dataTable, executeWorkflowTrigger. Event-driven trigger; 60 nodes.
debug. Uses httpRequest, slack, redis, mailgun. Scheduled trigger; 60 nodes.
Agendamiento_v2. Uses n8n-nodes-evolution-api, redis, httpRequest, executeWorkflowTrigger. Event-driven trigger; 59 nodes.
Brokeria-v20. Uses n8n-nodes-waha, httpRequest, redis, googleGemini. Webhook trigger; 56 nodes.
Agent: IPTV (instance_e2165d22_1762376395079). Uses openAi, redis, supabase, httpRequest. Webhook trigger; 56 nodes.
Final. Uses chatTrigger, agent, n8n-nodes-upstage, httpRequest. Chat trigger; 55 nodes.
Brokeria-v15. Uses n8n-nodes-waha, httpRequest, postgres, redis. Webhook trigger; 55 nodes.
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 l
AI Sales Development Representative for WhatsApp Leads. Uses supabase, redis, agent, lmChatOpenAi. Webhook trigger; 53 nodes.
Agente_Atendimento_E_commerce. Uses baserow, redis, openAi, httpRequest. Webhook trigger; 52 nodes.
Fluxo Nia App - Agendamento Multi-tenant. Uses redis, httpRequest, openAi, whatsApp. Webhook trigger; 52 nodes.
Addendo — Blog Automatico Don Jacinto Nahual. Uses httpRequest, redis, github, gmail. Scheduled trigger; 51 nodes.
Addendo — Blog Automatico Don Jacinto Nahual. Uses httpRequest, redis, github, gmail. Scheduled trigger; 51 nodes.
Automatically capture, categorize, and log expenses from receipts, PDFs, voice notes, or text — powered by AI and integrated with Telegram and Google Sheets.
'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, yo
W1 - IN WhatsApp Adapter (Secure + Fast ACK). Uses postgres, redis, httpRequest. Webhook trigger; 48 nodes.
Splitout Redis. Uses executeWorkflowTrigger, n8n, redis, splitOut. Event-driven trigger; 46 nodes.
3770. Uses executeWorkflowTrigger, n8n, redis, agent. Event-driven trigger; 46 nodes.
Cancelacion_v2. Uses executeWorkflowTrigger, redis, httpRequest, n8n-nodes-evolution-api. Event-driven trigger; 46 nodes.
Designing agent tools for outcome rather than utility has been a long recommended practice of mine and it applies well when it comes to building MCP servers; In gist, agents to be making the least amo
Workflow 3770. Uses executeWorkflowTrigger, n8n, redis, agent. Event-driven trigger; 46 nodes.
Build your own N8N Workflows MCP Server. Uses executeWorkflowTrigger, n8n, redis, agent. Event-driven trigger; 46 nodes.
SDR NINJA | WhatsApp | Texto, Áudio, Documentos, Imagens. Uses redis, executionData, memoryRedisChat, openAi. Webhook trigger; 45 nodes.
BIG-AGENT-V4-CONVERSAS. Uses redis, supabase, httpRequest, agent. Webhook trigger; 44 nodes.
humanized-telegram-bot. Uses telegram, openAi, httpRequest, redis. Event-driven trigger; 44 nodes.
Prevent concurrent workflow runs using Redis. Uses executeWorkflowTrigger, manualTrigger, stickyNote, executeWorkflow. Event-driven trigger; 43 nodes.
This workflow sets a small "lock" value in Redis so that only one copy of a long job can run at the same time. If another trigger fires while the job is still busy, the workflow sees the lock, stops e
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 [](https://gist.g
Conversational Interviews With Ai Agents And N8N Forms. Uses memoryManager, stickyNote, formTrigger, form. Event-driven trigger; 40 nodes.
Conversational Interviews With Ai Agents And N8N Forms. Uses memoryManager, stickyNote, formTrigger, form. Event-driven trigger; 40 nodes.
Telegram Redis. Uses telegramTrigger, telegram, redis, googleSheets. Event-driven trigger; 40 nodes.
This n8n template combines an AI agent with n8n's multi-page forms to create a novel interaction which allows automated question-and-answer sessions. One of the more obvious use-cases of this interact
This n8n template uses a Telegram chatbot to conduct a Product Satisfaction Survey and fetches questions and stores answers in a Google sheet. It augments an AI Agent to ask follow-up questions to eng
> ⚠️ 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 responsib
Template was created in n8n v1.90.2 Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node AI Agent node If node, Switch node, Code node, Edit Fields (Set) Execute Sub-workflow T
SDR Instagram. Uses httpRequest, openAi, memoryRedisChat, executionData. Webhook trigger; 40 nodes.
BIG-AGENT-V3-SUPABASE. Uses redis, supabase, httpRequest, agent. Webhook trigger; 40 nodes.
Telegram Code. Uses telegram, redis, lmChatOpenAi, memoryRedisChat. Event-driven trigger; 39 nodes.
Workflow 3350. Uses telegram, redis, lmChatOpenAi, memoryRedisChat. Event-driven trigger; 39 nodes.
3350. Uses telegram, redis, lmChatOpenAi, memoryRedisChat. Event-driven trigger; 39 nodes.
In this experiment, we play with the idea of states we want our agent to be in which controls it's interacton with the user. First state* - the agent is onboarding the user by collecting their details
BIG-AGENT-V3-PRO. Uses redis, supabase, httpRequest, agent. Webhook trigger; 39 nodes.
Template was created in n8n v1.90.2 Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node AI Agent node If node, Switch node, Code node, Edit Fields (Set) Execute Sub-workflow T
This workflow automates customer feedback processing by analyzing sentiment, identifying key issues, generating personalized responses, and escalating critical cases to support teams when required. De
Whatsap Evolution API V2.2.3. Uses httpRequest, redis, toolCalculator, toolWikipedia. Webhook trigger; 38 nodes.
Perform comprehensive research on a user's query by dynamically generating search terms, querying the web using Google Search (by Gemini) , reflecting on the results to identify knowledge gaps, and it
This workflow is for contractors, freelancers, local service businesses, and small teams that receive leads and customer requests through Gmail but do not have a dedicated sales or admin team.
Memory sessions with FlowiseAI and Zep. Uses telegram, redis, telegramTrigger, httpRequest. Event-driven trigger; 37 nodes.
AI Comprehensive Research on User's Query (reproduction of gemini-fullstack-langgraph-quickstart). Uses lmChatGoogleGemini, outputParserStructured, chainLlm, redis. Chat trigger; 37 nodes.
Delivery. Uses memoryPostgresChat, lmChatOpenAi, toolCalculator, redis. Webhook trigger; 37 nodes.
B.IA-v.0.3.0. Uses agent, lmChatGroq, n8n-nodes-evolution-api, httpRequest. Webhook trigger; 37 nodes.
Telegram Wait. Uses stickyNote, httpRequest, redis, noOp. Event-driven trigger; 36 nodes.
Automates the forwarding of messages from WhatsApp (via Evolution API) to Chatwoot, enabling seamless integration between external WhatsApp users and internal Chatwoot agents. It supports both text an
A robust n8n workflow designed to enhance Telegram bot functionality for user management and broadcasting. It facilitates automatic support ticket creation, efficient user data storage in Redis, and a
Powertech Whatsapp. Uses whatsAppTrigger, whatsApp, httpRequest, googleGemini. Event-driven trigger; 36 nodes.
Agente de Agendamento YT (V.2). Uses googleSheets, n8n-nodes-evolution-api, openAi, redis. Webhook trigger; 36 nodes.
👥 Who's it for This workflow is perfect for businesses or individuals who want to automate WhatsApp conversations 💬 with an intelligent AI chatbot that can handle text, voice notes 🎵, and images 🖼️. N
Template was created in n8n v1.90.2 Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node Telegram node HTTP Request node If node, Code node, Edit Fields (Set) Execute Sub-workf
Template was created in n8n v1.90.2 Chat Trigger node Telegram Trigger node Redis node Postgres node Execute Sub-workflow If node, Code node, Edit Fields (Set), Extract From File Community nodes: n8n-
[](https://www.linkedin.com/in/mosaab-yassir-lafrimi/)[](https://t.me/joevenner)
BIG-AGENT-V5-FIXED. Uses redis, supabase, agent, lmChatAnthropic. Webhook trigger; 35 nodes.
Template was created in n8n v1.90.2 Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node Google Calendar node Execute Sub-workflow If node, Switch node, Code node, Edit Fields
Agente IA, WhatsApp, Flowise, N8N Y Chatwoot. Uses whatsApp, httpRequest, openAi, redis. Webhook trigger; 33 nodes.
Response_Handler. Uses httpRequest, dataTable, n8n-nodes-evolution-api, redis. Webhook trigger; 32 nodes.
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.
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
Wait Redis. Uses manualTrigger, noOp, informationExtractor, lmChatOpenAi. Event-driven trigger; 30 nodes.
This workflow implements a lightweight message-batching buffer using Redis for temporary storage and a JavaScript consolidation function to merge messages. It collects incoming user messages per sessi
Template was created in n8n v1.90.2 Execute Sub-workflow Trigger node Chat Trigger node Redis node Postgres node AI Agent node Calculator node If node, Switch node, Code node, Edit Fields (Set) Execut
W4.1 - ROUTER (State + Voice). Uses executeWorkflowTrigger, postgres, redis. Event-driven trigger; 30 nodes.
When we text or chat casually, it's not uncommon to break our sentences over multiple messages or when it comes to voice, break our speech with the odd pause or umms and ahhs. If an agent replies to e
Content Assistant. Uses telegramTrigger, executionData, telegram, openAi. Event-driven trigger; 28 nodes.
This workflow automatically replies to new comments on your Instagram posts using smart AI. It checks your recent posts, finds unread comments, and skips spam or duplicates. The AI reads the post and
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
The system collects real-time wearable health data, normalizes it, and uses AI to analyze trends and risk scores. It detects anomalies by comparing with historical patterns and automatically triggers
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. Bu
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
o1 - mini. Uses redis, httpRequest, chatTrigger. Chat trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Response_Handler_v2. Uses httpRequest, n8n-nodes-evolution-api, redis. Webhook trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Transform any problem into innovative solutions using AI-powered brainstorming that combines mathematical randomness with intelligent synthesis.
Github Releases. Uses limit, splitInBatches, scheduleTrigger, slack. Scheduled trigger; 24 nodes.
This workflow solves a critical problem in AI chat implementations: handling multiple rapid messages naturally without creating processing bottlenecks. Unlike traditional approaches where every user w
This n8n template monitors specified GitHub repositories. When a new release is published, it automatically fetches the information, uses AI (Google Gemini by default) to summarize and translate it in
Github Releases. Uses slack, informationExtractor, lmChatGoogleGemini, redis. Scheduled trigger; 24 nodes.
BIG-AGENT-V2-REDIS-NATIVO. Uses redis, supabase, agent, lmChatAnthropic. Webhook trigger; 24 nodes.
Redis Code. Uses manualTrigger, httpRequest, scheduleTrigger, redis. Event-driven trigger; 23 nodes.
This Template gives the ability to monitor all uplinks for your Meraki Dashboard and then alert your team in a method you prefer. This example is a Teams notification to our Dispatch Channel
Meraki Packet Loss and Latency Alerts to Microsoft Teams. Uses httpRequest, redis, microsoftTeams. Event-driven trigger; 23 nodes.
[](https://www.linkedin.com/in/mosaab-yassir-lafrimi/)[](https://t.me/joevenner)
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 22 nodes.
o1 - groq. Uses redis, httpRequest, chatTrigger. Chat trigger; 22 nodes.
I built this tool because we faced a real, recurring problem: managing hundreds of client projects in a weekly automated loop.
Agente Vendas Veículos - Completo. Uses redis, httpRequest, googleCalendar, googleSheetsTrigger. Webhook trigger; 21 nodes.
Statemachine. Uses redis, redisTrigger. Webhook trigger; 20 nodes.
Unlike approaches where you have to authenticate users prior to interacting with the agent, this approach allows guest users to authenticate at any time during the session or not at all.
This implementation aggregates incoming data into a Redis list from potentially concurrent workflow executions. It buffers the data for a set period before a single execution retrieves and processes t
GitHub Trending → Redis Dedup → AI Post → Telegram. Uses httpRequest, redis, telegram, chainLlm. Scheduled trigger; 19 nodes.
My workflow 15. Uses redis, agent, n8n-nodes-evolution-api, lmChatOpenAi. Webhook trigger; 19 nodes.
Wm-Chat-Main-2B.N8N-Import. Uses httpRequest, redis. Webhook trigger; 19 nodes.
Wait Redis. Uses lmChatOpenAi, noOp, redis, memoryBufferWindow. Event-driven trigger; 18 nodes.
Wait Redis. Uses lmChatOpenAi, noOp, redis, memoryBufferWindow. Event-driven trigger; 18 nodes.
2346. Uses lmChatOpenAi, redis, memoryBufferWindow, twilioTrigger. Event-driven trigger; 18 nodes.
Workflow 2346. Uses lmChatOpenAi, redis, memoryBufferWindow, twilioTrigger. Event-driven trigger; 18 nodes.
This project is an AI-powered hotel receptionist built using n8n, designed to handle guest queries automatically through WhatsApp. It integrates Google Gemini, Redis, MySQL, and Google Sheets via Lang
This n8n workflow demonstrates a simple approach to improve chat UX by staggering an AI Agent's reply for users who send in a sequence of partial messages and in short bursts. Twilio webhook receives
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,
VocTest — Chat Conversacional. Uses redis, lmChatOpenAi, memoryRedisChat, agent. Webhook trigger; 18 nodes.
VocTest — Chat Conversacional. Uses redis, lmChatOpenAi, memoryRedisChat, agent. Webhook trigger; 18 nodes.
Wm-Followup-Cron.N8N-Import. Uses redis, httpRequest, postgres. Scheduled trigger; 18 nodes.
Addendo — Alert Router Central v1. Uses redis, gmail, httpRequest. Webhook trigger; 18 nodes.
Redis Schedule. Uses executeWorkflow, scheduleTrigger, redis, noOp. Scheduled trigger; 17 nodes.
OTP Generator. Uses gmail, redis, telegramTrigger, twilio. Event-driven trigger; 17 nodes.
Wm-State-Engine.N8N-Import. Uses redis, postgres. Webhook trigger; 17 nodes.
Wm-State-Engine.N8N-Import. Uses redis, postgres. Webhook trigger; 17 nodes.
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
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins
How It Works Telegram bot listens for messages and uses chat ID as the unique user identifier. Checks Google Sheets for existing users; registers new users if not found. Caches active sessions in Redi
W5 - OUT WhatsApp Sender (Meta Cloud API). Uses executeWorkflowTrigger, redis. Event-driven trigger; 14 nodes.
W7 - OUT Messenger Sender (Meta Send API). Uses executeWorkflowTrigger, redis. Event-driven trigger; 14 nodes.
del_redis_supa. Uses redis, supabase. Event-driven trigger; 12 nodes.
Wm-Admin.N8N-Import. Uses postgres, httpRequest, redis. Webhook trigger; 12 nodes.
My workflow 3. Uses httpRequest, redis. Event-driven trigger; 12 nodes.
Use Redis To Rate Limit Your Low Code Api. Uses airtable, redis. Webhook trigger; 11 nodes.
n8n-3-6: Flux Redis Master Bot. Uses telegramTrigger, openAi, telegram, redis. Event-driven trigger; 11 nodes.
N8N-Amazon-Affiliate-Links.Workflow. Uses redis, httpRequest, gmail. Webhook trigger; 10 nodes.
W16 - Health Check Endpoints (readyz/livez). Uses postgres, redis. Webhook trigger; 10 nodes.
New Ticket Alerts to Teams. Uses scheduleTrigger, redis, httpRequest, microsoftTeams. Scheduled trigger; 8 nodes.
Redis:info set keys get delete. Uses start, redis. Manual trigger; 8 nodes.
This Workflow does a HTTPs request to ConnectWise Manage through their REST API.
This ensures that executions of scheduled workflows do not overlap when they take longer than expected. This is a separate workflow which monitors the execution of the main workflow Stores a flag in R
n8n-3-6: Flux Redis Worker. Uses redis, httpRequest, telegram. Scheduled trigger; 8 nodes.
Cleaning Inspection - Submit. Uses redis. Webhook trigger; 7 nodes.
X-n8 Deduplication & Clustering Workflow. Uses redis. Event-driven trigger; 7 nodes.
OpenAI Chatbot with Redis Memory. Uses redis, openAi. Webhook trigger; 6 nodes.
Statemachinestatefind. Uses executeWorkflowTrigger, redis, httpRequest. Event-driven trigger; 6 nodes.
Agente GPT Deep. Uses chatTrigger, memoryRedisChat, toolWorkflow, redis. Chat trigger; 10 nodes.
EJEMPLO-n8n-redis-end-to-end. Uses redis. Webhook trigger; 4 nodes.
Get The Value Of A Key From Redis. Uses manualTrigger, redis. Event-driven trigger; 2 nodes.
168 of 168 workflows in this view · Browse all →
FAQ
How many n8n Redis workflows are in the catalog?
168 n8n workflows in AutomationFlows currently use the Redis integration — triggers, actions, or both.
How do I connect Redis in n8n?
After importing the workflow JSON, n8n will prompt for Redis credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Redis workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.