Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Google Drive Duplicates Manager

Google Drive Duplicates Manager is a 14-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.

14

Nodes

14

Links

1

Run groups

Connected tools

1 integrations

  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive Duplicates Manager execution lanes1 run groups containing 14 workflow nodes and 14 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.Google Drive Trigger. Google Drive node, googleDriveTrigger. 0 incoming and 1 outgoing connections.STARTGoogle Drive TriggerGOOGLE DRIVEGOOGLEDRIVETRIGGER0 IN / 1 OUTConfig. transform node, set. 1 incoming and 1 outgoing connections.STEP 02ConfigTRANSFORMSET1 IN / 1 OUTWorking Folder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Working FolderGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTDrop Google Apps files. decision node, filter. 1 incoming and 1 outgoing connections.STEP 04Drop Google Apps filesDECISIONFILTER1 IN / 1 OUTKeep First/Last. decision node, switch. 1 incoming and 2 outgoing connections.STEP 05Keep First/LastDECISIONSWITCH1 IN / 2 OUTDeduplicate Keep Last. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Deduplicate Keep LastTRANSFORMCODE1 IN / 1 OUTDeduplicate Keep First. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Deduplicate Keep FirstTRANSFORMCODE1 IN / 1 OUTEdit Fields. transform node, set. 2 incoming and 1 outgoing connections.STEP 07Edit FieldsTRANSFORMSET2 IN / 1 OUTFilter. decision node, filter. 1 incoming and 1 outgoing connections.STEP 08FilterDECISIONFILTER1 IN / 1 OUTTrash/Flag Duplicates. decision node, switch. 1 incoming and 2 outgoing connections.STEP 09Trash/Flag DuplicatesDECISIONSWITCH1 IN / 2 OUTSend Duplicates to Trash. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.STEP 10Send Duplicates to TrashGOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUTIs Flagged. decision node, if. 1 incoming and 2 outgoing connections.STEP 10Is FlaggedDECISIONIF1 IN / 2 OUTNo Operation, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMENo Operation, do nothingINTEGRATIONNOOP1 IN / 0 OUTGoogle Drive. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMEGoogle DriveGOOGLE DRIVEGOOGLEDRIVE1 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.14 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

Google Drive Trigger

14 Execution Links
  1. Start

    Google Drive Trigger

    Trigger

  2. Step 2

    Config

    Transform

  3. Step 3

    Working Folder

    Integration

  4. Step 4

    Drop Google Apps files

    Decision

  5. Step 5

    Keep First/Last

    Decision

  6. Step 6

    Deduplicate Keep Last

    Transform

    Deduplicate Keep First

    Transform

  7. Step 7

    Edit Fields

    Transform

  8. Step 8

    Filter

    Decision

  9. Step 9

    Trash/Flag Duplicates

    Decision

  10. Step 10

    Send Duplicates to Trash

    Integration

    Is Flagged

    Decision

  11. Outcome

    No Operation, do nothing

    Integration

    Google Drive

    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.