Get Started
Screenshot of n8n workflow
FREE TEMPLATE
Automate n8n Google Drive Backups
13
Views
0
Downloads
33
Nodes
Download Template
Free
Preview Template
Utility Rating
7 / 10
Business Function
IT
Automation Orchestrator
n8n
Integrations
n8n API
Google Drive
Trigger Type
Approx setup time ≈ 35 min
Need help setting up this template?
Ask in our free Futurise community
About
Community
Courses
Events
Members
Templates

How to Automate n8n Google Drive Backups?

Leon Petrou
FREE TEMPLATE
Automate n8n Google Drive Backups
13
Views
0
Downloads
33
Nodes
Download Template
Free
Preview Template
Utility Rating
7 / 10
Business Function
IT
Automation Orchestrator
n8n
Integrations
n8n API
Google Drive
Trigger Type
Approximate setup time ≈ 35 minutes
Need help setting up this template?
Ask in our free Futurise community

Description

Keep your automation safe without extra work. This setup copies all n8n workflows to Google Drive on a set schedule, moves yesterday’s files into an archive folder, and can remove old backups after a set number of days. It suits teams that want simple version safety and easy file access in Drive.

Here is how it runs. A scheduled trigger starts the job. The flow checks Google Drive for two folders and creates them if they do not exist. The n8n API pulls your workflows, then a file builder turns each workflow into a file and adds the active or inactive status to the file name. Files upload to the backups folder in batches. Before new uploads, current files are moved into the archive folder. A second schedule can list archive files and delete any that are older than your purge rule. A filter step avoids touching other Drive folders.

You will need a Google Drive account and an n8n API key. Connect both inside n8n credentials, set your run time, and pick the purge window if you want cleanup. Expect to cut manual exports and file moves to almost zero, while keeping a clean history. This is helpful for IT teams, agencies, or any group managing multiple n8n workflows.

Copy link

Tools Required

What this workflow does?

  • Two schedule triggers control nightly backups and timed cleanup.
  • Google Drive folder check and auto creation for backups and archive.
  • n8n API fetches all workflows with an adjustable limit.
  • Move Binary Data builds files and tags names with active or inactive status.
  • Batch upload sends files to Google Drive until all items are done.
  • Safe rotation moves current files into the archive folder before new uploads.
  • Purge rule lists archive files and deletes ones older than your set age.
  • Filter step ignores unrelated Drive folders to avoid unwanted changes.

What are the benefits?

  • Reduce manual export work from 60 minutes to 5 minutes per day
  • Automate 100 percent of backup rotation and cleanup
  • Improve backup accuracy by pulling directly from the n8n API
  • Handle large sets of workflows using batch uploads
  • Connect n8n and Google Drive in one reliable routine

How to set this up?

  1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
  2. You'll need accounts with Google Drive and n8n. See the Tools Required section above for links to create accounts with these services.
  3. In the n8n credentials manager, create a Google Drive OAuth2 credential. Or double click any Google Drive node, choose 'Credential to connect with', click 'Create new credential', then follow the on screen steps to connect your Google account.
  4. Open the n8n API node. In the 'Credential to connect with' dropdown, click 'Create new credential'. Enter your n8n API key and base URL. Name the credential clearly, for example n8n API Production.
  5. Open the Schedule Trigger that starts the backup. Set the time you want the backup to run, such as every night.
  6. Open the second Schedule Trigger for cleanup. Enable it only if you want auto delete. Set how often it should run, such as daily or weekly.
  7. Check the Google Drive nodes for the backup and archive folder names. Keep them consistent across all nodes so files are found and moved correctly.
  8. If you have many workflows, adjust the limit in the n8n API node. The batch nodes will loop until all files are uploaded.
  9. Run the workflow once manually to test. Confirm that the backup and archive folders are created in Google Drive and that new files appear in the backups folder.
  10. Verify rotation by running a second time. The previous backup files should move into the archive folder before new files upload.
  11. If you enabled cleanup, confirm that archive files older than your set age are removed after the cleanup schedule runs.
  12. Troubleshoot common issues: if you see a permission error, reconnect the Google Drive credential. If folders are not found, check exact names. If no files upload, verify the n8n API key and base URL.

Need help or want to customize this?

Ask in the Free Futurise Community.

Similar Templates

n8n
IT
Generate n8n Workflow Analytics
Get a live view of your n8n instance without manual checks. The workflow builds a full inventory of workflows, nodes, tags, and webhook URLs, then serves it as JSON and as a simple HTML dashboard. It fits teams that maintain many automations and need quick insight. Data is pulled from your n8n API and shaped into clear sections. Code nodes and JMESPath create lists and counts for each workflow, node type, and tag. Sort and Aggregate nodes rank the most used nodes and group related items. A webhook endpoint delivers an HTML page that reads XML data through an XSLT template. Another webhook returns the stylesheet so the page loads in the browser. A final JSON object can feed BI tools for deeper charts and reports. Setup needs an n8n API credential and your base URL. Cloud users may replace environment variables with direct URLs in the noted nodes. Expect faster audits, fewer errors in reporting, and clear visibility of active and idle flows. Teams use it to track growth, spot risky public webhooks, and plan refactoring work.
10 views
view
n8n
IT
Restore GitHub Backups to n8n Credentials
Recover your n8n credentials from a GitHub backup in a few clicks. Ideal for teams that need to rebuild an instance, migrate to a new server, or load a fresh workspace after a reset. You get a simple way to bring back many credentials without copy and paste. Here is how it works. You start the run manually. A Globals step stores the GitHub owner, repo, and folder path. The workflow calls the GitHub API to list every file in that folder, then splits the list and pulls each file content. It reads each JSON file, skips empty or blocked items with a check step, and sends valid data to the n8n API to create credentials with the right name and type. This gives you a clean restore, even when there are many files. Set your GitHub and n8n credentials first. Update the Globals values with your repo details. Test the list call to confirm the folder and files are correct, then run the full restore. Expect hours of manual setup to drop to minutes, fewer errors, and an easier way to move between environments. Use it for recovery after an incident, seeding new spaces, or setting up test data for a dev team.
13 views
view
n8n
IT
Audit n8n Credential Usage
Quickly see which n8n workflows use which app credentials. Ask questions in plain English and get instant answers, like which projects use Slack and Google Sheets. Built for IT and operations teams that need fast visibility and safer change control. The build has two parts. First, a manual run calls the n8n API to list all workflows, maps each workflow’s name and credential list, and writes that data into a small SQLite table. Second, a chat entry point lets you type a question. An AI model turns your words into a SQL query, runs it against the local database, and replies with the result. A short memory keeps the conversation context so you can refine your search. You will need an n8n API key and an OpenAI API key. Run the data load step to rebuild the database, then use the chat interface to search. Expect faster audits, quicker impact checks during credential rotation, and fewer missed dependencies. If your n8n instance restarts, rebuild the database by running the first step again. Teams with many automations will save hours each month by avoiding manual checks.
8 views
view
See More Templates

Credits: nuntius.creative.hub@gmail.com - these templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution. If you are the author and would like this template removed from the template library, email us at info@futurise.com and we will remove it promptly.