Block 1 - When chat message received
- Type / Role
- @n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
Target Audience This guide is designed for developers, data scientists, and AI enthusiasts who want to create intelligent chatbots capable of understanding and using custom data. Whether you are bu...
@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.embeddingsopenai, n8n-nodes-base.googledrive, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, n8n-nodes-base.manualtrigger, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Zakaria Ben.
Original n8n.io sourceThis guide is designed for developers, data scientists, and AI enthusiasts who want to create intelligent chatbots capable of understanding and using custom data. Whether you are building a research assistant, a customer support bot, or an internal knowledge base tool, this workflow helps you integrate your own documents into an AI chat system.
Retrieval-Augmented Generation (RAG) is an AI architecture that combines information retrieval with text generation. Instead of relying solely on a model’s built-in knowledge, RAG retrieves relevant data from external sources—such as your uploaded documents—and feeds it into the AI’s reasoning process. This approach solves a major limitation of traditional language models: their inability to access or recall up-to-date or proprietary information. By using RAG, your chatbot can deliver accurate, context-aware answers drawn directly from your specific data.
Consider a scenario where your organization has a collection of internal reports, manuals, or research documents. With RAG, your AI chatbot can answer detailed questions about these materials without exposing sensitive data externally. This setup is ideal for teams working in customer support, technical documentation, education, or data analysis.
Add your document to the Supabase Vector Store using the "Add Document" feature after downloading or linking it via Google Drive.
The workflow retrieves and embeds your document’s content into the vector database for efficient search and retrieval.
When you ask a question, the AI retrieves the most relevant context from the Supabase Vector Store based on semantic similarity.
The AI combines the retrieved context with its generative capabilities to produce accurate, data-driven responses tailored to your input.
Before setting up the workflow, ensure you have the following:
A GitHub account
A Supabase account
A Google Drive document containing your data
Basic understanding of APIs and environment configuration
Create a GitHub account and clone the repository containing the workflow. Then, create a Supabase account and a new project to generate your API keys.
Upload your data to Google Drive and make it downloadable. Add the document to the Supabase Vector Store using the “Add Document” feature.
Set your Supabase keys as environment variables in your workflow configuration.
Execute the workflow to connect your document with the AI agent. Once configured, you can start chatting with the AI agent—your responses will now be powered by your own data.
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 | Build a RAG-powered AI assistant with OpenAI, Google Drive & Supabase Vector DB |
|---|---|
| Complexity | advanced |
| Nodes | 16 |
| Categories | Internal Wiki, AI RAG |
| Author | Zakaria Ben |
| Published | 20 Mar 2025 |
Use the JSON export at /data/workflows/3250/3250.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.
Target Audience This guide is designed for developers, data scientists, and AI enthusiasts who want to create intelligent chatbots capable of understanding and using custom data. Whether you are bu...
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.