Block 1 - Sticky Note1
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Who’s it for This workflow is designed for n8n users who want an automated way to back up their workflows to Google Drive. It is useful for freelancers, developers, automation agencies, and teams m...
n8n-nodes-base.stickynote, n8n-nodes-base.splitinbatches, n8n-nodes-base.converttofile, n8n-nodes-base.scheduletrigger, n8n-nodes-base.filter, n8n-nodes-base.googledrive, n8n-nodes-base.n8n, n8n-nodes-base.manualtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Safa Khan.
Original n8n.io sourceThis workflow is designed for n8n users who want an automated way to back up their workflows to Google Drive. It is useful for freelancers, developers, automation agencies, and teams managing multiple workflows who need regular backups for recovery, migration, or version tracking.
The workflow automatically exports all workflows from your n8n instance and stores them as JSON files in a dedicated Google Drive folder. It can be triggered manually or scheduled to run every four hours.
First, the workflow creates a new backup folder in Google Drive with the current date and time in the folder name. It then retrieves all workflows from the connected n8n instance and processes them one by one using a loop. Each workflow is converted into a formatted JSON file and uploaded to the newly created backup folder.
The workflow also checks older backup folders and removes unnecessary folders to help keep storage organized and avoid duplicate backups.
An active n8n instance Google Drive OAuth2 credentials n8n API credentials Permission to create and delete folders in Google Drive
Change the backup schedule in the Schedule Trigger node. Modify the backup folder naming format if needed. Store backups in a different Google Drive location. Adjust the folder cleanup logic to keep more historical backups. Add notifications through email or Slack after successful backups.
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 workflow JSON files to Google Drive using the n8n API |
|---|---|
| Complexity | advanced |
| Nodes | 15 |
| Categories | DevOps |
| Author | Safa Khan |
| Published | 14 May 2026 |
Use the JSON export at /data/workflows/15724/15724.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.
Who’s it for This workflow is designed for n8n users who want an automated way to back up their workflows to Google Drive. It is useful for freelancers, developers, automation agencies, and teams m...
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.