Backup n8n workflows to Google Drive
Needs changesWhat this workflow does
This workflow has 9 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Drive.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Get Workflow List (HTTP Request): calls an HTTP API
- Map (Function): runs custom JavaScript (legacy Function node)
- Get Workflow (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- Function Item: runs custom JavaScript per item (legacy Function Item node)
- Move Binary Data (Convert to/from binary data): uses Convert to/from binary data
- Google Drive: uses Google Drive
Services it uses
Before you upgrade to n8n 3.0
4 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Convert to/from binary data in Move Binary Data: replace with Convert to File or Extract from File.
- Function (legacy) in Map: replace with Code node, mode 'Run Once for All Items'.
- Function Item (legacy) in FunctionItem: replace with Code node, mode 'Run Once for Each Item'.
- Cron in Run Daily at 2:30am: replace with Schedule Trigger.
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 |
| Function (legacy) Map | Code node, mode 'Run Once for All Items' |
| Function Item (legacy) FunctionItem | Code node, mode 'Run Once for Each Item' |
| Cron Run Daily at 2:30am | Schedule Trigger |
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Merge
n8n-nodes-base.merge - Convert to/from binary data
n8n-nodes-base.moveBinaryData - Function
n8n-nodes-base.function - HTTP Request
n8n-nodes-base.httpRequest - Function Item
n8n-nodes-base.functionItem - Google Drive
n8n-nodes-base.googleDrive - Cron
n8n-nodes-base.cron
From the author
Temporary solution using the undocumented REST API for backups using Google drive. Please note that there are issues with this workflow. It does not support versioning, so please know that it will create multiple copies of the workflows so if you run this…