Save email to Sharepoint document library (full email)

[BalletBob]

Hi,

We'd like to save a copy of an email to a Sharepoint document library for future reference. These are our outbound marketing emails and don't have attachments. We'd like to capture the body of the email, preferably how it looks in email.

Any ideas?

Thanks

Damien

[v-yamao-msft]

Hi BalletBob,

How about using a “Create file” action of SharePoint Online to save emails?
I had a flow, “when a control is selected, send email(Subject and Body were set to Ask in PowerApps), create file in SharePoint(File name and File content were set to Ask in PowerApps)”. In the App, I added one Button and two Text input(Text input1 for subject and Text input2 for Body), then added the flow to the Button. when the button was clicked, someone received the email and a file was created to the SharePoint library.
Here is a screenshot of my flow, please try if it works for you.

 

Best regards,
Mabel Mao

[Courtenay]

Hi there,

I just wanted to update this thread.

It is now possible to do this within flow using Parserr. We have just joined the Flow community and wanted to thank everyone in the flow team for making this possible:

https://flow.microsoft.com/en-us/services/shared_parserr/parserr/

Parserr allows you to turn incoming emails into useful data to use in various other 3rd party systems.You can use to extract anything trapped in email including email body contents and attachments.

Have a look here: https://parserr.com

[C_Helzer]

anyone know of a working solution? When I try this, the resulting file is a blank email file.

[Anonymous · Accepted solution]

The solution is pretty strait forward now.

The best practice is to combine outlook mail rules and Power Automate flow.

You can set up a folder, and use mail rule to determine which mails need to be archived (move the mail to this folder). And then in Power Automate flow, just monitor the new mails to this folder.

It will be better to add a time stamp to the file name.

[BalletBob]

I've marked this as the solution as both Teams and Sharepoint now natively support viewing MSG files which they didn't when I posted the question.

I was looking to end up with a PDF or image file but I guess I no longer need to.

[Amgarnier]

This is great thanks for the update

[XSpence8]

@Anonymous trying this and getting a failure, advising me to inspect my inputs. Any thoughts on what I missed?

EDIT: Adding flow details

[JP-007]

This worked nicely.  But there seems to be a problem.  When you open the created email in the browser (preview) it takes ages to open.  This only affect emails 'created' with the method you posted.  Actual emails dragged and dropped into sharepoint open with no problems.

A second issue is, if you download a 'created' email, it will not open in outlook.  Error:
"We can't open #filename It's possible the file is already open, or you don't have permission to open it."
FYI, I definitely have permissions on the file.

Any ideas on either issue?

[JP-007]

Please note, if you have trouble opening the file (email) after you re-download it, you may want to change the file ext to .eml

Please see this link... Solved: Not able to open email (.msg) file locally, create... - Power Platform Community (microsoft....

[skagawa]

I used this same flow and got a blank message

[skagawa]

See screen shot, 

[rceighteen0eigh]

Also using the same flow but I get the same blank email as skagawa. I have tried changing the extension from .msg to .eml to no avail. Any advice would be appreciated. 

[skagawa]

OK eventually I got this to work, though not sure what i changed or what i did. So my take away is this solution works and it was user error. 

[LauraCas72]

I tried to use this set up to save to One Drive, but I got an error on the Outputs

[Roaduser]

Instead of create file.

How do I use the export email, to then ad attachment? I want the email exported/saved into the list item as an attachment.

Is this possible rather than a link to a file in the doc library, which  I can do with the example above.?

[FabvE]

The Export mail-action leads to a timeout everytime I start the flow.

Instead I tried to directly use 

triggerOutputs()?['body']

but this generates just an empty email....

[Steve_luck22]

Has anyone else every faced problems with certain parts of the automation skipping? i have tested the flow from my own email address and it works fine, but when i receive an email from the person i want to automate it skips the final process? anyone else ever faced this issue? is there a solution for it?

[theseannn]

For those experiencing this issue finding this post - I have discovered *a solution* to the issue  It may not be your solution - but it was mine for the blank email error.

Make sure in your Flow creation that you in your Create a File component, the File Content you have selected (eg:  Body) is the one from the relevant Export component eg:

I noticed that when the "blank" emails are downloading, they're all varying sizes (8kb/15kb/etc) - so I figured they must be downloading some level of content and realised they're not actually blank - they're generating as Word Documents, so if you're using Create a File to make them .eml/.msg then that's why they're blank.

So basically if you're using the Body output from the initial Trigger, then it will generate the email as a Word Document and that's where the confusion is setting in.

Hope this helps someone out there - because I've spent an embarrassingly long amount of time trying to find the solution.  There's nothing worse than googling a problem to find someone discovered it 10 years ago, made an updated to say they found a solution, but never gave an answer.