Auto Backup n8n Workflows → Google Drive

The automation starts with a Schedule Trigger node—the heartbeat of your backup system. This node determines when and how often your workflows get backed up, running silently in the background without any manual intervention.

In this configuration, we're setting the workflow to execute every 6 hours. That means you'll have 4 backups per day: at midnight, 6am, noon, and 6pm. This interval strikes the right balance between protection and storage efficiency. Frequent enough to minimize data loss, but not so frequent that your Google Drive fills up with redundant copies.

💡 Tip: For testing, you don't need to wait 6 hours. Go back to the canvas and click "Execute Workflow" to run it manually and verify everything works before activating.

Before uploading any files, we need somewhere to put them. This Google Drive node creates a new folder for each backup run, automatically named with the current timestamp. This gives you a clean, chronological archive where you can easily identify when each backup was made.

The folder name uses an n8n expression that inserts the exact date and time: Backup - 2025-12-17T21:34:35.207+01:00. No two folders will ever have the same name, and you can sort them chronologically with a glance.

💡 Tip: Create a dedicated "n8n Backups" folder in your Google Drive first, then select it as the Parent Folder. This keeps your backup archive organized and easy to find.

Now we pull the actual data to back up. This n8n node uses your instance's API to retrieve every single workflow—active or inactive, recently modified or untouched for months. Nothing gets left behind.

The node returns complete workflow objects including all nodes, connections, settings, and metadata. Each workflow becomes an item in the output, ready to be processed individually in the next steps.

💡 Tip: Make sure your n8n API credential has read access to workflows. You can create an API key in your n8n instance settings under "API" section.

With potentially dozens or hundreds of workflows returned from the previous step, we need to process them one at a time. The Loop Over Items node handles this iteration, ensuring each workflow gets converted and uploaded individually.

Setting the batch size to 1 means each workflow is processed sequentially. This prevents any race conditions with file uploads and makes the automation more reliable, especially for larger n8n instances.

💡 Tip: If you have a very large number of workflows (100+) and want faster execution, you could increase the batch size. However, keeping it at 1 ensures maximum reliability and easier troubleshooting.

Each workflow arrives as structured JSON data, but we need to package it as an actual file for uploading to Google Drive. The Convert to File node transforms the workflow data into a downloadable JSON file format.

The "All Items to One File" mode consolidates the current workflow (remember, we're processing one at a time thanks to the loop) into a single JSON file. This file contains the complete workflow definition—every node, every connection, every parameter—ready for import back into n8n.

💡 Tip: The output file is stored in a binary field called "data." The next node (Google Drive Upload) will reference this exact field name to know which file to upload.