Block 1 - Aggregate1
- Type / Role
- n8n-nodes-base.aggregate - aggregate
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This n8n workflow is the data ingestion pipeline for the "RAG System V2" chatbot. It automatically monitors a specific Google Drive folder for new files, processes them based on their type, and ins...
n8n-nodes-base.aggregate, n8n-nodes-base.summarize, n8n-nodes-base.extractfromfile, n8n-nodes-base.httprequest, n8n-nodes-base.googledrive, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, @n8n/n8n-nodes-langchain.embeddingsopenai
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by edisantosa.
Original n8n.io sourceThis n8n workflow is the data ingestion pipeline for the "RAG System V2" chatbot. It automatically monitors a specific Google Drive folder for new files, processes them based on their type, and inserts their content into a Supabase vector database to make it searchable for the RAG agent.
Key Features & Workflow:
Google Drive Trigger: The workflow starts automatically when a new file is created in a designated folder (named "DOCUMENTS" in this template).
Smart File Handling: A Switch node routes the file based on its MIME type (e.g., PDF, Excel, Google Doc, Word Doc) for correct processing.
Multi-Format Extraction:
PDF: Text is extracted directly using the Extract PDF Text node.
Google Docs: Files are downloaded and converted to plain text (text/plain) and processed by the Extract from Text File node.
Excel: Data is extracted, aggregated, and concatenated into a single text block for embedding.
Word (.doc/.docx): Word files are automatically converted into Google Docs format using an HTTP Request. This newly created Google Doc will then trigger the entire workflow again, ensuring it's processed correctly.
Chunking & Metadata Enrichment: The extracted text is split into manageable chunks using the Recursive Character Text Splitter (set to 2000-character chunks). The Enhanced Default Data Loader then enriches these chunks with crucial metadata from the original file, such as file_name, creator, and created_at.
Vectorization & Storage: Finally, the workflow uses OpenAI Embeddings to create vector representations of the text chunks and inserts them into the Supabase Vector Store.
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 | Multi-format document processing for RAG chatbot with Google Drive & Supabase |
|---|---|
| Complexity | advanced |
| Nodes | 18 |
| Categories | Document Extraction, AI RAG |
| Author | edisantosa |
| Published | 20 Oct 2025 |
Use the JSON export at /data/workflows/9933/9933.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 n8n workflow is the data ingestion pipeline for the "RAG System V2" chatbot. It automatically monitors a specific Google Drive folder for new files, processes them based on their type, and ins...
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 Document Extraction, AI RAG use case.