How to Automatically Save Gmail Attachments to Google Drive with Make

If you regularly download email attachments and then upload them to Google Drive, Make can automate that job. This guide shows the basic workflow and the checks worth adding before you leave it running.

Checked: 10 September 2026 against Make's official Gmail + Google Drive integration pages and workflow templates. Features can change.

The simple version

The workflow is:

Make currently publishes an official template called Save new Gmail attachments to Google Drive. It uses Gmail, Flow Control and Google Drive. Make also has a newer Gmail → Google Drive template that uploads files when new Gmail messages arrive.

What you need

You need a Gmail account, a Google Drive account and a Make account. Make says you can connect Gmail and Google Drive inside a scenario by adding the relevant modules and authorising your Google account.

Step 1: Create a new scenario in Make

Open Make and create a new scenario. Add Gmail as the first app. The Gmail module is the trigger that starts the workflow when a matching message arrives.

Step 2: Connect Gmail

Connect the Gmail account you want Make to monitor. Make's current Gmail integration lets you work with incoming messages and attachments. Only grant access to the Google account you actually want the scenario to use.

Step 3: Watch for the emails you actually need

A good automation should not save every file from every email unless that is genuinely what you want. Start with a clear rule. For example, you might only want invoices from one sender, PDF attachments, or files from messages with a particular subject.

This makes the workflow easier to check and stops your Drive filling up with files you do not need.

Step 4: Get the attachment

Once Make detects the email, the workflow needs the attachment data so it can pass the file to the next step. Make's Gmail integration includes attachment-related functionality, and its official Gmail-to-Drive templates are designed specifically around moving incoming files into Drive.

Step 5: Add Google Drive

Add Google Drive as the next app in the scenario and choose the file-upload action. Connect the Google account and select the Drive folder where you want the attachment saved.

Make's official Gmail and Google Drive integration page describes automated attachment storage as a core use case for connecting the two apps.

Step 6: Choose a sensible folder

Do not dump everything into the root of Google Drive. Create a folder that matches the job, such as Invoices from Gmail, Receipts or Client Attachments. That makes the automation easier to review later.

Step 7: Test before turning it on

Send or use a test email with an attachment that matches your rule. Run the scenario once and check three things:

1. Make found the correct email.
2. The correct attachment was passed through.
3. The file appeared in the correct Google Drive folder.

Only turn the scenario on after those checks pass.

Useful filters to add

You can make the workflow much more useful by filtering before the upload step. Good examples include:

• Only save attachments from a particular sender.
• Only process messages with a keyword in the subject.
• Only save certain file types, such as PDF.
• Route different senders or attachment types into different Drive folders.

What happens to the original email?

Saving the attachment to Google Drive does not mean you need to delete or move the original Gmail message. Keep email organisation as a separate decision. If you later want to add labels or other Gmail actions, you can expand the scenario after the basic attachment workflow is working reliably.

Should you use Make's template or build it yourself?

If you are new to Make, the official template is the quickest place to understand the structure because the core apps are already selected. Building it yourself is useful if you want more control over filters, folder choice or naming rules.

Common mistakes to avoid

Saving everything: Use a clear filter instead of sending every attachment into Drive.

Using the wrong folder: Test with a real sample file before turning the scenario on.

Skipping duplicate checks: If the same message can be processed more than once, think about how you will recognise duplicate files.

Automating sensitive files without checking access: Make sure the destination Drive folder has the right sharing permissions.

Is this worth automating?

Yes, if downloading and filing attachments is a repetitive task you do regularly. It is a poor automation if you only receive an occasional attachment or if every file needs a different manual decision before storage.

Can you do this on Make's free plan?

Make currently offers a free account, so you can start by testing a small version of the workflow. Your usage and scheduling needs will determine whether the free plan is enough over time.

More Gmail automation ideas

If you want to go further, read my 7 useful Gmail automations with Make. You can also see my 10 Make automation ideas or my Make.com review.

Official Make references used for this guide: Make's Gmail + Google Drive integration pages and its official Gmail attachment workflow templates.