Power Automate examples that save hours each week
Three illustrative small businesses and the Power Automate flows each should build first, then what your Microsoft 365 licence covers, the daily action limits, and how to stop flows dying when someone leaves.
On this page
- Which flows should an accounting practice build first?
- Which flows suit a small clinic?
- What would a distributor automate first?
- What does a Microsoft 365 licence cover in Power Automate?
- How many actions can a flow run each day?
- Who should own a flow?
- How do you build a flow that doesn't break in the first month?
- When is Power Automate the wrong tool?
Build the flow that removes the most chasing first, not the cleverest one. In most small businesses that's an approval, a filing flow or a reminder, and nearly all of them run on standard connectors, which Microsoft 365 business plans already include. Premium connectors and desktop automation cost extra, so it pays to know which side of that line a flow sits on before you build it.
Below are three illustrative businesses, an accounting practice, a clinic and a distributor, with the flows I'd start each one on. They're examples to adapt, not case studies. After them come the licensing and ownership rules that apply to all three.
Which flows should an accounting practice build first?
An accounting practice gains most from filing documents automatically and never missing a deadline. Both run on Outlook, SharePoint and a list.
Take an illustrative 12-person practice. Clients email bank statements and receipts to a shared accounts@ mailbox, and a junior spends part of each morning saving attachments into client folders. A flow watches that mailbox, saves each attachment into the client's SharePoint library based on the sender's address, and posts a note in the client team's Teams channel. Senders it doesn't recognise go to a "to sort" folder for a person to check.
The second flow is a deadline reminder. Keep filing deadlines in a SharePoint list with a date column and an owner, and run a scheduled flow each morning that emails the owner a week before and again two days before. The list stays the record; the flow only nudges.
Third, a leave request built on Microsoft Forms and Approvals, writing each decision to a list so the partners can see who's off in busy months.
Which flows suit a small clinic?
A clinic's quickest wins are in admin around patient care rather than in the clinical records themselves. Routing enquiries, handling staff leave and tracking equipment checks are good places to start.
Say an illustrative clinic gets enquiries through a website form and a Microsoft Form. A flow sends each one to the right person by the option chosen (appointments to reception, billing questions to the office manager) and logs it in a list with the time it arrived, so nobody has to forward emails by hand.
Equipment servicing is the second. A list holds each item, its last service date and the interval, and a weekly flow emails the practice manager anything due in the next month. A new starter checklist in Planner, created by a flow when HR adds a name to a list, rounds out the first set.
Before any flow copies patient details into email, Teams or a list, check what your local health-data rules require. Often the safer design is a flow that sends a link to the record rather than its contents.
What would a distributor automate first?
A distributor usually starts with purchase approvals and supplier paperwork, because that's where orders stall. Both fit inside Microsoft 365.
For an illustrative distributor, purchase requests over a set amount go into a list, and a flow sends an approval card to the manager in Teams. If nobody answers in two days, it reminds them, then escalates to a director. Supplier invoices arriving in a mailbox get filed into a SharePoint library by supplier, the same pattern as the accounting practice. A scheduled flow sends a Monday summary of open purchase requests and contracts renewing in the next 60 days, pulled from lists.
| Flow | Starts when | Connectors used | Who it suits |
|---|---|---|---|
| File attachments by sender | An email arrives in a shared mailbox | Outlook, SharePoint, Teams | Accounting practice, distributor |
| Deadline or renewal reminder | A daily or weekly schedule | SharePoint list, Outlook | All three |
| Enquiry routing | A form is submitted | Forms, Outlook or Teams, SharePoint list | Clinic |
| Purchase approval with escalation | A request is added to a list | SharePoint list, Approvals, Teams | Distributor |
| Leave request | A form is submitted | Forms, Approvals, SharePoint list | All three |
| New starter checklist | HR adds a name to a list | SharePoint list, Planner, Teams | Clinic, and anyone hiring |
Every connector in that table is a Microsoft 365 service, which counts as standard.
A word on our interest: Cloudgramam builds Power Automate flows for clients, so we sell this work. Power Automate licences are paid to Microsoft or your partner, not to us. Licensing details below were checked on Microsoft's pages on 16 November 2026.
What does a Microsoft 365 licence cover in Power Automate?
Microsoft 365 business licences cover cloud flows with standard connectors. Premium connectors need a Power Automate Premium licence or a Process licence.
Microsoft's Power Automate licensing pages say Microsoft 365 licences include creating and running cloud flows with standard connectors. Power Automate Premium is listed on Microsoft's pricing page at $15 per user per month, paid yearly; a Process licence is assigned to a specific flow instead of a person. Microsoft's plan comparison marks Power Automate on Business Basic and Standard as "cloud flows only", so desktop automation of older software isn't included.
How many actions can a flow run each day?
The official limit on Microsoft 365 licences is 6,000 actions per user per 24 hours. Design for that number, even though a looser transition limit applies today.
Microsoft's request limits page lists 6,000 actions per user per 24 hours as the official limit for Office 365 licences. All organisations are currently in a transition period where the limit is 10,000 per flow instead, and Microsoft says per-user limits start replacing it in a phased rollout from April 2027. None of the flows above come close. A flow that loops over thousands of list items every day can, so I check the loop count before building anything that runs on a schedule.
Who should own a flow?
At least two people, or a dedicated service account with its own licence. A flow owned only by one person's account can stop when that account is disabled.
Consider an illustrative accounts team whose invoice filing and payment approval flows were built by the office manager under her own account. She leaves, and IT disables her account the same day, as it should. The flows stop without any warning. Two weeks later a supplier calls about an unpaid invoice that was never routed for approval.
The rules that prevent it:
- Make every business flow co-owned by at least two people, or owned by a service account.
- Keep a register with each flow's name, what it does, its owners and the connections it uses.
- Turn on failure notifications so someone hears when a flow stops.
- Put flow ownership on the leaver checklist, before the account is disabled.
Connections break the same way. A flow that connects to SharePoint as one person fails when that person's access changes, even if the flow itself has two owners.
How do you build a flow that doesn't break in the first month?
Write the process on paper before opening Power Automate: what starts it, who decides, what happens on yes, on no, and when nobody answers. Store the data in a SharePoint list rather than inside the flow, so you can see and report on what happened. Then test with the awkward cases, such as a rejected request, a cancelled one, and one edited after it was submitted, because those are what break flows in real use.
When is Power Automate the wrong tool?
When the process needs screens and records people work in all day, Power Apps fits better. When the goal is reporting, use Power BI. When it touches an old system with no connector, desktop flows can drive its screens, but they need Premium.
For those builds, or for documenting the flows you already have, see our Power Platform services. The flows here assume your files already live in SharePoint; if they don't yet, start with the Microsoft 365 migration checklist.