Five Power Automate patterns every business should steal

Power Automate (Microsoft's workflow tool, included with most Microsoft 365 plans) can look intimidating, but the truth is that the automations most businesses actually need come down to a handful of repeating shapes. Learn these five and you can adapt them to dozens of real situations. This guide is for anyone comfortable clicking around Microsoft 365 who wants to automate the boring, error-prone stuff without writing code. For each pattern you'll get the trigger that kicks it off, the key actions in the middle, and the one gotcha that trips people up. Build them in the Power Automate portal at https://make.powerautomate.com.

Before you start

• A Microsoft 365 account that includes Power Automate (most business plans do).
• Permission to the data each flow touches: the SharePoint list, the Teams channel, the form.
• A test version of any list or channel so you're not experimenting on live data.
• Knowing that flows live in an environment; for most SMBs the default environment is fine.

Pattern 1: An approval that routes a request and records the decision

Use this for purchase requests, time off, document sign-off, anything that needs a yes or no from a specific person.

• Trigger: A new item is created in a SharePoint list (for example a "Requests" list), or a new Microsoft Forms response.
• Key actions: Add Start and wait for an approval (choose the "Approve/Reject, first to respond" type), set the approver, and write a clear title and details. After it, add a Condition that checks the Outcome. On the Approve branch and the Reject branch, use Update item to write the decision, the approver, and the date back to the SharePoint list.
• Gotcha: "Start and wait for an approval" pauses the flow until someone responds, with no timeout by default. If the approver is on vacation, the request sits forever. Add a parallel branch or a reminder so requests don't stall silently.

Pattern 2: A scheduled "send this every Monday"

Use this for a weekly report, a recurring reminder, or any "every X" task a person currently remembers to do by hand.

• Trigger: Recurrence (a scheduled cloud flow). Set it to, say, every week on Monday at 8:00 AM.
• Key actions: Gather what you need (for example Get items from a SharePoint list, or run an Office Script to build a summary), then Send an email (V2) or Post message in a chat or channel with the result.
• Gotcha: The Recurrence trigger uses a specific time zone, and if you don't set it, your "8:00 AM" may fire at the wrong hour. Open the Recurrence trigger's advanced options and set the Time zone explicitly. Also watch daylight-saving shifts.

Pattern 3: An escalation or reminder for overdue items

Use this to chase anything with a due date: open tickets, unsigned documents, invoices, tasks past deadline.

• Trigger: Recurrence, run daily.
• Key actions: Get items from the SharePoint list with a filter for items where the due date has passed and status is still open. Use an Apply to each loop over the results, and inside it send a reminder email or Teams message to the owner. For escalation, add a Condition on how overdue the item is and notify a manager past a threshold.
• Gotcha: Use the list's Filter Query (OData) to pull only overdue items rather than retrieving everything and filtering in the flow. Pulling the whole list and looping over it is slow and can hit limits as your data grows.

Pattern 4: Form-to-record intake

Use this to turn a Microsoft Forms submission (a request, a sign-up, a support intake) into a tracked record automatically.

• Trigger: When a new response is submitted (Microsoft Forms).
• Key actions: Add Get response details right after the trigger to pull the answers, then Create item in a SharePoint list (or Post message in a Teams channel) mapping each form answer to a column.
• Gotcha: People forget the Get response details step. The trigger alone only gives you a response ID, not the actual answers. Without that action, your created records come out blank.

Pattern 5: An alert that posts to Teams when something happens

Use this so the right people see important events without watching a list or inbox.

• Trigger: Depends on the event. When an item is created or modified (SharePoint), When a new email arrives (Outlook), or another connector's event.
• Key actions: Optionally add a Condition so you only alert on what matters (for example only high-priority items), then Post message in a chat or channel to the relevant Teams channel with the key details and a link.
• Gotcha: The "item is created or modified" trigger fires on every edit, including the flow's own updates, which can cause loops or alert spam. Add a condition to alert only on the state you care about, and be careful not to have the flow modify the same item it watches.

Test before you trust

1. For each flow, click Test in the top right of the editor and run it manually (or trigger the real event in your test list).
2. Check the run history: every step should show a green check. Click into any step to see exactly what data passed through.
3. Run the unhappy path too: reject the approval, submit a blank form, create an overdue item, and confirm the flow behaves.

What to do next

Start with the one pattern that maps to your most annoying manual task, build it against test data, then point it at the real thing. As you get comfortable, you'll see these same five shapes everywhere. When your automations start touching real money, compliance, or customer data, it's worth having them designed for reliability and error handling rather than left to break quietly. We build and maintain these workflows for businesses every week, and we're happy to help you turn your worst manual process into a flow you can trust.