Scheduled workflow backups from n8n to Google Drive with auto cleanup
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 15 nodes and runs on a schedule (every hour). Along the way it connects Google Drive.
How it runs
Trigger: On a schedule (every hour).
- Settings (Edit Fields (Set)): sets 1 field: Coverage Period
- Date & Time: formats or calculates dates
- Date & Time: formats or calculates dates
- Date & Time: formats or calculates dates
- Google Drive: work with folder
- Date & Time: formats or calculates dates
- n8n: uses n8n
- Date & Time: formats or calculates dates
- Move Binary Data (Convert to/from binary data): uses Convert to/from binary data
- Google Drive: work with file folder
…plus 4 more steps. See the full node list below.
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 (8)
- Date & Time
n8n-nodes-base.dateTime - Google Drive
n8n-nodes-base.googleDrive - n8n
n8n-nodes-base.n8n - Convert to/from binary data
n8n-nodes-base.moveBinaryData - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Wait
n8n-nodes-base.wait - Edit Fields (Set)
n8n-nodes-base.set - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Auto Backup n8n Workflows to Google Drive Imagine the sinking feeling: hours, weeks, or even months of meticulous work building your n8n workflows, suddenly gone. A server crash, an accidental deletion, data corruption, or an unexpected platform issue – and…