Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Google Drive Download Link Automator

Google Drive Download Link Automator is a 8-node automation blueprint connecting Google Drive. Inspect its trigger, execution graph, branches, and implementation requirements.

Google Drive

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.

8

Nodes

9

Links

1

Run groups

Connected tools

1 integrations

  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive Download Link Automator execution lanes1 run groups containing 8 workflow nodes and 9 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.Manual Execute Workflow. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTManual Execute WorkflowTRIGGERMANUALTRIGGER0 IN / 1 OUTSet Folder ID. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Folder IDTRANSFORMSET1 IN / 1 OUTGoogle Drive. Google Drive node, googleDrive. 1 incoming and 2 outgoing connections.STEP 03Google DriveGOOGLE DRIVEGOOGLEDRIVE1 IN / 2 OUTGenerate Download Links. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Generate Download LinksTRANSFORMCODE1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 05Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTChange Status. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 06Change StatusGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 07MergeDECISIONMERGE2 IN / 1 OUTReplace Me. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEReplace MeINTEGRATIONNOOP1 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.8 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

Manual Execute Workflow

9 Execution Links

  1. Start

    Manual Execute Workflow

    Trigger

  2. Step 2

    Set Folder ID

    Transform

  3. Step 3

    Google Drive

    Integration

  4. Step 4

    Generate Download Links

    Transform

  5. Step 5

    Loop Over Items

    Integration

  6. Step 6

    Change Status

    Integration

  7. Step 7

    Merge

    Decision

  8. Outcome

    Replace Me

    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.

Create a build planReturn to the atlas