Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow automates the backup of all your n8n workflows to a specified Google Drive folder. It operates in two main phases: 1. Orchestration (Scheduled Task): The workflow is init...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.n8n, n8n-nodes-base.googledrive, n8n-nodes-base.splitinbatches, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.limit
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by HoChien Chang.
Original n8n.io sourceThis workflow automates the backup of all your n8n workflows to a specified Google Drive folder. It operates in two main phases:
Orchestration (Scheduled Task):
Individual Workflow Backup (Worker Task):
WorkflowName_WorkflowID.json) already exists.ifDriveEmpty) checks the result:Backup to Google Drive2).Backup to Google Drive4).After the loop in the orchestration phase completes (all workflows processed), a Limit node ensures only one signal proceeds to send a Success Email and a Discord message indicating the overall backup process was completed.
directory value to the full URL of the Google Drive folder where you want to store your backups (e.g., https://drive.google.com/drive/folders/YOUR_FOLDER_ID).workflowId in the "Execute Workflow" node to the new ID of this imported workflow. However, n8n usually handles this if it's self-referential within the same imported workflow..json files (named WorkflowName_WorkflowID.json) in the Google Drive folder you specified in the "Parameters" node.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.
Showing the first 24 of 29 workflow blocks. Download the JSON for the full node graph.
| Workflow | Automated Workflow Backup System with Google Drive, Gmail and Discord Alerts' |
|---|---|
| Complexity | advanced |
| Nodes | 29 |
| Categories | DevOps |
| Author | HoChien Chang |
| Published | 29 Apr 2025 |
Use the JSON export at /data/workflows/3787/3787.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.
How it works This workflow automates the backup of all your n8n workflows to a specified Google Drive folder. It operates in two main phases: 1. Orchestration (Scheduled Task): The workflow is init...
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.