How to Automatically Save and File Gmail Attachments

TL;DR: Gmail filters and Zapier act on the sender, the subject line, and the filename. They cannot tell a $480 invoice from a $7,480 one, or a signed contract from a draft. A Gmail attachment workflow in The Drive AI reads the attachment itself, decides where it belongs, renames it, files it into The Drive AI or a connected drive, and can hold anything over a limit for a person to approve. Your inbox is never touched.

Every team has a mailbox that quietly becomes a filing system. Invoices arrive at ap@, signed agreements arrive at legal@, and a client sends the same onboarding form three times to three different people. Somebody downloads each attachment, works out what it is, names it, and drags it into a folder. On a good week that happens on Friday. On a bad week it happens never, and the file lives in search results forever.

Gmail gives you filters, and filters are useful. They apply labels, skip the inbox, and forward. What they cannot do is open the attachment. A filter for "invoice" in the subject matches the invoice, the invoice reminder, and the email from your accountant asking about the invoice.

A Gmail attachment workflow is a standing instruction that runs when an attachment arrives: read the file, decide from what is inside it, and file it, rename it, or hold it for a person, with every move recorded.

What Gmail attachment automation can and cannot do natively

Gmail's own tools decide from the envelope, not the letter. Filters match sender, recipient, subject, size, and words in the message body. Labels can be applied automatically, and messages can be forwarded or archived. None of that reads the PDF.

The usual next step is a connector. Zapier and Make both offer a "new attachment in Gmail" trigger that saves the file to Google Drive, Dropbox, or OneDrive. That gets the file out of the inbox, which is real progress. But the destination folder is fixed when you build the zap, or built from fields Gmail already knows: sender, subject, date. The result is a folder called "Gmail attachments" with 1,400 files in it, or twelve zaps for twelve senders that break every time a vendor changes their billing address.

The gap is the same in every case. The information that decides where a file belongs is inside the file. Which vendor. Which client. What total. Whether both parties signed. Whether the form is complete. Anything that decides from the outside of the attachment is guessing.

How a Gmail attachment workflow works

A workflow in The Drive AI starts from a sentence. You type what should happen, and the steps appear on a canvas where you can adjust them. For Gmail, the trigger is Email Attachment: an attachment received from a connected Gmail account.

From there, the steps are the app's own:

• Check File Details sends files down different paths by type, size, name, or age. This step is free, because it decides from details already known.
• Ask AI About the File opens the attachment and answers a question about it: is the total over $5,000, is this a contract or a proposal, does it carry both signatures. It reads the whole file, not the filename. This step costs a little per file, and the badge on the step says it can occasionally be wrong.
• Read Details from File pulls named values out, such as vendor, client, invoice number, total, or a renewal date. Later steps can use those values in folder paths and filenames.
• Save a Copy gives the attachment a home. An email attachment has no storage location yet, so this step puts a copy in The Drive AI or in a connected Google Drive, OneDrive, SharePoint, or Dropbox account. Gmail itself is never modified.
• Rename and Move name and file it, either from what the AI read or from an explicit pattern and path. Existing folders are used when they fit; nothing is guessed.
• Ask a Person to Approve pauses the workflow and shows the person the plan: what will be renamed and where it will go. They approve or reject, and the file continues down that branch.
• Send a Message posts to Slack or sends an email when a file has been handled.

Every run lands in an activity feed. Any run can be replayed on the canvas exactly as it happened and retried from the step that failed. If a run fails, it hands the file back rather than leaving it half-filed.

Example Gmail attachment workflows

Each of these is the sentence you would type. The steps are laid out from it.

Accounts payable, with a limit:

When an invoice arrives at ap@northwind.com, save a copy to Finance/Inbox. If the total including tax is over $5,000, ask Dana to approve first. Otherwise file it under Vendors, then the vendor name, then the year, named "<vendor> - Invoice <number> - <date>".

Legal intake:

When a contract arrives, read the counterparty and the effective date. If it carries both signatures, file it under Clients/<counterparty>/Executed and rename it "<counterparty> MSA <effective date>". If it is unsigned, file it under Clients/<counterparty>/Drafts and message #legal.

HR onboarding packets:

When a new-hire form arrives, check whether every required section is complete. Complete forms go to People/<employee name>/Onboarding. Incomplete forms go to People/Follow-up and email hr@ with what is missing.

Real estate transactions:

When a document arrives for a property, read the property address and the document type. File it under Transactions/<address>/<type>. If it is a signed purchase agreement, ask Maria to confirm before filing.

Client deliverables from a shared inbox:

When an attachment arrives at hello@ from a client domain, save a copy to Clients/<client>/Received, named by the document title inside the file and today's date.

The last example is the simplest and the most common. Most teams start there and add a condition once they trust the filing.

Gmail filters vs Zapier vs a workflow that reads the file

Filters remain the right tool for triage inside Gmail. A connector remains the right tool when the file only needs to leave the inbox. A workflow is for the case where the folder depends on the contents.

Where do the attachments end up?

