Block 1 - Google Drive
- Type / Role
- n8n-nodes-base.googleDrive - googleDrive
- Config choices
- Version 3
This workflow is provided as-is. Please review and test before using in production.
Google Drive Upload Trigger → Pinecone Vector Upsert for Document Indexing Category: AI & LLM / Document Indexing Level: Intermediate Tags: Google Drive, Pinecone, OpenAI, Embeddings, Vector Sto...
n8n-nodes-base.googledrive, n8n-nodes-base.splitinbatches, @n8n/n8n-nodes-langchain.vectorstorepinecone, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, n8n-nodes-base.googledrivetrigger, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Automate With Marc.
Original n8n.io source🧠 Google Drive Upload Trigger → Pinecone Vector Upsert for Document Indexing Category: AI & LLM / Document Indexing Level: Intermediate Tags: Google Drive, Pinecone, OpenAI, Embeddings, Vector Store, LangChain, RAG
📄 What This Workflow Does This workflow watches a specific Google Drive folder and automatically uploads any newly added document to a Pinecone vector database — complete with OpenAI-generated embeddings.
Perfect for setting up retrieval-augmented generation (RAG) pipelines, semantic search, or document Q&A systems. Once configured, your knowledge base stays up-to-date with zero manual effort.
Watch Full Step By Stey Tutorial Video Here: https://www.youtube.com/@Automatewithmarc
🔧 How It Works 📁 Google Drive Trigger Watches a specific folder and triggers when new documents are uploaded.
🔍 Google Drive File Search & Download Finds and fetches all files in the folder.
🔄 Loop Over Each File Handles batch processing for multiple files.
📃 Document Loader Parses each file as binary and applies custom metadata like document type.
✂️ Text Splitter Breaks content into manageable chunks for embedding (e.g., 600 characters, 60 overlap).
🧠 OpenAI Embeddings Generates vector embeddings using OpenAI.
📦 Pinecone Vector Store Inserts/upserts documents into a specific Pinecone namespace for search-ready indexing.
🧠 Why This is Useful This is a production-grade setup for:
Building vector search tools over internal docs
Feeding up-to-date data into RAG agents or chatbots
Auto-tagging and chunking files for scalable AI workflows
Whether you’re indexing course outlines, SOPs, or technical docs — this automation keeps your vector store fresh and organized.
🪜 Setup Instructions Connect your Google Drive, OpenAI, and Pinecone accounts.
Specify the Google Drive folder to monitor.
Customize metadata, chunk size, or vector namespace as needed.
Activate the workflow and drop a file into the folder — magic happens behind the scenes.
📌 Notes Works best with PDFs or text-based documents.
You can swap out OpenAI with other embedding models if needed.
Consider adding notifications or logging (e.g., via Slack or email) for better observability.
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 | Index Documents from Google Drive to Pinecone with OpenAI Embeddings for RAG |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | Document Extraction, AI RAG |
| Author | Automate With Marc |
| Published | 01 Jun 2025 |
Use the JSON export at /data/workflows/4552/4552.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.
Google Drive Upload Trigger → Pinecone Vector Upsert for Document Indexing Category: AI & LLM / Document Indexing Level: Intermediate Tags: Google Drive, Pinecone, OpenAI, Embeddings, Vector Sto...
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.