Scheduled n8n workflow backups to Google Drive using n8n API
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 5 nodes and runs on a schedule (every day). Along the way it connects Google Drive.
How it runs
Trigger: On a schedule (every day).
- Get many workflows (n8n): uses n8n
- Get a workflow (n8n): get
- Move Binary Data (JSON → File) (Convert to/from binary data): uses Convert to/from binary data
- Upload file (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 (JSON → File): 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 (JSON → File) | Convert to File or Extract from File |
Nodes used (4)
- n8n
n8n-nodes-base.n8n - Google Drive
n8n-nodes-base.googleDrive - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Convert to/from binary data
n8n-nodes-base.moveBinaryData
From the author
Overview This template provides an automatic backup solution for all your n8n workflows, saving them directly to Google Drive. It’s designed for freelancers, agencies, and businesses that want to keep their automations safe, versioned, and always recoverable.…