Vector DB Loader from Google Drive
Configured with Document Default Data Loader, Embeddings Open Ai, Extract From File, Google Drive, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Files / media
- Transform
- AI & models
- Data store
- Trigger
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Default Data Loader | Files / media | Document Default Data Loader | See node parameters |
| Recursive Character Text Splitter | Transform | Text Splitter Recursive Character Text Splitter | See node parameters |
| Embeddings OpenAI | AI & models | Embeddings Open Ai | See node parameters |
| Postgres PGVector Store | Data store | Vector Store Pgvector | See node parameters |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Loop Over Items | Routing | Loop Over Items | See node parameters |
| Move File | Files / media | Google Drive | move |
| Download File | Files / media | Google Drive | download |
| Search Folder | Files / media | Google Drive | fileFolder |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Switch | Routing | Switch | See node parameters |
| Extract from PDF | Transform | Extract From File | |
| Extract from Text | Transform | Extract From File | text |
| Extract from JSON | Transform | Extract From File | fromJson |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2ApiopenAiApipostgres
Workflow notes
Creative Commons License
Creative Commons License
License: Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
Author: AlexK1919 You are free to use, adapt, and share this workflow—even commercially—under the terms of this license.
Full license details: https://creativecommons.org/licenses/by-sa/4.0/
Vector DB Loader from Google Drive
Vector DB Loader from Google Drive
Purpose and structure
This folder contains the Vector DB Loader from Google Drive workflow. Its executable nodes use documentDefaultDataLoader, embeddingsOpenAi, extractFromFile, googleDrive, manualTrigger, scheduleTrigger, splitInBatches, switch, textSplitterRecursiveCharacterTextSplitter, vectorStorePGVector. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’, Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/1750_Schedule_Extractfromfile_Import_Scheduled.json MIT; preserve source notices.