Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Scheduled Backup AutomationIntermediate

Automated Workflow Backups to Google Drive

Automated Workflow Backups to Google Drive is a 14-node automation blueprint connecting Google Drive, Telegram, n8n API. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveTelegramn8n API

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

14

Nodes

14

Edges

6

Zones

System stack

3 integrations

  • Google Drive
  • Telegram
  • n8n API
Automated Workflow Backups to Google Drive interactive execution graphStructural view of 14 workflow nodes and 14 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.On clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTEvery Day. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.Every DayTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet DateTIme. transform node, set. 2 incoming and 1 outgoing connections.Get DateTImeTRANSFORMSET2 IN / 1 OUTExecute Once. integration node, noOp. 1 incoming and 2 outgoing connections.Execute OnceINTEGRATIONNOOP1 IN / 2 OUTComplete Message. Telegram node, telegram. 1 incoming and 0 outgoing connections.Complete MessageTELEGRAMTELEGRAM1 IN / 0 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTSearch Folder Names. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.Search Folder NamesGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTCreate Folder with DateTime Stamp. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.Create Folder with DateTi…GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTConvert Workflow to JSON File. integration node, convertToFile. 1 incoming and 1 outgoing connections.Convert Workflow to JSON …INTEGRATIONCONVERTTOFILE1 IN / 1 OUTFind Folders to Delete. transform node, code. 1 incoming and 1 outgoing connections.Find Folders to DeleteTRANSFORMCODE1 IN / 1 OUTGet Workflows. integration node, n8n. 1 incoming and 1 outgoing connections.Get WorkflowsINTEGRATIONN8N1 IN / 1 OUTSave JSON File to Google Drive Folder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.Save JSON File to Google …GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTDelete Folders. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.Delete FoldersGOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUTLimit to 200. integration node, limit. 1 incoming and 1 outgoing connections.Limit to 200INTEGRATIONLIMIT1 IN / 1 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph edd975d85fa2109fEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

2 nodes

Events, schedules, and unconnected roots that can start an execution.

On clicking 'execute'

Trigger

Every Day

Trigger

02

Data & operations

10 nodes

Transformations and external-system actions that move the work forward.

Loop Over Items

Integration

Create Folder with DateTime Stamp

Integration

Get DateTIme

Transform

Get Workflows

Integration

Limit to 200

Integration

Convert Workflow to JSON File

Integration

+ 4 more in system map
03

Intelligence & routing

0 nodes

Model calls and control points that interpret, branch, or govern the run.

No nodes observed in this zone
04

Terminal actions

2 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Delete Folders

Integration

Complete Message

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
prefix
Quality score
12 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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