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

Google Drive Document Processor

Google Drive Document Processor is a 13-node automation blueprint connecting Google Drive, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveOpenAI

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

11

Links

2

Run groups

Connected tools

2 integrations

  • Google Drive
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive Document Processor execution lanes2 run groups containing 13 workflow nodes and 11 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 Executed by Another Workflow. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTWhen Executed by Another …TRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTOperation. decision node, switch. 1 incoming and 1 outgoing connections.STEP 02OperationDECISIONSWITCH1 IN / 1 OUTDownload File1. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Download File1GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTFileType. decision node, switch. 1 incoming and 4 outgoing connections.STEP 04FileTypeDECISIONSWITCH1 IN / 4 OUTExtract from PDF. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 05Extract from PDFINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTExtract from CSV. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 05Extract from CSVINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTAnalyse Image. OpenAI node, openAi. 1 incoming and 0 outgoing connections.STEP 05Analyse ImageOPENAIOPENAI1 IN / 0 OUTTranscribe Audio. OpenAI node, openAi. 1 incoming and 0 outgoing connections.STEP 05Transcribe AudioOPENAIOPENAI1 IN / 0 OUTGet PDF Response. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEGet PDF ResponseTRANSFORMSET1 IN / 0 OUTGet CSV Response. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEGet CSV ResponseTRANSFORMSET1 IN / 0 OUTGoogle Drive MCP Server. Google Drive node, mcpTrigger. 2 incoming and 0 outgoing connections.CORE RUNTIMEGoogle Drive MCP ServerGOOGLE DRIVEMCPTRIGGER2 IN / 0 OUTSearch Files from Gdrive. Google Drive node, googleDriveTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Search Files from GdriveGOOGLE DRIVEGOOGLEDRIVETOOL0 IN / 1 OUTRead File From GDrive. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Read File From GDriveAITOOLWORKFLOW0 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 Executed by Another Workf…

9 Execution Links

  1. Start

    When Executed by Another Workflow

    Trigger

  2. Step 2

    Operation

    Decision

  3. Step 3

    Download File1

    Integration

  4. Step 4

    FileType

    Decision

  5. Step 5

    Extract from PDF

    Integration

    Extract from CSV

    Integration

    Analyse Image

    AI reasoning

    Transcribe Audio

    AI reasoning

  6. Outcome

    Get PDF Response

    Transform

    Get CSV Response

    Transform

02

Run Group

Google Drive MCP Server

0 Execution Links2 Support Dependencies

  1. Core Runtime

    Google Drive MCP Server

    Trigger

Attached dependencies

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

2 nodes

  • Search Files from Gdrive

    Integration dependency

  • Read File From GDrive

    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