Automations

Save Outlook Attachments to a Folder, Named and Filed

Outlook rules can file the message, flag it, categorise it and forward it. What they cannot do is take the attachment out and put it somewhere useful, which is the only part anybody wanted.

The short answer

An Outlook rule acts on the message rather than on what is attached to it, which is why the attachment is still sitting in the mail. A workflow starts from the Email Attachment trigger, uses the Save a Copy step to give the file a home outside the mailbox, the Read Details from File step to read what the document actually is, the Rename step to name it accordingly, and the Move step to file it into OneDrive or a SharePoint library. The message itself is left alone and nothing in the mailbox changes.

Steps this uses

Email AttachmentCheck File DetailsAsk AI About the FileRead Details from FileSave a CopyRenameMove

Before and after

What actually changes

As they arrive

  • image001.png
  • Invoice.pdf
  • ATT00012.pdf
  • scan.pdf

After the workflow

  • Finance/Invoices/2026/2026-08-14-invoice-northwind-4821.pdf
  • Finance/Invoices/2026/2026-08-19-invoice-acme-1180.pdf
  • Contracts/2026-08-21-msa-lighthouse-signed.pdf
  • Finance/Receipts/2026-08-22-receipt-dataflow.pdf

Four attachments from three senders, saved out of the mailbox and named from what is written inside them. The signature image was not one of them.

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 Outlook, save a copy out of the mail, read the document type and the party off it, rename it date-first, and file it into the right folder in SharePoint.

01

Connect the mailbox, not the desktop app

The connection is to the Microsoft 365 account rather than to Outlook on a particular machine, so it works whether the mail is read on a laptop, a phone or the web. On a work account this usually needs an administrator to consent once.

02

Decide what counts as an attachment worth keeping

Signature images, logos and tracking pixels are attachments too. The Check File Details step narrows by file type and size, so the destination folder does not fill up with images nobody attached on purpose.

03

Name it from the document, not the subject line

Subjects are written by senders and are frequently three replies deep. The Read Details from File step takes the date, the document type and the party off the document itself, which is what makes the resulting filename worth having.

04

File it where the team already looks

OneDrive for your own filing, a SharePoint library for anything the team needs. The file lands in the library itself rather than in a copy of it, so nothing has to be moved back later.

Why an Outlook rule cannot do this

Rules operate on the message. They can move it, mark it, forward it, or run a script on desktop Outlook only. The attachment is a property of the message rather than a file the rule can act on, so the best a rule achieves is a mail folder full of messages that still have to be opened one at a time. It is also why the usual answer to this question online is a VBA macro, which runs only while that copy of Outlook is open on that computer.

Shared mailboxes are where this pays off most

An invoices mailbox or an orders mailbox is a queue several people work, and the usual result is that each of them saves attachments somewhere slightly different with slightly different names. Filing from the mailbox itself rather than from one person's copy of it means the naming is identical whoever happened to be watching the queue that afternoon.

What it does not do

It saves attachments out and files them. It changes nothing in the mailbox: the message stays where it was, unread stays unread, and nothing is deleted or marked. It does not send mail on your behalf. And it reads the attachment rather than the body of the message, so an instruction written in the email itself is not something it acts on.

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 have

It needs a connected account

This workflow reads files out of a connected Outlook 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

Can Outlook save attachments automatically?

Not on its own. Outlook rules act on the message rather than the attachment, and the usual workaround is a VBA macro, which only runs while that copy of Outlook is open on that computer. A workflow connected to the mailbox does it server side, so it runs whether or not anyone has Outlook open.

Does this change anything in my inbox?

No. The attachment is copied out and filed, and the message stays exactly where it is with its read state and its folder untouched. Nothing is deleted and nothing is sent.

Can attachments go into SharePoint rather than OneDrive?

Yes, and for anything a team uses that is the better destination. The file lands in the library you choose, in the folder the workflow works out from what the document says it is.

What about Gmail?

The same workflow shape applies and it has its own page, because the connection and the usual destinations are different. Outlook attachments tend to belong in OneDrive or SharePoint, and Gmail attachments in Google Drive.

The attachment lands where it belongs.

Saved out of Outlook, named from what is inside it, filed in OneDrive or SharePoint.

Build this workflow

5 GB free · No credit card required