Skip to Workflow Atlas
ETL PipelineIntermediate

Google Drive Folder Management Automation

Google Drive Folder Management Automation is a 11-node automation blueprint connecting Google Drive. 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.

11

Nodes

12

Links

1

Run groups

Connected tools

1 integrations

  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive Folder Management Automation execution lanes1 run groups containing 11 workflow nodes and 12 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 OUTExecute Workflow Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTExecute Workflow TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTDummy input data. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Dummy input dataTRANSFORMSET1 IN / 1 OUTSplit the desired path. transform node, code. 2 incoming and 1 outgoing connections.STEP 03Split the desired pathTRANSFORMCODE2 IN / 1 OUTCreate desired path. transform node, code. 2 incoming and 1 outgoing connections.STEP 04Create desired pathTRANSFORMCODE2 IN / 1 OUTCheck if top folder exists. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 05Check if top folder existsGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTIf top folder doesn't exist. decision node, if. 1 incoming and 2 outgoing connections.STEP 06If top folder doesn't existDECISIONIF1 IN / 2 OUTCreate new subfolder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 07Create new subfolderGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTSet parameters for next run. transform node, code. 2 incoming and 1 outgoing connections.STEP 08Set parameters for next runTRANSFORMCODE2 IN / 1 OUTIf path has been completely created. decision node, if. 1 incoming and 2 outgoing connections.STEP 09If path has been complete…DECISIONIF1 IN / 2 OUTReturn the ID of the last folder. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEReturn the ID of the last…TRANSFORMSET1 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.11 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’

12 Execution Links
  1. Start

    When clicking ‘Test workflow’

    Trigger

    Execute Workflow Trigger

    Trigger

  2. Step 2

    Dummy input data

    Transform

  3. Step 3

    Split the desired path

    Transform

  4. Step 4

    Create desired path

    Transform

  5. Step 5

    Check if top folder exists

    Integration

  6. Step 6

    If top folder doesn't exist

    Decision

  7. Step 7

    Create new subfolder

    Integration

  8. Step 8

    Set parameters for next run

    Transform

  9. Step 9

    If path has been completely created

    Decision

  10. Outcome

    Return the ID of the last folder

    Transform

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.