My Google Drive used to be a single folder holding everything: client invoices, screenshots, half-finished drafts, random downloads, all mixed together with no order. I would lose ten minutes a week just hunting for one file. Building a Make.com scenario to sort things automatically fixed that, and it turned out to be a simpler build than I expected, mostly recycled modules I already understood from other automations.
How Do You Automate File Organization in Google Drive with Make.com?
The core pattern has four parts: a watch trigger that notices new files, a router that decides where each file belongs, a rename step for consistent naming, and a move or copy action that puts the file in its final home. You build this once as a scenario, connect it to a folder you upload into, and every file that lands there gets sorted the same way from then on.
None of the individual pieces are complicated. What makes it feel powerful is chaining them together so a task that used to take you minutes of manual dragging and renaming happens the instant a file appears.
How Does the Watch Trigger Work?
Make.com's Google Drive watch module keeps an eye on a folder you specify and fires whenever a new file shows up there. I point mine at a single inbox-style folder, something like an "Unsorted" folder, rather than my whole Drive. That keeps the automation focused on files I intentionally dropped in for processing, instead of accidentally reacting to every file across every folder I own.
Like other scheduled checks, this watch runs on an interval you set, so it is worth reading our guide to scheduling Make.com scenarios if you want to fine-tune how often it checks versus how many operations that check uses on your plan.
How Do You Route Files by Type or Name?
Once a new file is detected, a router module splits the scenario into separate paths, one for each category you care about. A common setup routes based on file extension or MIME type: images to one folder, PDFs to another, spreadsheets to a third, everything else to a catch-all. Each route carries a filter checking that condition, so only matching files travel down that path.
You can also route by name pattern instead of type, which is useful if your files follow a naming convention already, like invoices always starting with "INV" or screenshots always starting with "Screen." Our guide to filters and routers covers the logic behind this branching in more detail if routing is new to you.
How Do You Rename Files Consistently?
Before or during the move step, add a rename action that builds a new file name from pieces you control, like the date the file arrived, a category label from your router, and the file's original name. A simple pattern like combining the date with the original name keeps files sortable and searchable without you thinking about it on upload.
Consistency here matters more than cleverness. I kept my rename pattern boring on purpose, a fixed order of date, category, then original name, because a boring, predictable name is what makes files easy to find later, whether you are searching manually or building another automation on top of this one.
What Is the Monthly Folder Pattern, and Why Use It?
Instead of dumping every sorted file into one folder that grows forever, the monthly folder pattern creates a new folder for each month, like one named for the current year and month, and routes files into that month's folder. Six months in, you have six tidy folders instead of one folder with hundreds of files in it.
To build this, the scenario checks whether that month's folder already exists before moving a file, using a search step against the parent folder. If it exists, the file goes straight in. If not, the scenario creates the folder first, then moves the file. This check-then-create logic is a small extra step, but it is what keeps the automation from erroring out on the first day of a new month when that month's folder does not exist yet.
What Happens to the Original Unsorted File?
You get to choose between moving and copying. A move takes the file out of your inbox folder entirely and puts it in its sorted home, which keeps the inbox clean and is what I use for most of my scenarios. A copy leaves the original in place and creates a duplicate in the sorted folder, which some people prefer as a safety net while they are still trusting the automation. I ran mine in copy mode for the first couple of weeks, checked that everything landed where it should, then switched to move once I trusted it.
Can This Extend Beyond Just Sorting?
Once files are landing in the right monthly folders automatically, it is a short step to layer on more. You could add a data store, like the one covered in our guide to Make.com data stores, to keep a running log of every file processed, or trigger a notification whenever a new invoice specifically arrives, so you never miss one buried in a folder you rarely open. Once the sorting foundation exists, adding these extra behaviors is mostly just new branches off the same router.
What Should You Test Before Trusting This Automation?
Upload a handful of test files covering every category your router handles, including a file type you did not plan for, and watch where each one lands. The catch-all route matters here: files that do not match any specific rule should still end up somewhere sensible rather than silently vanishing or erroring the scenario. I found my first version had no catch-all, and a stray file type just broke the run until I added one.
What If Two Files Land With the Same Name?
This trips people up more often than you would expect, especially with screenshots, which frequently arrive with generic default names. If your rename pattern includes only the date and category, two screenshots taken the same day can collide, and depending on how your move step is configured, one might overwrite the other or Google Drive might quietly create a second file with the same visible name.
The fix is building enough uniqueness into your rename pattern from the start, such as including the time down to the minute or second alongside the date, not just the date alone. It costs nothing to add that extra piece of specificity up front, and it saves you from ever discovering, weeks later, that a file you thought you still had was silently overwritten by another one that happened to share its name.
Next step: Once your Drive sorts itself, you can apply the same watch-route-rename pattern to other storage tools and workflows. Explore more ideas on the automation hub.
