Auto-Backup a Drive Folder

Fourth stop in the no-code foundations of our AI Automation for Beginners (the hub). A watched Google Drive folder copies its new files into a backup folder automatically, so a wrong delete is never the end of the world.

Two new skills live here: scheduling (deciding how often an automation runs) and the Router (sending files down different paths by type). Both show up in nearly every serious build.

What does this automation do?

It watches a Drive folder. When a new file appears, it copies that file into a separate backup folder. The original stays put; the copy is your insurance. Optionally a Router sends images and documents into different backup folders.

A few real cases, none of them the usual ones:

• A design team backs up a shared “Working” folder into a dated “Archive” folder nightly.
• A consultant copies every client deliverable into a separate read-only backup.
• A teacher keeps a safety copy of a shared class folder that students can edit.

It is not glamorous, but the first time a file is deleted by accident, this automation pays for the twenty minutes a hundred times over.

Why schedule a backup instead of doing it by hand?

Because manual backups happen right up until the week you forget, which is always the week you needed them. A scheduled automation does not get busy, distracted, or sick.

Scheduling is also a core idea worth learning on something low-stakes. Once you can say “run this every night at 1am”, you can apply the same control to reports, digests, and reminders. A backup is a safe place to practise.

What do you need before you start?

• A free Make account.
• A Google Drive folder you want protected (the source).
• A second, separate Drive folder to hold the backups (the destination).

Two terms. Scheduling is how often the scenario runs, as often as every minute, or once a day at a set time. A Router is a module that splits the flow into branches, each with its own filter, so different files can go different ways.

How does the workflow work, step by step?

At its simplest it is two modules: watch the folder, copy the file. Here is the core scenario; we add a Router in Step 3:

Module	App	What it does
Watch Files in a Folder	Google Drive	Fires when a new file lands in the source folder
Copy a File	Google Drive	Copies that file into your backup folder

Step 1: Watch the source folder

New scenario, add Google Drive, choose Watch Files in a Folder, and pick the folder you want protected. Set “Maximum number of results” to 3 for testing.

Run once so Make sees a sample file and knows the fields (name, ID, type) it can use later.

Step 2: Copy each new file to backup

Add another Google Drive module, choose Copy a File, and map the File ID from the watch step. Set the destination to your backup folder.

Give the copy a clear name by mapping the original name with a date in front, so backups never clash:

{{formatDate(now; "YYYY-MM-DD")}} - {{1.name}}

Step 3: Split by file type with a Router (optional)

Want images in one backup folder and documents in another? Delete the direct link, add a Router after the watch module, and give each branch a Copy a File module with its own filter, for example:

Branch A filter:  {{1.mimeType}}  (contains)  image
Branch B filter:  {{1.mimeType}}  (contains)  document

This is the Router in one picture: one trigger, several filtered paths. It is the building block behind every “if this, do that, otherwise do the other” automation.

How do you run it and check the result?

Click Run once, then drop a new file into the source folder. A renamed copy should appear in the backup folder moments later.

Check the copy opens and is intact. Then switch the scenario on and set the schedule to once a day (or every few hours for busy folders). Your safety net is now automatic.

What does this cost to run?

Piece	Free tier	If you outgrow it
Make	1,000 operations a month free	$9/mo Core if you back up large folders often
Google Drive	Free with your account	Google One storage if backups grow large
AI	Not used here	Add an AI step to caption or sort files later for pennies

Each copied file is a couple of operations. A daily backup of a normal folder stays comfortably free.

What can go wrong, and how do you avoid it?

• Backing up into the same folder. The source and destination must be different folders, or you create copies of copies forever.
• Name clashes. Use the date-prefix from Step 2 so two files with the same name do not overwrite each other.
• Running too often. A folder that rarely changes does not need a per-minute schedule. Match the schedule to how often files actually arrive.

Test with a throwaway folder and a few files first. Point it at the real folder only when the copies look right.

Where does AI plug in later?

On the backup branch. Add a step that reads each backed-up image and writes a caption or alt text, or one that reads each document and files it by topic. The first is our guide to write image alt text with AI.

As across the AI Automation for Beginners (the hub), the backup itself needs no intelligence. AI is an optional branch you add once the plumbing is solid, never a replacement for it.

How do you build this in Zapier or n8n instead?

Scheduled file copying is universal. Each tool has its own version:

Job	Make	Zapier	n8n
Watch a folder	Google Drive: Watch Files	Google Drive trigger	Google Drive Trigger node
Branch by type	Router with filters	Paths	Switch node
Copy the file	Google Drive: Copy a File	Google Drive action	Google Drive node

All three can do it. We teach Make because the visual canvas is the easiest place to learn. The same shape works in any of them, and Zapier vs Make vs n8n compares the three for beginners.

Common questions

Is a copy really a backup?

It is a simple one. For a true off-site backup, send the copy to a different cloud (Dropbox, OneDrive) by swapping the second module.

Will it copy files that were already there?

On the first run it may copy the most recent few. After that, only new arrivals.

Do I have to use the Router?

No. The two-module version is a complete backup. The Router is there when you want to split by file type.

Can I back up to Dropbox instead?

Yes. Replace the Copy a File module with a Dropbox Upload module; the watch step is unchanged.

Does this need any code?

No. The only typed parts are the date formula and the filter words, both copy-paste from above.

Sources and official documentation

• Make: Google Drive app docs
• Make: routers and multiple routes
• Google Drive Help: organize your files

Last reviewed: May 2026. Make’s Router and Drive modules update occasionally; the docs above are current.

You may also like

• AI Automation for Beginners (the hub)
• Foundation before this: RSS to Slack with a filter
• write image alt text with AI
• Make.com Complete Beginner’s Guide
• Zapier vs Make vs n8n
• AI Tools Directory