Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

PDF AI Processing Workflow

PDF AI Processing Workflow is a 6-node automation blueprint connecting Google Drive, Gemini API, Claude API. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

6

Nodes

5

Links

1

Run groups

Connected tools

3 integrations

  • Google Drive
  • Google AI
  • Anthropic

Canvas controls

Fit wide systems, then zoom into any run group.

PDF AI Processing Workflow execution lanes1 run groups containing 6 workflow nodes and 5 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 OUTDefine Prompt. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Define PromptTRANSFORMSET1 IN / 1 OUTGoogle Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Google DriveGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTExtract from File. integration node, extractFromFile. 1 incoming and 2 outgoing connections.STEP 04Extract from FileINTEGRATIONEXTRACTFROMFILE1 IN / 2 OUTCall Claude 3.5 Sonnet with PDF Capabilities. Anthropic node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMECall Claude 3.5 Sonnet wi…ANTHROPICHTTPREQUEST1 IN / 0 OUTCall Gemini 2.0 Flash with PDF Capabilities. Google AI node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMECall Gemini 2.0 Flash wit…GOOGLE AIHTTPREQUEST1 IN / 0 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.6 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'

5 Execution Links
  1. Start

    When clicking 'Test workflow'

    Trigger

  2. Step 2

    Define Prompt

    Transform

  3. Step 3

    Google Drive

    Integration

  4. Step 4

    Extract from File

    Integration

  5. Outcome

    Call Claude 3.5 Sonnet with PDF Capabilities

    Integration

    Call Gemini 2.0 Flash with PDF Capabilities

    Integration

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.