Block 1 - Daily Backup Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.3
This workflow is provided as-is. Please review and test before using in production.
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 has...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.googledrive, n8n-nodes-base.datatable, n8n-nodes-base.splitout
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Chandan Singh.
Original n8n.io sourceThis 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 when a workflow has actually been modified.
To keep Google Drive clean and predictable, the workflow intentionally deletes the existing backup file before uploading the updated version. This avoids duplicate files and ensures there is always one authoritative backup per workflow.
A Data Table is used as an index to track workflow IDs, hash values, and timestamps. This allows the workflow to quickly determine whether a workflow already exists, whether its content has changed, or whether it should be skipped entirely.
Set the Cron schedule Open the Cron Trigger node and choose the time you want the backup to run (for example, once daily during off-peak hours).
Create a Data Table Create a new n8n Data Table with the title defined in dataTableTitle. This table stores workflowId, workflowName, hashCode, and DriveFiveId.
Configure the Set node
In the Set Backup Configuration node, provide the following values:
{
"n8nHost": "https://your-n8n-domain",
"apiKey": "your-n8n-api-key",
"backupFolder": "/n8n/workflow-backups",
"hashAlgorithm": "sha256",
"dataTableTitle": "n8n_workflow_backup_index",
"backupScope" : "",
"requiredTag" : ""
}
In the Set Backup Configuration node, choose how workflows should be selected for backup: all – backs up every workflow (default) active – backs up only enabled workflows tagged – backs up only workflows containing a specific tag If using the tagged option, provide the required tag name to match. { "backupScope": "tagged", "requiredTag": "production" }
Connect Google Drive credentials Authorize your Google Drive account and ensure the backup folder exists.
Activate the workflow Once enabled, backups run automatically with no further action required.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Back up self-hosted workflows to Google Drive daily with change detection |
|---|---|
| Complexity | advanced |
| Nodes | 23 |
| Categories | DevOps |
| Author | Chandan Singh |
| Published | 28 Dec 2025 |
Use the JSON export at /data/workflows/12242/12242.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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 has...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.