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

Google Drive Backup & Management Workflow

Google Drive Backup & Management Workflow is a 23-node automation blueprint connecting Google Drive, n8n. Inspect its trigger, execution graph, branches, and implementation requirements.

Google Driven8n

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.

23

Nodes

26

Links

3

Run groups

Connected tools

2 integrations

  • Google Drive
  • n8n

Canvas controls

Fit wide systems, then zoom into any run group.

Google Drive Backup & Management Workflow execution lanes3 run groups containing 23 workflow nodes and 26 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGET CURRENT FOLDER. Google Drive node, googleDrive. 3 incoming and 1 outgoing connections.STEP 02GET CURRENT FOLDERGOOGLE DRIVEGOOGLEDRIVE3 IN / 1 OUTCode. transform node, code. 1 incoming and 2 outgoing connections.STEP 03CodeTRANSFORMCODE1 IN / 2 OUTIf1 n8n_backups. decision node, if. 1 incoming and 2 outgoing connections.STEP 04If1 n8n_backupsDECISIONIF1 IN / 2 OUTIf n8n_old. decision node, if. 1 incoming and 2 outgoing connections.STEP 05If n8n_oldDECISIONIF1 IN / 2 OUTMerge mensage. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06Merge mensageDECISIONMERGE2 IN / 1 OUTCreate n8n_backups. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 07Create n8n_backupsGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTCreate n8n_old. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 08Create n8n_oldGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTGET CURRENT FOLDER CREATES. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 09GET CURRENT FOLDER CREATESGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTIGNORE FILES. decision node, filter. 1 incoming and 2 outgoing connections.STEP 10IGNORE FILESDECISIONFILTER1 IN / 2 OUTGET CURRENT BACKUPS1. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 11GET CURRENT BACKUPS1GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTn8n. integration node, n8n. 1 incoming and 1 outgoing connections.STEP 12n8nINTEGRATIONN8N1 IN / 1 OUTItem Lists. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 13Item ListsTRANSFORMITEMLISTS1 IN / 1 OUTMove Binary Data. integration node, moveBinaryData. 1 incoming and 1 outgoing connections.STEP 14Move Binary DataINTEGRATIONMOVEBINARYDATA1 IN / 1 OUTSplit In Batches2. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 15Split In Batches2INTEGRATIONSPLITINBATCHES2 IN / 1 OUTSplit In Batches. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 16Split In BatchesINTEGRATIONSPLITINBATCHES2 IN / 1 OUTMOVE INTO OLD FOLDER. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 17MOVE INTO OLD FOLDERGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTUPLOAD WORKFLOWS. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.OUTCOMEUPLOAD WORKFLOWSGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTLIST OLD BACKUPS. Google Drive node, googleDrive. 0 incoming and 1 outgoing connections.STARTLIST OLD BACKUPSGOOGLE DRIVEGOOGLEDRIVE0 IN / 1 OUTItem Lists old. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 02Item Lists oldTRANSFORMITEMLISTS1 IN / 1 OUTSplit In Batches old. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03Split In Batches oldINTEGRATIONSPLITINBATCHES2 IN / 1 OUTDELETE OLD BACKUP. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.OUTCOMEDELETE OLD BACKUPGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTSchedule Trigger1. trigger node, scheduleTrigger. 0 incoming and 0 outgoing connections.CORE RUNTIMESchedule Trigger1TRIGGERSCHEDULETRIGGER0 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.23 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

Schedule Trigger

22 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    GET CURRENT FOLDER

    Integration

  3. Step 3

    Code

    Transform

  4. Step 4

    If1 n8n_backups

    Decision

  5. Step 5

    If n8n_old

    Decision

  6. Step 6

    Merge mensage

    Decision

  7. Step 7

    Create n8n_backups

    Integration

  8. Step 8

    Create n8n_old

    Integration

  9. Step 9

    GET CURRENT FOLDER CREATES

    Integration

  10. Step 10

    IGNORE FILES

    Decision

  11. Step 11

    GET CURRENT BACKUPS1

    Integration

  12. Step 12

    n8n

    Integration

  13. Step 13

    Item Lists

    Transform

  14. Step 14

    Move Binary Data

    Integration

  15. Step 15

    Split In Batches2

    Integration

  16. Step 16

    Split In Batches

    Integration

  17. Step 17

    MOVE INTO OLD FOLDER

    Integration

  18. Outcome

    UPLOAD WORKFLOWS

    Integration

02

Run Group

LIST OLD BACKUPS

4 Execution Links

  1. Start

    LIST OLD BACKUPS

    Integration

  2. Step 2

    Item Lists old

    Transform

  3. Step 3

    Split In Batches old

    Integration

  4. Outcome

    DELETE OLD BACKUP

    Integration

03

Run Group

Schedule Trigger1

0 Execution Links

  1. Core Runtime

    Schedule Trigger1

    Trigger

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