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

Google Drive to Pinecone AI Workflow

Google Drive to Pinecone AI Workflow is a 13-node automation blueprint connecting Google Drive, OpenRouter, Pinecone. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveOpenRouterPineconeGoogle Gemini

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.

13

Nodes

13

Links

1

Run groups

Connected tools

4 integrations

  • Google Drive
  • OpenRouter
  • Pinecone
  • Google AI

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive to Pinecone AI Workflow execution lanes1 run groups containing 13 workflow nodes and 13 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 OUTGet Document From Google Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Get Document From Google …GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTExtract Text Data From Google Document. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 03Extract Text Data From Go…INTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTSplit Document Text Into Sections. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Split Document Text Into …TRANSFORMCODE1 IN / 1 OUTPrepare Sections For Looping. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 05Prepare Sections For Loop…TRANSFORMSPLITOUT1 IN / 1 OUTAI Agent - Prepare Context. ai node, agent. 2 incoming and 1 outgoing connections.STEP 06AI Agent - Prepare ContextAIAGENT2 IN / 1 OUTConcatenate the context and section text. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Concatenate the context a…TRANSFORMSET1 IN / 1 OUTPinecone Vector Store. Pinecone node, vectorStorePinecone. 3 incoming and 1 outgoing connections.STEP 08Pinecone Vector StorePINECONEVECTORSTOREPINECONE3 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.OUTCOMELoop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTOpenRouter Chat Model. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenRouter Chat ModelAILMCHATOPENROUTER0 IN / 1 OUTEmbeddings Google Gemini. Google AI node, embeddingsGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings Google GeminiGOOGLE AIEMBEDDINGSGOOGLEGEMINI0 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.13 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’

9 Execution Links4 Support Dependencies

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Get Document From Google Drive

    Integration

  3. Step 3

    Extract Text Data From Google Document

    Integration

  4. Step 4

    Split Document Text Into Sections

    Transform

  5. Step 5

    Prepare Sections For Looping

    Transform

  6. Step 6

    AI Agent - Prepare Context

    AI reasoning

  7. Step 7

    Concatenate the context and section text

    Transform

  8. Step 8

    Pinecone Vector Store

    AI reasoning

  9. Outcome

    Loop Over Items

    Integration

Attached dependencies

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

4 nodes

  • OpenRouter Chat Model

    AI reasoning dependency

  • Embeddings Google Gemini

    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