Easy Tech Tuts
SharePoint

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

By Impran M NLast checked against official docs

Manually pulling attachments out of email and dropping them into SharePoint is a small chore that quietly eats a chunk of every week. Power Automate replaces it with a flow that watches your inbox and saves matching attachments the moment they arrive. This guide follows a real flow built around a "When a new email arrives (V3)" trigger filtered to a specific subject line, so you can see the actual trigger configuration and the inbox it's watching, not just a description of the steps.

Before you start

  • A Microsoft 365 account with access to Power Automate and the target SharePoint site
  • Edit access to the document library the flow will write to

01Find your existing flows or start a new one

Open My flows in Power Automate to see everything you've already built, listed by Name, Modified date, and Type. Name flows clearly as this list grows — entries like "Automated Report" or "When a new email arrives (V3) -> Condition Apply to e..." describe what they do at a glance, which matters once you have a dozen of them. To start fresh, use New flow and choose Automated cloud flow, since this needs to fire on an event (a new email) instead of a fixed schedule.

The My flows list, showing existing automated flows including one built around a new-email trigger with a condition step.
The My flows list, showing existing automated flows including one built around a new-email trigger with a condition step.

02Configure the When a new email arrives trigger

The trigger block, "When a new email arrives (V3)," connects to your Outlook mailbox. Open its Advanced parameters and set Include Attachments to Yes, which makes the attachment bytes available to later steps, and Subject Filter to a value like "Automated Reports," which narrows the trigger to matching emails only.

Set Only with Attachments to Yes alongside them so the flow doesn't fire at all on messages with nothing to save. Skipping Include Attachments is the most common reason Create file fails later with a null-content error.

The email trigger's Advanced parameters panel, with Include Attachments set to Yes and a Subject Filter narrowing it to matching emails.
The email trigger's Advanced parameters panel, with Include Attachments set to Yes and a Subject Filter narrowing it to matching emails.

03Confirm what the trigger is watching

Check 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. Sending yourself one test email with the target subject and an attachment, before turning the flow loose on real mail, is the fastest way to catch a misconfigured filter.

The connected Outlook inbox with a series of "Automated Report" test emails, used to confirm the trigger's subject filter is matching correctly.
The connected Outlook inbox with a series of "Automated Report" test emails, used to confirm the trigger's subject filter is matching correctly.

04Save each attachment to a SharePoint document library

Add a "Create file" action from the SharePoint connector under the trigger, and point it at your target site and document library. Set File Name to the Attachments Name dynamic value and File Content to Attachments Content.

Attachments is a collection, not a single value, so Power Automate wraps the Create file action in an Apply to each loop automatically the moment you pick that dynamic content. A message with three files creates three rows without any extra step. To keep files organized, either add a condition before Create file that checks the sender or subject and branches into a subfolder, or follow up with an "Update file properties" action to tag the new file with sender and received-date metadata instead of moving it into a folder.

05Guard against duplicate files

Re-sent emails or near-duplicate messages with the same filename can overwrite each other in the library, or just clutter it. Add a check before the Create file step, either a "Get file metadata" call against the target folder or a simple existence check. If a match turns up, append a timestamp or counter to the filename instead of skipping the save, so nothing gets silently lost.

When it doesn't work

Create file fails with a 400 Bad Request the first time the flow runs

Why: Include Attachments was left at its default of No on the trigger, so the attachment's content bytes are null by the time Create file tries to read them.

Fix: Open the trigger's Advanced parameters and set Include Attachments to Yes.

The flow runs on every email, even ones with nothing to save

Why: Only with Attachments was left unset on the trigger.

Fix: Set Only with Attachments to Yes in the same Advanced parameters panel.

A saved file opens as corrupted, or won't open at all

Why: File Content in the Create file action was mapped to the wrong dynamic value, usually Attachments Name instead of Attachments Content, or an inline signature image got swept in as if it were a real attachment.

Fix: Recheck that File Content points to Attachments Content, and add a condition to skip attachments under a few KB if signature images keep getting saved.

FAQ

Frequently asked questions

Can I filter which emails trigger the flow?

Yes. The trigger's Advanced parameters include Subject Filter, sender and folder options, and Only with Attachments, so the flow only fires on matching mail that has something to save.

What happens if an email has multiple attachments?

Power Automate wraps the Create file action in an Apply to each loop automatically the moment you map its File Content field to the Attachments Content dynamic value. There's no separate loop to build by hand.

How do I avoid saving duplicate files?

Add a file-existence check against the target SharePoint folder before the Create file step, and append a timestamp or counter to the filename if a match is found.

Can attachments be organized or tagged automatically?

Yes, two ways: a condition on sender or subject before Create file to route files into different folders, or an Update file properties step afterward to tag the file with metadata like sender and received date instead of moving it.

Do I need Include Attachments turned on for this to work?

Yes. Without it, the attachment content bytes are null and the Create file action fails. Only with Attachments is a separate, optional setting that just stops the flow firing on mail with no attachments at all.

Sources and last check

Trigger configuration and screens come from a flow build recorded in July 2025. The Apply to each auto-insertion, the Only with Attachments parameter, and the Update file properties alternative were re-checked in September 2026 against Microsoft's own Power Automate training module for this exact scenario. That check corrected the earlier description of extracting attachments as a separate manual step.

About the author

Impran M N
Written by

Impran M N

I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.