This is the question that decides whether the automation is useful, so it is worth being exact.

A Gmail attachment does not live anywhere yet. Save a Copy is the step that gives it a home. That home can be The Drive AI, where the file becomes searchable by what it says and where the assistant can answer questions about it, or a folder in a connected Google Drive, OneDrive, SharePoint, or Dropbox account.

Nothing is done to the email. It is not archived, labeled, or moved. If you use Gmail search to find the original, it is exactly where it was.

If you want a copy in two places, add two Save a Copy steps. Each one sets whether the following steps work on the copy or the original, so a workflow can file the copy in Drive and keep the original in The Drive AI for search.

What a Gmail workflow will not do

An honest list, because the limits are what make the rest trustworthy.

• AI steps can be wrong. Any step that reads the file carries the ai badge, and the badge says it can occasionally be wrong. That is why Ask a Person to Approve exists, why it shows the plan before anyone clicks, and why every run can be replayed.
• Approvals expire. An approval waits up to the time you set, three days by default and thirty at most. After that the file takes the Expired path. If nothing is connected there, nothing happens to the file, and the expiry is recorded.
• It does not read your email. The trigger is the attachment. The body of the message is not part of what the workflow decides from.
• It does not summarize, tag, or sign. There are no summarize, tag, or e-signature steps. The steps are the ones listed above.
• Connected Gmail needs a paid plan. Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail needs the Max plan on a personal workspace, or any Team plan. Each file a workflow processes counts once against a monthly allowance.

Setting up Gmail attachment automation

1. Connect Gmail. Open the Gmail integration and sign in. On a team, each member connects their own mailbox; nobody's connection reaches anyone else's mail.
2. Say what should happen. In Workflows, type a sentence like the accounts payable example above. The trigger, the check, the approval, and the filing steps appear on the canvas.
3. Decide how much to hold for you. Add Ask a Person to Approve on every file while you are building trust, or only on the branch that matters, such as invoices over a limit.
4. Pick where copies go. In Save a Copy, choose The Drive AI or a folder in a connected drive. Existing folders are reused.
5. Save and watch the first run. Send yourself a test attachment. Open the run in the activity feed, replay it on the canvas, and adjust any step. Nothing in Gmail has changed.

Teams that already save attachments by hand usually start with one mailbox and one destination, then add the condition that used to require a human to open the file. For the mechanics of the underlying integration, Gmail integration: save and organize attachments covers connection and history import.

Beyond Gmail

The same workflow grammar applies wherever files arrive. Outlook attachments work identically with a Microsoft 365, Outlook.com, or Exchange mailbox. Files shared in Slack use the Messaging trigger and can hear back in the channel. And a folder in Google Drive can be watched directly, in which case files are renamed and moved in place inside Drive rather than copied. The complete guide to automated document workflows covers how these fit together.

Frequently Asked Questions

Can Gmail automatically save attachments to a folder?

Not by itself. Gmail filters can label, archive, and forward messages, but they cannot save an attachment to a folder. Saving requires a connector such as Zapier or Make, or a workflow in The Drive AI. The difference is what decides the folder: a connector uses sender and subject, a workflow reads the attachment and decides from what it says.

Does the workflow change anything in my Gmail inbox?

No. The trigger is the attachment arriving. The workflow makes a copy with Save a Copy and works on that. The original email is not labeled, archived, moved, or deleted, and Gmail search finds it exactly where it was. Your inbox is left as it is.

Can it tell an invoice from a receipt or a quote?

Yes. Ask AI About the File opens the attachment and answers a question about it, so a workflow can send invoices, receipts, and quotes down different paths. It reads the whole document, not the filename or subject. Because the step uses AI, it can occasionally be wrong, which is why an approval step can hold the file first.

Where can the attachments be filed?

Into The Drive AI, where they become searchable by content, or into a folder in a connected Google Drive, OneDrive, SharePoint, or Dropbox account. Each Save a Copy step names one destination. Rename and Move then name and file the copy, using values the workflow read from the file or an explicit pattern you set.

What happens if the approver is on holiday?

The approval waits up to the time you set, three days by default and thirty at most. When it expires, the file takes the Expired path. If you connected nothing to that path, nothing happens to the file, and the expiry is recorded in the run history so the file is never silently lost.

Do I need a paid plan for Gmail attachment automation?

Workflows on files uploaded to The Drive AI work on every plan. Connecting a Gmail account needs the Max plan on a personal workspace, or any Team plan. Every file a workflow processes counts once against a monthly allowance, and a run that fails hands its file back without using it up.

Can several people on my team connect their own Gmail?

Yes. Each team member connects their own mailbox with their own consent. A workflow one person builds on their mailbox does not reach anyone else's mail. On a Team plan, that is how a shared process like accounts payable is built once and run against the mailbox that actually receives the invoices.

Start with one mailbox

The invoice that arrives tonight can be filed by what it says, with the one that matters waiting for a person. Build your first workflow, or see how the pieces fit on the Workflows page.