Block 1 - Google Drive Trigger
- Type / Role
- n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
What This Workflow Does This RAG Pipeline in n8n automates document ingestion from Google Drive, vectorizes it using OpenAI embeddings, stores it in Pinecone, and enables chat based retrieval us...
n8n-nodes-base.googledrivetrigger, n8n-nodes-base.googledrive, @n8n/n8n-nodes-langchain.vectorstorepinecone, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.chattrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Olusola.
Original n8n.io sourceπ What This Workflow Does
This RAG Pipeline in n8n automates document ingestion from Google Drive, vectorizes it using OpenAI embeddings, stores it in Pinecone, and enables chat-based retrieval using LangChain agents.
Main Functions:
π Auto-detects new files uploaded to a specific Google Drive folder. π§ Converts the file into embeddings using OpenAI. π¦ Stores them in a Pinecone vector database. π¬ Allows a user to query the knowledge base through a chat interface. π€ Uses a GPT-4o-mini model with LangChain to generate intelligent responses using retrieved context. βοΈ Setup Instructions
β Google Drive (OAuth2) β OpenAI β Pinecone You can do this in n8n > Credentials > New and use the matching names from the file:
Google Drive: "Google Drive account 2" OpenAI: "OpenAi success" Pinecone: "PineconeApi account 2" 2. Folder Setup Upload your documents to this folder in Google Drive:
π Power Folder
The workflow is triggered every minute when a new file is uploaded.
Google Drive Trigger β detects new file. Google Drive (Download) β downloads the new file. Recursive Text Splitter β splits text into chunks. Default Data Loader β loads content as LangChain documents. OpenAI Embeddings β converts text chunks into embeddings. Pinecone Vector Store β stores them in "ragfile" index. B. Chat Retrieval Path
When chat message received β AI Agent β LangChain agent managing tools. OpenAI Chat Model (GPT-4o-mini) β generates replies. Pinecone Vector Store (retrieval) β retrieves matching content. Embeddings OpenAI1 β helps match queries to document chunks.
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 & query RAG system with Google Drive, OpenAI GPT-4o-mini, and Pinecone |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | Internal Wiki, AI RAG |
| Author | David Olusola |
| Published | 30 May 2025 |
Use the JSON export at /data/workflows/4501/4501.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.
What This Workflow Does This RAG Pipeline in n8n automates document ingestion from Google Drive, vectorizes it using OpenAI embeddings, stores it in Pinecone, and enables chat based retrieval us...
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.