Google Drive Automated PDF Ingestion & Qdrant Vector Indexer
Event-driven ETL pipeline monitoring Google Drive for PDFs, extracting and chunking text, generating embeddings, and upserting vectors into Qdrant for RAG.
A question. A process.
Work you can explore.
Move from the project’s purpose to its available previews and source files.
Chapter 1 of 4 · The question
What this project explores.
Event-driven ETL pipeline monitoring Google Drive for PDFs, extracting and chunking text, generating embeddings, and upserting vectors into Qdrant for RAG.
Follow the implementation.
- 01
Monitored Google Drive folder for newly uploaded or updated PDF documents via event triggers.
- 02
Extracted raw text, applied Recursive Character Text Splitter, and generated embeddings with OpenAI.
- 03
Upserted vectors into Qdrant collections with metadata payload for document source attribution.
- 01Drive PDF
- 02Parse & split
- 03Embed text
- 04Qdrant index
Look beyond the project summary.
The workflow overview describes the documented stages. Use the source files to inspect their implementation.
Choose where to look deeper.
Search the linked source inventory or narrow it to the kind of artifact you want to inspect. Files open at their original source.
The source
keeps moving.
Source updated
Event-driven ETL pipeline monitoring Google Drive for PDFs, extracting and chunking text, generating embeddings, and upserting vectors into Qdrant for RAG.
Current README excerpt
Category: RAG & Knowledge Bases Automates document ingestion: monitors Google Drive folder for new PDFs, parses text, generates embeddings, and indexes into Qdrant.
A source excerpt, not an independently verified outcome.