Block 1 - Recursive Character Text Splitter
- Type / Role
- @n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter - textSplitterRecursiveCharacterTextSplitter
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This workflow demonstrates a simple Retrieval Augmented Generation (RAG) pipeline in n8n, split into two main sections: Part 1: Load Data into Vector Store Reads files from disk (or Google Drive...
@n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.chainretrievalqa, @n8n/n8n-nodes-langchain.retrievervectorstore, n8n-nodes-base.manualtrigger, @n8n/n8n-nodes-langchain.chattrigger, n8n-nodes-base.readwritefile
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by JustinLee.
Original n8n.io sourceThis workflow demonstrates a simple Retrieval-Augmented Generation (RAG) pipeline in n8n, split into two main sections:
🔹 Part 1: Load Data into Vector Store Reads files from disk (or Google Drive).
Splits content into manageable chunks using a recursive text splitter.
Generates embeddings using the Cohere Embedding API.
Stores the vectors into an In-Memory Vector Store (for simplicity; can be replaced with Pinecone, Qdrant, etc.).
🔹 Part 2: Chat with the Vector Store Takes user input from a chat UI or trigger node.
Embeds the query using the same Cohere embedding model.
Retrieves similar chunks from the vector store via similarity search.
Uses Groq-hosted LLM to generate a final answer based on the context.
🛠️ Technologies Used: 📦 Cohere Embedding API
⚡ Groq LLM for fast inference
🧠 n8n for orchestrating and visualizing the flow
🧲 In-Memory Vector Store (for prototyping)
🧪 Usage: Upload or point to your source documents.
Embed them and populate the vector store.
Ask questions through the chat trigger node.
Receive context-aware responses based on retrieved content.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Basic RAG chat |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | Internal Wiki, AI RAG |
| Author | JustinLee |
| Published | 18 Jun 2025 |
Use the JSON export at /data/workflows/5028/5028.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.
This workflow demonstrates a simple Retrieval Augmented Generation (RAG) pipeline in n8n, split into two main sections: Part 1: Load Data into Vector Store Reads files from disk (or Google Drive...
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 Internal Wiki, AI RAG use case.