Back up self-hosted workflows to Google Drive daily with change detection
Ready for 3.0What this workflow does
This workflow has 18 nodes and runs on a schedule (every day at 01:00). Along the way it connects Google Drive.
How it runs
Trigger: On a schedule (every day at 01:00).
- Set Configuration (Edit Fields (Set)): sets or maps fields
- Config Validation (Code): runs custom JavaScript code
- Get All n8n Workflows (HTTP Request): calls an HTTP API
- Split Workflows (Split Out): splits a list into separate items
- Process Each Workflow (Loop Over Items (Split in Batches)): loops over the items in batches
- Backup scope all? (If): checks a condition and branches into true / false
- Prepare Workflow (Code): runs custom JavaScript code
- Backup scope active? (If): checks a condition and branches into true / false
- Generate Workflow Hash (Crypto): hashes or encrypts values
- If: checks a condition and branches into true / false
…plus 7 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Google Drive
n8n-nodes-base.googleDrive - Data table
n8n-nodes-base.dataTable - Split Out
n8n-nodes-base.splitOut - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Crypto
n8n-nodes-base.crypto
From the author
This workflow creates a daily, automated backup of all workflows in a self-hosted n8n instance and stores them in Google Drive. Instead of exporting every workflow on every run, it uses content hashing to detect meaningful changes and only updates backups…