Vector DB Loader from Google Drive

Overview

Free n8n workflow: Vector DB Loader from Google Drive. 15 nodes across documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Vector DB Loader from Google Drive" chains 15 nodes to move data between documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule. 15 nodes · documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

• Study how data moves from documentDefaultDataLoader to textSplitterRecursiveCharacterTextSplitter before building your own variant.
• Share it with your team as a documented reference for scheduled/triggered automations in the documentDefaultDataLoader stack.
• Import "Vector DB Loader from Google Drive" into n8n, reconnect credentials for documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule, and run the same automation in your own workspace.
• Use it as a starting template when wiring documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Vector DB Loader from Google Drive" exposes 15 configured nodes. Trigger type: scheduled/triggered. Integrations: documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule. Set your credentials on the documentDefaultDataLoader node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Frequently asked questions

How do I import "Vector DB Loader from Google Drive" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "Vector DB Loader from Google Drive" use?

It uses: documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule. The flow diagram above shows how each service connects across the 15 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own documentDefaultDataLoader and textSplitterRecursiveCharacterTextSplitter credentials in n8n after import.

What trigger type does "Vector DB Loader from Google Drive" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "Vector DB Loader from Google Drive" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for documentDefaultDataLoader, textSplitterRecursiveCharacterTextSplitter, embeddingsOpenAi, vectorStorePGVector, manual, splitInBatches, googleDrive, schedule.