How to Automatically Save Email Attachments to OneDrive with Power Automate Easily 2026

From Create, choose Automated cloud flow, which opens a "Build an automated cloud flow" dialog asking for a Flow name and a trigger. The trigger list is searchable and covers a wide range of events — When a new response is submitted, When an item is created in SharePoint, When a file is created in OneDrive for Business, and more — but for this flow you want the Outlook trigger, "When a new email arrives." Naming the flow clearly here (rather than leaving the auto-generated name) makes it much easier to find later in a busy My flows list.

After the email trigger, this flow adds a Condition step that splits into a True branch and a False branch — in this case, checking whether the email came from inside the organization (pmnonline) versus an outside customer. Branching like this before you even touch attachments means you can route internal files and external files to completely different destinations without writing two separate flows.

Inside the flow designer, search the action picker for "onedrive" to see the available OneDrive actions: Create file, Copy file using path, Upload file from URL, Get file tags, and more. Create file is the one that matters here — it takes a file name and content and writes it into a folder you specify. This flow adds a Create file action inside both the True and False branches of the earlier condition, so each path ends up writing to its own destination.

An email can carry more than one attachment, so each branch wraps its Create file action inside an Apply to each loop set to the trigger's Attachments output. In the finished flow this shows up as two clearly named loops — "Apply to each email attachment from pmnonline" feeding into "Create file in pmnonline," and "Apply to each email attachment from outside customer" feeding into "Create file for Customers." Naming the loops and actions this specifically, rather than leaving Power Automate's defaults, makes the whole flow self-documenting when you or a teammate opens it months later.

Inside each Create file action, set the folder path to wherever that branch's files should land — an internal team folder for the True branch, a customer-facing or intake folder for the False branch. Keeping these destinations separate at the flow level means nobody has to remember to manually sort attachments after the fact; the routing decision happens automatically based on the sender.

Because this flow can run every time a matching email arrives, the same attachment name can show up more than once if someone resends a message. Add a check before Create file — either a Get file metadata call against the target folder or a simple condition on the file name — and if a match already exists, append a timestamp to the new file's name rather than overwriting or skipping it, so you never lose a file silently.