Power Automate is included in most Microsoft 365 business plans and is used by almost nobody. Partly because the name suggests something technical, and partly because Microsoft's own examples are unconvincing.
Here are five flows that genuinely earn their place in a small business, and the three rules that separate a flow you can rely on from one that quietly stops working in March.
The licensing, briefly
Worth understanding before you plan anything, because it determines what is free and what is not.
Standard connectors — Outlook, SharePoint, Teams, OneDrive, Forms, Planner, Excel — are included with most Microsoft 365 business plans. Everything below uses only these.
Premium connectors — SQL databases, Salesforce, HTTP requests to arbitrary systems, Dataverse — need an additional per-user or per-flow licence. The per-flow licence is often the better buy for a business with two or three important automations, because it covers everybody using that flow.
Flow 1: form submissions to somewhere useful
What it does. A Microsoft Form or website enquiry arrives. The flow writes it to a SharePoint list, posts a notification in the relevant Teams channel and sends the enquirer an acknowledgement.
Why it earns its place. It converts an enquiry from a message in somebody's inbox into a tracked item with an owner and a date. The acknowledgement alone measurably improves conversion, because a customer who hears nothing for a day assumes you did not receive it.
Build effort. An hour or two. This is the standard first flow and it is a good one.
Flow 2: email attachments into SharePoint
What it does. Attachments arriving at a monitored address — supplier invoices, signed documents, delivery notes — are saved automatically into the right SharePoint library, named consistently by sender and date.
Why it earns its place. It removes the save-and-file step entirely, and it removes the variation between how five different people name files. That consistency is worth as much as the time saved, because it makes everything findable afterwards. It also supports the file discipline described in where files should live.
Build effort. An hour, plus thought about the naming convention.
Flow 3: approvals that do not live in email
What it does. A request — purchase, holiday, discount, expense — creates an approval task with a due date. The approver responds in Teams or email. The outcome is recorded and the requester is told.
Why it earns its place. Approvals over email are invisible. Nobody can say what is outstanding, how long approvals take or where a particular request has got to. A proper approval flow makes all three visible without anybody chasing.
Build effort. Two to three hours. Most of that is agreeing who approves what, which is a management conversation rather than a technical one.
Flow 4: the chase you keep forgetting
What it does. Watches a SharePoint list or a shared mailbox for items past a date and prompts the owner. Overdue quotes, unreturned documents, unpaid invoices, expiring certifications.
Why it earns its place. Chasing is the work most reliably dropped when people are busy, and it is directly attached to revenue. A flow that reminds somebody on day seven that a quote has not been followed up is one of the highest-return automations a small business can build.
Build effort. An hour or two. There is more on this pattern in automating invoices and payment chasing.
Flow 5: the daily digest
What it does. Instead of twenty notifications during the day, one message each morning summarising what needs attention: new enquiries, overdue items, approvals waiting.
Why it earns its place. It reduces interruption while increasing visibility, which is a rare combination. It is also usually the flow people like most, because it replaces the vague anxiety of a busy inbox with a short list.
Build effort. Two to three hours, and worth iterating on for a fortnight until the content is right.
Three rules that keep flows working
1. Never own a flow personally
A flow owned by an individual account stops when that person leaves, changes role or has their permissions altered. Use a service account, and add a second owner so somebody else can open and fix it.
This is the most common cause of an automation that worked fine for eight months and then did not.
2. Alert on failure, to somewhere monitored
By default a failed flow notifies its owner and stops. If nobody reads those notifications, the flow silently ceases, and everybody carries on assuming the task is being done.
Configure failure alerts explicitly, to a Teams channel or a monitored mailbox that a named person checks.
3. Write down what it does
One page per flow: what triggers it, what it touches, who owns it and how to do the job manually if it is down. Store it with the flow, not in somebody's head.
The difference between an automation and a liability is whether anybody other than the person who built it can explain what happens when it breaks.
Where Power Automate stops being the right tool
It handles moving information between systems that have connectors. It is a poor fit when data needs meaningful transformation, when a system has no connector, when volumes are high or when the process is complex enough that the visual editor becomes harder to read than code.
At that point you want proper system integration rather than a flow, and it is better to recognise that early than to build something increasingly fragile.
If you would like the first two or three flows built properly — owned correctly, alerting on failure and documented — that is routine work for our business automation team. Tell us what your team retypes most.
