How to Save Email Attachments Automatically

Choose a small, clear set of emails

Start with one recurring file, such as a supplier delivery sheet or a weekly branch report. Write down the sender, the usual subject and the file types you expect. Avoid a rule that saves every attachment from the entire inbox.

For example: save PDF delivery sheets from an approved supplier when the subject includes the order reference. Leave newsletters, signatures and unrelated messages alone. Keep the original email so someone can check where a file came from.

Pick a folder the right people can use

Choose an existing business folder, such as Deliveries / 2026 / October. Check that the person who uses the files can open it, and that unrelated staff or clients cannot.

Name files so they make sense outside the email. A useful pattern is date, supplier, order reference and original file name. If a reference is missing, put the file in a Needs checking folder instead of guessing.

Keep different files with the same name separate. Two suppliers may both send delivery.pdf. Adding the supplier and order reference makes it easier to find the correct one.

Connect the inbox to the folder

If you already use Microsoft 365, Power Automate can start a flow when an email arrives. A flow is a saved set of steps. Microsoft documents filters for the sender, subject, folder and whether the email has attachments.

Choose the matching email, go through its attachments and save each allowed file into your chosen storage folder. Skip inline images such as email signature logos. Keep normal email security checks in place; saving a file should not open or run it.

For busy Outlook inboxes, Microsoft recommends getting attachments in a separate Get Attachment (V2) step when downloading them in the trigger causes timeouts. Check the connector limits and what your existing account includes before choosing the setup.

A simple delivery-sheet example

Imagine a small shop receives two delivery PDFs from one supplier. Both emails include order 184. The first file is the delivery sheet; the second is a corrected version sent later.

The first email saves a file named 2026-10-20_supplier_order184_delivery.pdf. The later email saves a separate corrected copy with its received time. A short log keeps the email reference, saved-file link and result.

The rule should not overwrite the first sheet just because the names match. A person can check which version to use.

Handle repeats and missing files

Record the email identifier and attachment identifier after a successful save. These are the reference numbers the email service gives the message and file. Before saving again, check whether that pair already has a completed entry.

A forwarded copy may have a new email identifier. If that is common, add a review for matching file content or order references. Do not delete a possible duplicate automatically when the file might be a revision.

If the folder is unavailable or an attachment is too large, send a clear internal alert with a link to the email. Mark it as saved only after the file exists and can be opened.

Test the awkward cases

Try one normal email, two attachments in one email, a repeated run and two different files with the same name. Also try a message with only a signature image and a file that does not meet your rule.

Open the saved files and check their contents. Confirm that a failure is visible to the person responsible. Run the small pilot for a few working days before adding more senders.

Use the worksheet below to write your rule. For help connecting your inbox and folders, send Automations For Business the tools you use and one example of the job on WhatsApp.

Your ready-to-use checklist

Make the next step clear.

Sources and notes

Sources checked on October 20, 2026.

• Microsoft: start a flow from email properties

  Sender, folder, subject and attachment filters.

• Microsoft: Office 365 Outlook connector

  Attachment fields, inline images and timeout guidance.