💾 Backup automation for n8n workflows to Google Drive (daily or manual)
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Convert to/from binary data. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on a schedule (every day) (plus 1 other trigger). Along the way it connects Google Drive.
How it runs
Trigger: On a schedule (every day) (plus 1 other trigger).
- Date & Time: formats or calculates dates
- Folder Creation in Drive (Google Drive): uses Google Drive
- Search All Workflows (n8n): uses n8n
- Compiles Individual Data (n8n): uses n8n
- Merge: merges the data from its input branches
- Move Binary Data (Convert to/from binary data): uses Convert to/from binary data
- Save to Drive (Google Drive): uses Google Drive
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Convert to/from binary data in Move Binary Data: replace with Convert to File or Extract from File.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Convert to/from binary data Move Binary Data | Convert to File or Extract from File |
Nodes used (7)
- Convert to/from binary data
n8n-nodes-base.moveBinaryData - Date & Time
n8n-nodes-base.dateTime - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Google Drive
n8n-nodes-base.googleDrive - n8n
n8n-nodes-base.n8n - Merge
n8n-nodes-base.merge
From the author
💾 Backup Automation for n8n Workflows to Google Drive – No Risk, No Stress Hi! I’m Amanda, I build automation workflows for n8n and Make. This ready-to-use workflow is designed to automatically export and back up all your n8n workflows to a designated Google…