Automated System Backup and Archiving to Google Drive - n8n Workflow

• DevOps professionals responsible for maintaining n8n instances.


• n8n users needing reliable, scheduled backups of their n8n templates.


• System administrators looking to implement routine cleanup of archived or inactive n8n workflow configurations.

Managing complex automation infrastructure requires robust backup strategies. This critical n8n workflow template provides a fully automated, scheduled solution for backing up your entire collection of n8n workflows. It addresses the common pain point of workflow sprawl by identifying and archiving specific 'ARCHIVE' n8n templates, saving them securely to Google Drive, and then deleting them from the live system to maintain optimal performance. The process starts with a reliable n8n trigger, uses the Google Drive node for cloud storage, and crucially leverages the dedicated n8n node to communicate with the local API to retrieve and manage your valuable n8n workflow definitions. This ensures data integrity and operational cleanliness.

This automation initiates on a schedule defined by the n8n trigger, typically running daily or weekly.

1. Preparation: The n8n workflow first uses the Google Drive n8n node to create a new, date-stamped folder, ensuring organized backups.


2. Fetch Workflows: The dedicated n8n node (labeled 'GET Workflows') calls the local n8n API to retrieve JSON data for every active n8n workflow and every saved n8n template on the instance.


3. Conditional Split: An If n8n node evaluates each retrieved workflow. Workflows intended for permanent removal (marked as 'ARCHIVE' in the name/tag) follow the True branch, while all other active n8n workflows follow the False branch.


4. Data Conversion: In both branches, the data is converted into storable JSON files using the Convert to File n8n node.


5. Storage: Both sets of JSON files are uploaded to the newly created folder in Google Drive using separate Google Drive n8n nodes.


6. Cleanup: Finally, after successful backup, the n8n node labeled 'Delete 'ARCHIVE' Workflows' executes a DELETE operation via the local n8n API, permanently removing the archived n8n workflow from the live instance.

1. Import: Copy the provided n8n workflow JSON and paste it into your n8n instance using the 'New' -> 'Import from JSON' function.


2. Credentials: You will need to configure two sets of credentials:

1. Configuration: Define the schedule in the 'Schedule Trigger' n8n node (e.g., daily at 2 AM).


2. Archival Logic: Review and adjust the conditions in the 'If' n8n node to correctly identify which n8n workflow definitions should be categorized as 'ARCHIVE' (e.g., matching a specific tag or name pattern).


3. Activation: Save and activate the n8n workflow to begin automated backups.

Schedule Trigger (n8n trigger): The starting n8n node. It defines when the entire backup operation for all n8n workflow assets should run.
Create to date folder (Google Drive n8n node): Creates the dedicated destination folder for the backup files, ensuring an organized file structure in Google Drive.
GET Workflows (n8n node): Essential for this specific n8n workflow. It uses the N8N API Resource to retrieve all existing n8n workflow definitions from the host instance.
If (n8n node): A core logic n8n node used to branch the flow, separating n8n workflow files that are active from those flagged for permanent archival/deletion (the 'ARCHIVE' n8n templates).
Convert to JSON/Convert to JSON' (Convert to File n8n node): Takes the raw JSON output of the workflow definitions and packages them into a proper JSON file format, ready for cloud storage.
Save 'ARCHIVE' Workflows / Save all other Workflows (Google Drive n8n node): Handles the secure transfer and storage of the backed-up n8n workflow JSON files into Google Drive.

• Delete 'ARCHIVE' Workflows (n8n node): The final step for system maintenance. This n8n node performs a DELETE request via the N8N API Resource to remove the archived n8n templates from the live n8n instance after successful backup.