Block 1 - When clicking ‘Test workflow’
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This workflow automates the creation and management of a Retrieval Augmented Generation (RAG) system using Qdrant as a vector store and Google Drive as the document source. It enables full or incre...
n8n-nodes-base.manualtrigger, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.vectorstoreqdrant, n8n-nodes-base.httprequest, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Davide.
Original n8n.io sourceThis workflow automates the creation and management of a Retrieval-Augmented Generation (RAG) system using Qdrant as a vector store and Google Drive as the document source. It enables full or incremental updates to documents in the Qdrant vector database and integrates with a chatbot using Google Gemini for question answering.
Here is a clear and professional description in English of the n8n workflow “Create a RAG with Qdrant and update single files”, including its benefits:
Efficient RAG Setup Seamlessly integrates OpenAI, Qdrant, and Google Drive to create a scalable RAG pipeline.
Single File Update You can replace the vector representation of a single file without reprocessing the entire collection—ideal for maintaining document freshness.
Flexible File Source Works with Google Drive, allowing document management and updates from a familiar interface.
This workflow is designed to create a Retrieval-Augmented Generation (RAG) system using Qdrant as a vector store and Google Drive as a document source. It consists of four main phases:
Collection Setup:
Document Processing:
Single-File Update:
RAG Querying:
Configure Qdrant:
QDRANTURL and COLLECTION in the "Create collection" and "Clear collection" HTTP nodes. Google Drive Integration:
OpenAI and Gemini Keys:
Single-File Update:
file_id in the "Edit Fields3" node to target a specific Google Drive file for updates.Testing:
Contact me for consulting and support or add me on Linkedin.
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 | Build and update RAG system with Google Drive, Qdrant, and Gemini Chat |
|---|---|
| Complexity | advanced |
| Nodes | 29 |
| Categories | Internal Wiki, AI RAG |
| Author | Davide |
| Published | 23 Jun 2025 |
Use the JSON export at /data/workflows/5140/5140.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 automates the creation and management of a Retrieval Augmented Generation (RAG) system using Qdrant as a vector store and Google Drive as the document source. It enables full or incre...
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.