← Al Davies, 250 High Street

How to save an email to SharePoint with Power Automate

Use the Office 365 Outlook action Export email (V2) to turn the email into an EML file. Then add the SharePoint action Create file to store it in a library.

What does this flow save?

Export email (V2) exports the content of one email in the EML file format. The EML file is the whole message. If you only want the attached files, use the other flow in saving email attachments to SharePoint.

You can run both in one flow if you want the message and its files in the same place.

How do you build the flow?

Menu and button names can vary by tenant, so match what your screen shows.

  1. Go to Power Automate and select Create, then Automated cloud flow.
  2. Pick the trigger When a new email arrives (V3). Set the Folder, and add filters if needed.
  3. Add the action Export email (V2) from Office 365 Outlook.
  4. For Message Id, choose the Message Id from the trigger.
  5. Add the SharePoint action Create file.
  6. Set Site Address and Folder Path. The folder path must start with an existing library.
  7. Set File Name, for example the subject plus .eml.
  8. Set File Content to the output of Export email (V2).
  9. Save and send yourself a test email.

What should the file name be?

The File Name field is required. Add .eml at the end, or the file will have no type. Email subjects can hold characters that SharePoint does not allow in file names, so clean the subject first. Our guide on replacing text shows how.

A good pattern is the received date, then the sender, then a cleaned subject. This is advice, not a rule.

How do you trigger it for emails you choose?

The new email trigger fires on every match. To save only some emails, use its filter fields, such as From or Subject Filter. Another trigger, When an email is flagged (V4), runs when you flag a message. Microsoft lists it as a preview feature.

For a flow you start by hand on a record, see running a flow on a selected item.

Are there size limits?

The new email trigger skips any email larger than the limit your Exchange admin set, or 50 MB, whichever is less. It may also skip protected emails and emails with an invalid body or attachment. Test with a large email before you rely on the flow.

Microsoft's connector page does not say how Export email (V2) treats attachments, so open an exported file and check it.

What if you want a list item instead of a file?

If you want a row for each email, with sender and subject in columns, create a list item. See creating a list item from an email. Some teams use both: a row to track, and an EML file to keep as the record. That is advice, not a rule.

Want help with this?

If you would rather have someone build a flow like this for you, I can help. I am Al Davies at 250 High Street LLC, and I build SharePoint and Power Automate trackers for small teams, fully remote. A tracker is $5,000 and takes 2 weeks, and the first call is free. You can see past work in the portfolio.

FAQ

What file type does Export email (V2) make?

It exports the email content in the EML file format.

Does Create file need a library?

Yes. The folder path must start with an existing library.

Can I save to a list instead?

Yes, with Create item. See the list item guide linked above.

Sources