Block 1 - When chat message received
- Type / Role
- @n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
- Config choices
- Version 1.4
An end to end Retrieval Augmented Generation (RAG) customer support workflow for n8n , using a cache first strategy (LangCache) combined with a Redis vector store powered by OpenAI embeddings . Thi...
@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.splitout, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.splitinbatches
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mohamed Abdelwahab.
Original n8n.io sourceAn end-to-end Retrieval-Augmented Generation (RAG) customer support workflow for n8n, using a cache-first strategy (LangCache) combined with a Redis vector store powered by OpenAI embeddings. This template is designed for fast, accurate, and cost-efficient customer support chatbots, internal help desks, and knowledge-base assistants.
This workflow implements a production-ready RAG architecture optimized for customer support use cases. Incoming chat messages are processed through a structured pipeline that prioritizes cached answers, falls back to semantic vector search when needed, and validates response quality before returning a final answer.
The workflow supports:
The workflow starts when a new chat message is received.
A centralized configuration node defines:
0.75)2)The user message is analyzed and decomposed into:
This improves retrieval accuracy and cache reuse.
Each sub-question is processed independently:
If no cache hit exists:
The research agent:
"no info found" if no relevant data existsEach generated answer is evaluated by a dedicated quality-check node:
SCORE (0.0 – 1.0)High-quality answers are saved back to LangCache for future reuse.
All sub-answers are aggregated and synthesized into:
Create the following credentials in n8n:
Update the configuration node with:
langcacheBaseUrllangcacheCacheId0.7 – 0.851 – 30.7customer-support, RAG, knowledge-base, redis, openai, langcache, chatbot, n8n-templateThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 38 workflow blocks. Download the JSON for the full node graph.
| Workflow | Handle customer support queries with cache-first RAG using Redis, LangCache and OpenAI |
|---|---|
| Complexity | advanced |
| Nodes | 38 |
| Categories | Support Chatbot, AI RAG |
| Author | Mohamed Abdelwahab |
| Published | 02 Jan 2026 |
Use the JSON export at /data/workflows/12400/12400.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
An end to end Retrieval Augmented Generation (RAG) customer support workflow for n8n , using a cache first strategy (LangCache) combined with a Redis vector store powered by OpenAI embeddings . Thi...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI RAG use case.