Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Google Drive to Vector DB Automation

Google Drive to Vector DB Automation is a 14-node automation blueprint connecting OpenAI, Google Drive, Postgres PGVector. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIGoogle DrivePostgres PGVector

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

14

Nodes

16

Links

1

Run groups

Connected tools

3 integrations

  • OpenAI
  • Google Drive
  • PostgreSQL

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive to Vector DB Automation execution lanes1 run groups containing 14 workflow nodes and 16 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTSchedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTSearch Folder. Google Drive node, googleDrive. 2 incoming and 1 outgoing connections.STEP 02Search FolderGOOGLE DRIVEGOOGLEDRIVE2 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTDownload File. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 04Download FileGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 3 outgoing connections.STEP 05SwitchDECISIONSWITCH1 IN / 3 OUTExtract from PDF. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 06Extract from PDFINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTExtract from Text. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 07Extract from TextINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTExtract from JSON. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 08Extract from JSONINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTPostgres PGVector Store. PostgreSQL node, vectorStorePGVector. 5 incoming and 1 outgoing connections.STEP 09Postgres PGVector StorePOSTGRESQLVECTORSTOREPGVECTOR5 IN / 1 OUTMove File. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.OUTCOMEMove FileGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTEmbeddings OpenAI. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings OpenAIOPENAIEMBEDDINGSOPENAI0 IN / 1 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTRecursive Character Text Splitter. ai node, textSplitterRecursiveCharacterTextSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Recursive Character Text …AITEXTSPLITTERRECURSIVECH0 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.14 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

When clicking ‘Test workflow’

13 Execution Links3 Support Dependencies

  1. Start

    When clicking ‘Test workflow’

    Trigger

    Schedule Trigger

    Trigger

  2. Step 2

    Search Folder

    Integration

  3. Step 3

    Loop Over Items

    Integration

  4. Step 4

    Download File

    Integration

  5. Step 5

    Switch

    Decision

  6. Step 6

    Extract from PDF

    Integration

  7. Step 7

    Extract from Text

    Integration

  8. Step 8

    Extract from JSON

    Integration

  9. Step 9

    Postgres PGVector Store

    AI reasoning

  10. Outcome

    Move File

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

3 nodes

  • Embeddings OpenAI

    AI reasoning dependency

  • Default Data Loader

    AI reasoning dependency

  • Recursive Character Text Splitter

    AI reasoning dependency

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas