How to Automatically Save Outlook Attachments to Folders

TL;DR: Outlook rules act on sender, subject, and keywords and cannot read an attachment, so the most they can do is move the email. A Power Automate flow can save every attachment to OneDrive or SharePoint, but it names the folder from the email's fields, usually the sender. Real outlook attachment automation reads the attachment itself: a workflow in The Drive AI opens the invoice or contract, pulls out the vendor or counterparty, and saves a named copy to the right folder in The Drive AI, OneDrive, SharePoint, Google Drive, or Dropbox. The mailbox is never touched.

An invoice from Pinecone Systems arrives in the accounts payable mailbox. Someone opens it, reads the total, downloads the PDF, renames it, and drags it into the vendor's folder. Then the next one. A team receiving 200 attachments a week spends most of a day on this, and the folders still drift.

The obvious fix is to automate it. The trouble is that both tools Microsoft gives you stop at the envelope. Outlook rules can see who sent the message and what the subject says. A Power Automate flow can save the attachment somewhere, but it does not know whether the file is an invoice or a contract, or which client it belongs to.

An Outlook attachment workflow is a set of instructions, described once in plain English, that reads each attachment as it arrives, decides where it belongs and what to call it from the document itself, and saves a copy there, holding anything that needs a person's sign-off.

Can Outlook rules save attachments to a folder?

Outlook rules act on the message, not the attachment. A rule can match a sender, a subject line, or words in the body, then move the email to a mail folder, flag it, categorize it, or forward it. There is no rule action that saves an attachment into a OneDrive or SharePoint folder, and no condition that looks inside a PDF.

That is fine for triage. "Move everything from billing@pinecone.com to the Pinecone folder" works instantly. But it leaves you with a mail folder, not a file folder. The attachment is still inside the message, still named Invoice_Final_v2.pdf, and invisible to anyone without that mailbox open.

Rules also break on the cases that matter. A vendor who sends from three addresses needs three rules. And no rule can see that this invoice is for $12,400 and needs a manager first.

Where a Power Automate flow gets you, and where it stops

Power Automate can save Outlook attachments to SharePoint or OneDrive automatically, and for one mailbox with one destination it does the job well. Ready-made templates cover exactly this: when a new email arrives with an attachment, create the file in a chosen library or folder.

The limit is what the flow knows: sender, subject, received date, attachment name. So the folder ends up named after the sender or subject, and the file keeps whatever name the vendor gave it. That is why so many teams end up with one SharePoint library of attachments sorted by email address, which is the inbox, copied.

Branching on what the attachment says is possible, but it means adding AI Builder or a separate extraction service, mapping its output to variables, and maintaining the flow as document formats change. Each step is built by hand in the designer, and licensing follows your Microsoft 365 plan. For teams that already build flows, this is workable. For everyone else it is a project.

How does Outlook attachment automation work?

A workflow starts with the Email Attachment trigger, which fires when a connected Outlook mailbox receives an attachment, and reads the attachment before deciding anything. You describe it in one sentence. The steps appear on a canvas in When / If / Then form, and you can edit them there.

A typical Outlook workflow uses these steps:

• Check File Details (free): routes attachments by file type, size, or name. Drop images and calendar invites here at no cost.
• Ask AI About the File (ai): opens the attachment and answers a question a careful reader could answer. Is this an invoice? Is the total over $5,000? Which client is this for? It reads the whole file, not the filename.
• Read Details from File (ai): pulls out named values such as vendor, total, counterparty, or effective date for later steps to use in folder paths and file names.
• Save a Copy: gives the attachment a home. Email attachments have none yet, so the copy goes to The Drive AI or to a connected OneDrive, SharePoint, Google Drive, or Dropbox account, in the folder you name. You choose whether later steps act on the copy or the original.
• Rename and Move (ai or free): use the values from Read Details from File, or an explicit pattern and path. Move uses folders that already exist when they fit; it does not guess.
• Ask a Person to Approve (human): pauses the run for anything over a limit. The approver sees the plan, including the proposed name and destination.

The mailbox is never modified. Every run is recorded in an activity feed, can be replayed on the canvas exactly as it happened, and can be retried from the step that failed. The Outlook integration works with Microsoft 365, Outlook.com, and Exchange accounts, and each team member connects their own mailbox. The same trigger covers Gmail attachment workflows.

Example workflows for four teams

Each is the sentence a user types. Change the names, limits, and folders to match your own.

Accounts payable. Invoices go under the vendor, and large ones wait for a manager:

When an attachment arrives in the ap@ mailbox and it is an invoice, read the vendor, invoice number, and total. Save a copy to SharePoint under Finance/Invoices/<vendor>/2026 and rename it <vendor>-<invoice number>.pdf. If the total is over $5,000, ask Dana to approve before it is filed.

Legal intake. Contracts are filed by counterparty, and anything unsigned goes to a paralegal:

