Gmail Attachments to Drive: Make

This is the first stop in the no-code foundations corner of our AI Automation for Beginners (the hub): the plumbing that every AI automation later sits on top of. No model, no code, just two apps talking to each other.

The job is simple and oddly satisfying: a file lands in your email, and seconds later it is filed neatly in Google Drive without you lifting a finger. Once you have built this, the pattern behind it (something happens, so do this) is one you will reuse in every automation you ever make.

What does this automation actually do?

It watches one Gmail inbox. When a new email arrives with an attachment, it grabs the file and uploads it to a Google Drive folder you choose. That is the whole loop, running every fifteen minutes in the background.

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

• A bookkeeper auto-files every supplier invoice into a “To process” Drive folder.
• A photographer saves every client-sent image into a per-month folder.
• A small charity collects signed PDF forms from email into one shared folder the whole team can see.

None of these need AI. They need a reliable pair of hands that never forgets, which is exactly what this is.

Why automate this without any AI at all?

Because the task is not a thinking task, it is a moving task. AI is for judgment (is this urgent, what does this say, write a reply). Filing a known file into a known folder needs no judgment, so adding AI would only add cost and a thing to go wrong.

Learning the no-AI version first is the point. Once you can move a file from one app into another reliably, adding a smart step in the middle later is a small change, not a new skill. Build the pipe first, then decide where intelligence belongs.

What do you need before you start?

• A free Make account.
• A Gmail (or Google Workspace) account.
• A Google Drive folder to file things into, with its name in mind.

Two words you will meet. A trigger is the module that watches and starts the run (here, “watch emails”). An action is the module that does something as a result (here, “upload a file”). Almost every automation is one trigger and one or more actions.

How does the workflow work, step by step?

Two modules, left to right. Gmail watches for new mail; Google Drive uploads any attachment it finds. Here is the finished scenario:

Module	App	What it does
Watch emails	Gmail	Fires when a new email arrives in the folder you pick
Upload a File	Google Drive	Saves each attachment into your chosen Drive folder

Step 1: Add the Gmail trigger

In a new Make scenario, click the big plus and choose Gmail, then Watch emails. Connect your Google account when asked.

Set the folder to INBOX, the criteria to Only unread emails with attachments, and “Mark as read” to No so you do not change your inbox. Set “Maximum number of results” to 2 while testing.

Step 2: Add the Google Drive action

Click the plus to the right and choose Google Drive, then Upload a File. Connect your Drive account.

In the File field, map the attachment from the Gmail step (Make shows it as Attachments[]). Choose the destination folder. Because one email can hold several files, Make adds an Iterator automatically when you map an array, so each attachment is saved separately.

Step 3: Only save real attachments

Inline images and signatures count as attachments too. To skip them, click the link between the two modules and add a filter so it only runs when the file size is over, say, 20 KB:

Condition:  Size  (Greater than)  20000

That one filter is the difference between a tidy folder and a folder full of one-pixel logos.

How do you run it and check the result?

Click Run once, then send yourself a test email with a PDF attached. Within a moment the file should appear in your Drive folder.

Open the folder to confirm. If it is there, switch the scenario on with the toggle and set the schedule to every 15 minutes. From now on it runs without you.

What does this cost to run?

Piece	Free tier	If you outgrow it
Make	1,000 operations a month free, plenty for this	$9/mo Core if you run thousands of files
Gmail + Google Drive	Free with any Google account	Google One storage if your Drive fills up
AI	Not used here	Pennies per file only if you add a smart step later

For most people this runs free forever. Each saved file is one or two operations.

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

• Saving junk images. Use the size filter in Step 3 so signatures and logos do not flood the folder.
• Duplicate saves. Leave “Mark as read” off but set the trigger to unread-only, or Make may re-save the same email. Test with two results first.
• Wrong folder. Drive can have several folders with the same name. Pick it from the dropdown, do not type it.

Build it watching one label first. Widen to the whole inbox only once you trust it.

Where does AI plug in later?

Right after the file is saved. Add one step that reads each saved PDF and writes a one-line summary, and you have turned a filing robot into a reading assistant. That is exactly the build in our guide to summarize documents with Claude.

The lesson holds for the whole AI Automation for Beginners (the hub): get the file moving with no-AI plumbing first, then drop Claude in at the single point where judgment actually helps. The pipe you built today does not change.

How do you build this in Zapier or n8n instead?

This is a two-app move, so every major tool can do it. Here is the same job in each:

Job	Make	Zapier	n8n
Watch for new email	Gmail module	Gmail trigger	Gmail / IMAP node
Save the file	Google Drive: Upload a File	Google Drive action	Google Drive node
Skip tiny files	Filter on size	Filter step	IF 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

Do I need to know how to code?

No. This is two boxes on a canvas and one small filter. There is no code anywhere in it.

Will it save emails I already have?

No. The trigger only fires on new mail from the moment you switch it on. Old email is left alone.

Can I sort files into different folders?

Yes. Add a Router after the trigger and send, say, PDFs to one folder and images to another. That is the next skill up.

Is Google Drive the only option?

No. Swap the second module for Dropbox, OneDrive, or Box. The Gmail trigger stays the same.

Does this cost anything?

For normal personal volumes, no. Make’s free plan and your Google account cover it.

Sources and official documentation

• Make: Gmail app docs
• Make: Google Drive app docs
• Google Drive Help: upload files and folders

Last reviewed: May 2026. Make’s apps update often; check the official docs above if a field has moved.

You may also like

• AI Automation for Beginners (the hub)
• Make.com Complete Beginner’s Guide
• Zapier vs Make vs n8n: which to learn first
• summarize documents with Claude
• Make AI Scenarios: automations that save hours
• AI Tools Directory