Automations/Everyone
Save Gmail Attachments to a Folder, Named and Filed
The contract is in an email from March. So is the invoice, the signed W-9, and the revised statement of work. Your inbox has become a filing cabinet that only opens with a search box.
The short answer
An email attachment has no home. It lives inside a message, which is why finding it later means remembering who sent it and roughly when. The Email Attachment trigger picks up attachments as they arrive in Gmail, the Save a Copy step gives each one a home in cloud storage, and the Rename and Move steps name it from its contents and file it. Nothing is forwarded, downloaded or re-uploaded — the attachment goes from the message to the folder it belongs in.
Steps this uses
Before and after
What actually changes
As they arrive
- document.pdf (from billing@northwind.com)
- scan.pdf (from bookkeeper@acme.co)
- FINAL v2.pdf (from legal@lighthouse.io)
After the workflow
- Invoices/2026-08-02-invoice-northwind-4821.pdf
- Receipts/2026-08-04-receipt-acme.pdf
- Contracts/2026-08-09-contract-lighthouse.pdf
Three attachments named by three different senders, filed by what they actually are.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When an attachment arrives in Gmail, save a copy to my drive, read what the document is off it, rename it date-first, and file it into the folder for that document type.
Connect Gmail
The Email Attachment trigger watches for messages carrying attachments. You can narrow it to a label, a sender, or a subject so unrelated mail is left alone.
Save a Copy gives it a home
This step is not optional for email. An attachment has no folder of its own until something files it, which is what separates email from cloud storage where files already live somewhere.
Name it from the document
The Read Details from File and Rename steps name the attachment from what is written inside it, not from what the sender happened to call it.
File it
The Move step puts it in the folder the document belongs in.
Why attachments are different from files in a drive
A file in Google Drive already has a home; a workflow watching that folder renames and moves it in place. An attachment does not — it exists inside a message and has never had a folder. That is why the Save a Copy step comes first for email and never appears in a cloud-storage workflow. It is the step that turns a message attachment into a file.
Narrowing what gets filed
Filing every attachment in an inbox is rarely what anyone wants, because inboxes carry signatures, logos and calendar invitations. Restricting the trigger to a label, a sender or a subject line is how you keep the workflow pointed at the mail that matters — and applying a label in Gmail is something you were probably doing anyway.
Outlook works the same way
The same trigger and the same steps apply to Outlook. The difference is only which mailbox is connected; an attachment has no home in either system, so Save a Copy does the same work.
Then build
Variations worth building next
When an attachment arrives in Gmail with the label Clients, save a copy to our SharePoint library, read the client off the document, rename it date-first, and file it under that client.
Puts client attachments in storage the team shares instead of one person's drive.
When an attachment arrives in Gmail, ask AI whether it is an invoice, a contract or something else. Save invoices and contracts to my drive under Invoices or Contracts, renamed date-first, and skip everything else.
Files only the documents that matter and leaves logos and invitations in the inbox.
When an attachment arrives in Gmail from my accountant, save a copy to my drive, rename it date-first from its contents, file it by document type, and send me a Slack message saying where it went.
Tells you the moment an important sender's document is filed and where to find it.
Limits
What to know before you build it
It runs on new files, not your backlog
This workflow fires when a file arrives. It will not go back over the documents already sitting in the folder, so switching it on leaves the existing pile exactly where it is. Working through what is already there is a scheduled run instead, which is a different workflow.
Organize the files you already haveIt needs a connected account
This workflow reads files out of a connected Gmail account, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.
FAQ
Common questions
How do I save Gmail attachments to Google Drive automatically?
Connect Gmail so the Email Attachment trigger picks up messages carrying attachments, then the Save a Copy step files each one into Google Drive. The Rename and Move steps name it from its contents and put it in the right folder. Nothing is forwarded or downloaded.
Can I save attachments from only certain emails?
Yes. Narrow the trigger to a Gmail label, a sender or a subject so the workflow ignores everything else. Most people restrict it to a label they already apply.
Why do email attachments need an extra step?
Because an attachment has no home. A file in cloud storage already sits in a folder and can be renamed in place; an attachment lives inside a message, so the Save a Copy step has to give it a folder before anything else can act on it.
Does this work with Outlook?
Yes. The same Email Attachment trigger and the same steps apply — only the connected mailbox differs.
Give every attachment a home.
Filed and named the moment it arrives, instead of found by searching your inbox in April.
5 GB free · No credit card required