If you built the one-click consolidation, your monthly report now assembles itself from a folder. Which leaves exactly one manual step in the whole pipeline: someone still has to save the email attachment into that folder. Every month. Without going on holiday.

Power Automate exists to delete steps like that one. It’s the plumbing layer of Microsoft 365 — when this happens, do that — and this single flow is the best first project in it: small, genuinely useful, and finished in fifteen minutes.

The shape of a flow

A flow has two halves. A trigger — the event that starts it — and actions — what happens next. Ours:

When an email arrives with an attachment, from the finance system’s address → save the attachment to the reports folder on OneDrive/SharePoint.

Build it at make.powerautomate.com (it’s in most Microsoft 365 work licences — the tile you’ve scrolled past for years):

  1. Create → Automated cloud flow, trigger: When a new email arrives (V3).
  2. Open Advanced options on the trigger and make it precise: From = the sender that mails the export, Has Attachment = Yes, Subject Filter if the sender mails other things too. Precision here is the whole game — you’re writing the drop-down-list of emails allowed to feed your report.
  3. Action: Create file (OneDrive/SharePoint) → folder = your reports folder, name = the attachment’s name, content = the attachment’s content. Wrapped, automatically, in a loop over each attachment.

Turn it on. From now on the export files appear in the folder, and next time you open the workbook, Refresh finds them — months of them, whether you were at your desk or on a beach.

inbox finance-system@… "June export" 📎 Sales_Jun.xlsx the flow: right sender? → save file reports folder Sales_Apr.xlsx Sales_May.xlsx workbook Refresh reads all nobody saved anything — the trigger fired, the action filed it, the recipe read it
Email in, file filed, refresh fed. The last manual step of the monthly report, retired by one trigger and one action.

Three habits that keep flows trustworthy

Automation you can’t see fail is automation you’ll stop trusting.

  • Tell yourself it worked. Add a step: Send a mobile notification or a Teams message — “June export filed”. Thirty seconds of setup buys you the same comfort as the backup engineer’s daily check: silence is never assumed to be success.
  • Let failures be loud. The flow’s run history shows every execution, green or red; the service emails you when runs fail repeatedly. Glance at the history the first few months — the IFNA principle, applied to plumbing.
  • Name it for the person who inherits it. “When finance mails the export, file it for the sales report” beats “Untitled flow 3” — the same kindness as a named range.

Where to stop (the honest part)

Power Automate can do vastly more — approvals, Teams posts, Forms responses into Tables, writing rows into Excel directly. Some of it you should take; some is a trap for the enthusiastic. The line that’s served me: automate the transport of data; keep the transformation in Power Query, and the thinking in the workbook. A flow that moves files is transparent and nearly unbreakable. A flow that edits spreadsheet rows one by one is a fragile robot doing a job the recipe does better in bulk — slower to debug, easier to double-fire, harder to audit.

And the trigger-precision rule has a security face: this flow files attachments from one trusted sender. Resist the tempting general version (“save every attachment I receive”) — you’d be piping the whole world’s spam into the folder your report trustingly reads.

One trigger, one action, one notification. The pipeline now runs from the finance system’s Send button to your refreshed dashboard — and the only monthly job left is reading the thing.