Block 1 - Default Data Loader
- Type / Role
- @n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Chat with Internal Documents (RAG AI Agent) Features Answers should given only within provided text. Chat interface powered by LLM (Ollama) Retrieval Augmented Generation (RAG) using Supabase ...
@n8n/n8n-nodes-langchain.documentdefaultdataloader, n8n-nodes-base.stickynote, n8n-nodes-base.googledrive, n8n-nodes-base.googledrivetrigger, n8n-nodes-base.extractfromfile, @n8n/n8n-nodes-langchain.memorypostgreschat, n8n-nodes-base.supabase, n8n-nodes-base.set
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Lakindu Siriwardana.
Original n8n.io sourceWatches a Google Drive folder for new or updated files.
Deletes old vector entries for the file.
Uses conditional logic to extract content from PDFs, Excel, Docs, or text
Summarizes and preprocesses content. (if needed)
Splits and embeds the text via Ollama.
Stores embeddings in Supabase Vector DB
Chat is initiated via Webhook or built-in chat interface.
User input is passed to the RAG Agent.
Agent queries the User_documents tool (Supabase vector store) using the Ollama model to fetch relevant content.
If context is found, it answers directly.
Otherwise, it can call tools or request clarification.
Responses are returned to the user, with memory stored in PostgreSQL for continuity.
Create a Supabase project at https://supabase.com and go to the SQL editor.
Create a documents table with the following schema:
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.
Showing the first 24 of 29 workflow blocks. Download the JSON for the full node graph.
| Workflow | Chat with internal documents using Ollama, Supabase Vector DB & Google Drive |
|---|---|
| Complexity | advanced |
| Nodes | 29 |
| Categories | Internal Wiki, AI RAG |
| Author | Lakindu Siriwardana |
| Published | 02 Aug 2025 |
Use the JSON export at /data/workflows/6894/6894.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.
Chat with Internal Documents (RAG AI Agent) Features Answers should given only within provided text. Chat interface powered by LLM (Ollama) Retrieval Augmented Generation (RAG) using Supabase ...
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.