In This Article
If your business runs on Microsoft 365, you are already paying for one of the most useful automation tools on the market and probably not using it. Power Automate is bundled into most business plans alongside Outlook, Excel and Teams, and in a lot of companies it sits there untouched because nobody knows where to start.
That's a shame, because the first few flows are genuinely easy. You don't need a developer, you don't need a budget, and you don't need to understand APIs. A flow is just a recipe: something happens (the trigger), the flow checks a condition if you need one, and then it does something (the action). That's the whole model.
Here are five Power Automate flows most small businesses can build in a spare afternoon this week. Each one removes a chore that someone in your business is currently doing over and over without thinking about it.
1.Save Email Attachments to SharePoint Automatically
Think about how invoices, statements and signed documents actually arrive in your business. They come in as email attachments, and someone opens the email, downloads the file, renames it, and drags it into the right folder. Multiply that by every supplier and every month, and you've got a job nobody was ever hired to do.
The flow is about as simple as they come. Trigger: a new email arrives in a particular mailbox, say accounts@yourcompany. Condition: it has an attachment, and optionally the sender or subject matches what you're looking for. Action: save the attachment to a SharePoint or OneDrive folder, with the date and sender added to the filename so it's findable later.
Once it's running, the filing just happens. Nothing gets forgotten because someone was on holiday, and when your accountant asks for the March invoices, they're already sitting in the March folder. It's a small win each time, but it's a win that repeats dozens of times a week, and it's the best possible first flow because you'll see it working within minutes.
2.Invoice and Leave Approvals Through Teams
Most small businesses run approvals by forwarding emails. An invoice needs sign-off, so it gets sent to the owner, who is busy, so it sits. Three days later someone chases it, the original email has been buried, and the supplier is now chasing too. Leave requests follow the same pattern with a spreadsheet at the end of it.
Power Automate has a built-in approvals feature that tidies this up properly. The trigger can be whatever suits you: an email arriving in an invoices mailbox, a form being submitted, or a file being dropped into a folder. The flow then sends an approval card to the right person in Teams, with the details and the document attached. They tap Approve or Reject on their phone, add a comment if they want, and the flow records the outcome, files the document and notifies whoever asked.
The point isn't just speed. Every approval now has a timestamp, a named approver and an audit trail, which matters the day a supplier disputes a payment or an employee questions their leave balance. Chasing sign-offs quietly disappears as a task.
3.Microsoft Forms to Excel to a Teams Alert
This one is a chain of three tools you already have. Anywhere your business collects information, enquiries from your website, customer feedback, site visit reports, new starter details, a Microsoft Form can capture it. The problem is what happens next: someone has to notice the response, copy it somewhere useful and tell the right person about it.
The flow does all three steps at once. Trigger: a new form response is submitted. Actions: add a row to an Excel table with every answer in its own column, then post a message to a Teams channel so the right people know immediately. If some responses matter more than others, add a condition in the middle, so an enquiry marked "urgent" pings a named person directly rather than just the channel.
For anyone who currently transcribes paper forms or copies answers out of notification emails, this flow removes the entire job. The spreadsheet fills itself, nobody re-types anything, and the response to a new enquiry starts in minutes rather than whenever someone next checks the inbox. It's also the flow that tends to spark ideas, because once people see a form feeding a spreadsheet automatically, they start spotting other places the same pattern fits.
4.Scheduled Reminders That Never Forget
Not every flow needs a trigger event. Some of the most useful ones just run on a schedule, and they exist to do the remembering your team currently does with sticky notes and recurring guilt.
Every business has these rhythms. The sales figures need pulling every Monday. VAT prep starts at the same point each quarter. Timesheets are due Friday. Someone is supposed to check the stock report on the first of the month. None of it is difficult, but all of it depends on a person remembering, and the reminder usually lives in one person's head.
A scheduled flow uses a recurrence trigger: every Monday at 8am, or the first working day of the month. The action can be a simple Teams message to a channel, an email with a checklist, or something slightly smarter, like opening the Excel file it's reminding you about and including the headline numbers in the message so the update is half-written before anyone opens a laptop.
These flows save minutes rather than hours, but that undersells them. What they really remove is the cost of forgetting: the missed report, the late submission, the scramble that follows. Boring, reliable, worth ten of the clever ones.
5.Keep Customer Records in Sync Between Systems
Here's a pattern almost every small business will recognise. A new customer or order exists in more than one place: the order confirmation in Outlook, the tracking spreadsheet in Excel, maybe a CRM like Dynamics or HubSpot. Someone updates one, means to update the others, and within a few months no two systems agree. Then someone spends a painful afternoon reconciling them.
A sync flow attacks the cause instead of the symptom. Trigger: a new record appears in the system where it's born first, an order email arriving, a row added to a table, a contact created in the CRM. Actions: create or update the matching record everywhere else it needs to exist. Power Automate has ready-made connectors for hundreds of systems, so this is mostly a matter of mapping which field goes where, not writing code.
Start narrow. Pick one record type, new customers, say, and one direction of travel, and get that solid before adding more. The time saved on data entry is real, but the bigger prize is trust: when every system agrees, people stop double-checking before every customer call, and the quiet drag of "which spreadsheet is right?" goes away.
Before You Build Anything
Write the process down in plain English before you open Power Automate: when X happens, check Y, do Z. If you can't describe it that clearly, the flow will fight you.
Build one flow, run it supervised for a week or two, and only then start the next. A single reliable flow builds more confidence in automation than five half-tested ones, and the failure emails Power Automate sends when something breaks are only useful if someone is actually reading them.
Start with the attachment flow. It's the quickest to build, the easiest to test, and the moment it files its first invoice you'll understand the tool well enough to attempt the rest.
Where to Go From Here
These five flows are the shallow end, and the shallow end is genuinely valuable. But Power Automate reaches much further: multi-step workflows across departments, AI-driven document handling, integrations with your accounting and eCommerce systems.
If you'd rather have someone design, build and maintain that for you, that's what Fulcrum Three does. We build Power Platform automation for UK small businesses, from first flows to full workflow systems, and we look after them once they're live.
See where automation would give your business the most leverage.
Book a Free Operations Audit →