How to save emails from an Outlook to a file in Power Automate
Saves an email as an .eml file, automatically as it arrives or manually in bulk from a folder.
Here I share the best practices I use for the Power Platform tools, drawn from my own experience and plenty of learning from other people's mistakes so I don't repeat them. None of this is set in stone, so adjust it to fit how you work. Consistency matters, especially when several people share a platform. I see it constantly: SharePoint sites with mismatched naming, lists with convoluted names, and flows nobody can follow. When you agree on rules, everyone always knows what something means, and onboarding a new person becomes far easier. Even if you never adopt my conventions, at least write your own down. And even if you work alone, building your own reference makes you think, and you will often spot places where things could be better. That reflection is half the value.
Saves an email as an .eml file, automatically as it arrives or manually in bulk from a folder.
Provider SDKs often pull in dozens of dependencies when a simple HTTP request to the API would do.
Copies a file to another library or site. Version history and metadata don't carry over.
Move files past the 100 MB limit by splitting them into chunks, and know when to switch to Graph.
Returns one of two values based on whether a condition is true or false.
Why running a random curl | sh install command is a security risk, not just a convenience.
Starts a workflow at fixed times or intervals, like Unix cron. Missed runs are skipped, not backfilled.
Converts a timestamp from a source time zone to UTC using Windows time zone names.
Bundle hundreds of SharePoint writes into a single $batch request to stop hitting throttling limits.
Adds numbers, cells, or ranges into a single total. A single error in the range takes over the result.
Converts text to uppercase, leaving numbers and punctuation untouched. The result is always text.
Checks if a string is an integer.