When an attachment arrives in Outlook and it is a contract or an NDA, read the counterparty and the effective date. Save a copy to The Drive AI under Clients/<counterparty>/Contracts and rename it <counterparty>-<document type>-<effective date>. If it is missing a signature, ask Priya to approve before filing.

HR. Resumes are sorted by role, and employee paperwork is held for review:

When an attachment arrives at careers@ and it is a resume, read the candidate name and the role applied for. Save a copy to OneDrive under Recruiting/<role>/<candidate name>. If it is an I-9 or an offer letter instead, save it under HR/Employees/<employee name> and ask Marcus to approve first.

Real estate. Property documents are filed by address and type, and large closings go to a broker:

When an attachment arrives in Outlook and it is a lease, an inspection report, or a closing statement, read the property address and the document type. Save a copy to Google Drive under Properties/<property address>/<document type>. If it is a closing statement over $1,000,000, ask Elena to approve before filing.

In every case the workflow reads the document to find the vendor, counterparty, candidate, or address. The sender does not matter. For what happens once files land, see SharePoint document library workflows and OneDrive workflow automation.

Outlook rules vs Power Automate vs The Drive AI Workflows

What will it not do?

A workflow copies attachments out of Outlook; it does not manage the mailbox. If you want messages moved or marked as read, that is still an Outlook rule's job.

Steps marked ai cost a little per file and can occasionally be wrong. A blurry scan or an unusual layout can produce a wrong total or vendor. Put Ask a Person to Approve in front of anything where a wrong answer is expensive.

Approvals expire. Ask a Person to Approve waits three days by default and thirty at most. After that the file takes the Expired path. If nothing is connected to that path, nothing happens to the file and the expiry is recorded.

Move uses folders that already exist when they fit, so create Finance/Invoices or Clients before turning the workflow on, or name the path explicitly. Send a Message reaches Slack or an email address only, not Microsoft Teams. Workflows do not summarize, tag, configure OCR, or collect e-signatures.

Connecting Outlook requires the Max plan on a personal workspace or any Team plan. Workflows on files uploaded directly to The Drive AI work on every plan, including free. Every file processed counts once against a monthly allowance.

Setting it up

1. Connect Outlook. Open /integrations/outlook and sign in with the Microsoft account that receives the attachments. Each team member connects their own mailbox.
2. Connect the destination, if it is not The Drive AI. OneDrive, SharePoint Online, Google Drive, and Dropbox connect the same way. For SharePoint, a tenant administrator may need to approve the app once; the connect screen gives you the link and a ready-to-send request.
3. Describe the workflow in one sentence. Start from one of the examples above. Name the folder, the values to read, the limit, and the approver.
4. Check the canvas. Confirm the trigger is Email Attachment and Save a Copy points at the right account and folder.
5. Send yourself a test. Email an invoice to the connected mailbox and watch the run in the activity feed. Replay it if something is off, fix the step, and retry.

For triggers, steps, and where files end up across every source, read the complete guide to automated document workflows. The earlier post on saving and organizing Outlook attachments covers the integration itself.

Frequently Asked Questions

Can Outlook rules save attachments to a folder automatically?

No. Outlook rules match on sender, subject, keywords, and similar message fields, and their actions apply to the message: move it to a mail folder, flag it, categorize it, or forward it. There is no rule action that writes an attachment to a OneDrive, SharePoint, or local folder, and no condition that inspects the attachment. Saving attachments as files takes Power Automate or a workflow tool.

How do I automatically save Outlook attachments to a folder by what the attachment says?

Use a workflow with the Email Attachment trigger. Connect your Outlook account, then describe the outcome in one sentence, for example: "When an invoice arrives, read the vendor and total, save a copy to SharePoint under the vendor's folder, and ask Dana if the total is over $5,000." The workflow reads each attachment, fills in the vendor and total, and files a named copy. The email is left alone.

Does the workflow move or delete emails in my Outlook mailbox?

No. The Email Attachment trigger only reads attachments as they arrive. Save a Copy writes a copy of the attachment to The Drive AI or a connected storage account, and Rename and Move act on that copy. Nothing in the mailbox is moved, marked, or deleted. If you also want messages filed inside Outlook, keep using Outlook rules for that; the two do not interfere with each other.

Which Outlook accounts work with the Email Attachment trigger?

Microsoft 365 work and school accounts, personal Outlook.com accounts, and Exchange accounts all connect through Microsoft sign-in. Each team member connects their own mailbox, so consent is per person rather than tenant-wide. A shared mailbox such as ap@ or intake@ is connected by whoever has access to it. Connecting Outlook needs the Max plan on a personal workspace or any Team plan.

What happens if nobody approves an attachment that is waiting?

Ask a Person to Approve waits for the time you set: three days by default, up to thirty. When that passes, the file takes the Expired path on the canvas. If you connected a step there, such as Send a Message to the approver's email, it runs. If nothing is connected, the file is left where it is and the expiry is recorded, so nothing is filed silently.

Start with one mailbox

Outlook can tell you who sent a file. A workflow can tell you what the file is, and put it where it belongs. Build your first workflow, or see how Workflows handle files from every source.