📥 Transform Google Drive Documents into Vector Embeddings
n8n template #3647Summary
Use templateAutomatically convert documents from Google Drive into vector embeddings using OpenAI, LangChain, and PGVector — fully automated through n8n. ⚙️ What It Does This workflow monitors a Google Drive folder for new files, supports multiple file types (PDF, TXT, JSON), and processes them into vector embeddings using OpenAI’s text-embedding-3-small model. These embeddings are stored in a Postgres database using the PGVector extension, making them query-ready for semantic search or RAG-based AI agents. After successful processing, files are moved to a separate “vectorized” folder to avoid duplication. 💡 Use Cases Powering Retrieval-Augmented Generation (RAG) AI agents Semantic search across privat
Hand off to your agent
Prompt
Help me set up the n8n workflow "📥 Transform Google Drive Documents into Vector Embeddings" (https://n8n.io/workflows/3647). It uses: Google Drive, Embeddings OpenAI, Recursive Character Text Splitter, Default Data Loader, Postgres PGVector Store. Import the template JSON into my n8n instance, list every credential I need to create, and walk me through testing it.
Paste into Claude Code and it will do the rest.
Apps and nodes
Google DriveEmbeddings OpenAIRecursive Character Text SplitterDefault Data LoaderPostgres PGVector Store
Similar workflows
NameViews
- Chat with PDF docs using AI (quoting sources)95K
- HR & IT Helpdesk Chatbot with Audio Transcription36K
- Automate sales cold calling pipeline with Apify, gpt-5.6-terra, and WhatsApp34K
- Supabase Insertion & Upsertion & Retrieval24K
- Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG10K
- Generating Image Embeddings via Textual Summarisation7,286
- AI Agent To Chat With Files In Supabase Storage and Google Drive5,693
- Build & Query RAG System with Google Drive, OpenAI GPT-4o-mini, and Pinecone3,336