How to Automatically Save Email Attachments to SharePoint With Power Automate Easily 2026

Open My flows in Power Automate to see everything you've already built, listed with a Name, Modified date, and Type column. In a working account this list fills up fast — automated flows, instant button-triggered flows, scheduled ones — so it's worth naming things clearly, as seen with entries like "Automated Report" and "When a new email arrives (V3) -> Condition Apply to e..." which describe what they do at a glance. To start a fresh flow for saving attachments, use New flow and choose an automated cloud flow, since this needs to fire on an event (a new email) rather than a fixed schedule.

The trigger block, "When a new email arrives (V3)," connects to your Outlook mailbox and exposes a set of Advanced parameters beyond the basic folder and sender fields. Two matter most here: Include Attachments, set to Yes, which is what makes the attachment data available to later steps at all, and Subject Filter, set to a value like "Automated Reports," which narrows the trigger so it only fires for emails matching that subject instead of every message that lands in the inbox. Filtering by subject (or sender, or folder) up front keeps the flow from processing irrelevant mail and wasting runs.

It helps to look at the real inbox the flow is connected to before trusting the automation. In this account, the Outlook inbox shows a thread of test emails with the subject "Automated Report," sent to confirm the trigger fires as expected — exactly the kind of matching subject line the Subject Filter parameter was set to catch. Sending yourself a test email with the target subject and attachment before going live is the fastest way to confirm the trigger condition is set up correctly.

Once the trigger fires, add a step to pull the attachments out of the email body — Power Automate exposes them as a collection you can loop over with an Apply to each control, which matters because a single email might carry more than one file. Inside that loop, each attachment gives you its file name and content, which is exactly what the next step needs to write it somewhere else.

Add the "Create file" action for SharePoint, point it at your target site and document library, and map the attachment's file name and content into it. If you want attachments organized rather than dumped into one folder, add a condition before the Create file step that checks the sender or subject and routes the file into a matching subfolder — for example, reports from one sender going into a "Finance" folder and another sender's into "Operations."

Re-sent emails or slightly different messages with the same filename can otherwise overwrite or clutter the library. Add a check — either a "Get file metadata" call against the target folder or a simple existence check — before the Create file step, and if a match is found, append a timestamp or a counter to the filename rather than skipping the save outright, so nothing gets silently lost.