Phase 5 · Power Automate · Level 1 · Foundations
What automation actually is
By the end, you'll be able to…
- Explain a trigger, an action and a connector in plain English
- Judge whether a task is worth automating using frequency, time and error-proneness
- Tell a good first automation candidate from a poor one
Why it matters
Before you build anything, you need a clear head about what automation is and, just as important, when it's a waste of effort. Most disappointing automations fail not because the tool is weak but because someone automated the wrong task. This lesson gives you the three-word vocabulary the rest of the phase relies on, and a simple test for whether a job is worth the build.
Automation is just "when this happens, do that"
Strip away the jargon and every automated flow is one sentence: when something happens, do something in response. When an email with an invoice arrives, save the attachment to a folder. When a form is submitted, post a message in a team channel. When a new row is added to a spreadsheet, send an approval request. You already think this way; you just do the "do that" part by hand, dozens of times a week.
Power Automate is Microsoft's tool for writing those sentences down so the computer runs them for you. It sits across the Microsoft 365 tools most workplaces already have (Outlook, OneDrive, SharePoint, Teams, Excel) and stitches them together. You don't write code. You describe the sentence, choose the pieces from menus, and it runs quietly in the background.
Three words carry the whole idea, so it's worth pinning them down now.
Trigger: the "when"
A trigger is the event that starts a flow. It's the "when this happens" half of the sentence. When an email arrives. When a file is created. When a form is submitted. When it's 8am. A flow has exactly one trigger, and until that event happens, the flow sits and waits; it costs you nothing while it waits. Some triggers watch for events (a new email); others run on a schedule (every morning at eight).
Action: the "do that"
An action is a step the flow carries out once it's triggered. Save the attachment. Send a message. Create a row. Ask a person to approve. A flow can have one action or twenty, running in order, one after another. The trigger fires once; the actions then do the work.
Connector: the bridge to an app
A connector is the bridge between Power Automate and a particular app or service. There's an Outlook connector, a OneDrive connector, a Teams connector, an Excel connector, and hundreds more. Each connector offers its own triggers and actions: the Outlook connector gives you the "when a new email arrives" trigger and the "send an email" action; the OneDrive connector gives you "create file". When you build a flow you're really choosing connectors and then picking a trigger and actions from each. The full set is the connector directory, and we'll tour it in the next lesson.
So the whole of Power Automate reduces to: pick a trigger from a connector, then add actions from connectors. That's it. Everything else is detail.
When automation is worth it, and when it isn't
The tool will happily let you automate almost anything. That doesn't mean you should. The honest test is three factors multiplied together: frequency × time-per-instance × error-proneness.
- Frequency: how often does the task happen? Once a quarter, or forty times a day?
- Time per instance: how long does each one take you by hand? Ten seconds, or ten minutes?
- Error-proneness: how easily does a human get it wrong or forget it entirely? Renaming a file is hard to botch; remembering to copy every invoice into the right folder every single time is very easy to let slip.
A task scores high when it's frequent, fiddly, and easy to fluff. That's the sweet spot. A task that's rare, quick, or basically foolproof rarely earns back the time you'll spend building and maintaining the flow. Automating a five-minute job you do once a year is a hobby, not a saving.
There's a fourth, quieter factor: stability. Automating a process that changes every month means rebuilding the flow every month. Automate the settled, boring, repetitive things; that's where automation shines.
When I receive an email in Outlook with an attachment, save each attachment to the "Invoices" folder in my OneDrive, then post a message in the Finance channel in Teams saying a new invoice has arrived.
Why this works: Power Automate's Copilot builds a draft flow from a plain sentence. A good description names the trigger event, the apps, and the actions: the same three ideas as trigger, connector and action. Naming all three gives Copilot a target it can actually hit.
Notice how that sentence contains a trigger (an email arrives with an attachment), three connectors (Outlook, OneDrive, Teams), and clear actions (save the file, post a message). You didn't need technical words; you needed to be specific about the when and the do.
Good and poor candidates at Fernway
Let's make it concrete with the Fernway Group, our sample company. Dan in Finance is drowning in expense receipts emailed to him; Maya keeps forgetting to file new-starter paperwork; Priya wants customers to actually hear back when they submit feedback. Which of these is worth a flow?
When a new response is submitted to the Fernway customer-feedback form, add a row to the "Feedback log" spreadsheet with the date and message, and send the customer an automatic acknowledgement email.
Why this works: This is frequent (feedback arrives most days), fiddly by hand (log it, notify someone, acknowledge the customer), and very easy to drop, exactly the tasks that pay back a build. It also directly fixes the 'customers never hear back' problem in Fernway's feedback brief.
When someone posts "coffee machine" in the office chat, send Maya a reminder to call the leasing company.
Why this works: Reminding Maya the coffee machine is broken is easy to automate, but the task is trivial and rare enough that a flow adds clutter for almost no saving. High-ish frequency alone isn't enough; the time saved per run is near zero.
When Tom flags the Harlow renewal, automatically decide whether to approve the discount and reply to the customer.
Why this works: Approving a discount on a big renewal happens a few times a year and depends on human judgement about the customer relationship. Low frequency and high judgement mean a flow adds fragile machinery to something a person should just decide. Automating a reminder to review it might help; automating the decision does not.
The pattern holds: automate the repetitive, rules-based, easy-to-forget work, and leave the rare, judgement-heavy decisions to people. A flow is brilliant at "do this exact thing every time"; it is hopeless at "use your judgement".
Try it now
Common mistakes
- Automating the wrong task. The commonest failure isn't a broken flow; it's a working flow that saved a job not worth saving. Run the frequency × time × error-proneness check before you build.
- Automating an unstable process. If the steps change every few weeks, you'll spend more time rebuilding the flow than you ever saved. Wait until a process settles before you automate it.
- Confusing "can" with "should". The tool will let you automate a once-a-year task. That it's possible doesn't make it worthwhile.
- Over-trusting a flow you never watch. A silent automation can quietly do the wrong thing for weeks (filing invoices in the wrong folder, emailing the wrong list), and because it's silent, nobody notices. Automation removes the doing, not the responsibility. Anything a flow does still has your name on it, so plan from the start to check its output, especially in its first weeks.
Keeping current
Power Automate's connectors, triggers and actions grow constantly, but the core idea (trigger, action, connector) is durable and won't change. For the current picture of what the product can do, see Microsoft Learn's Power Automate documentation. Accurate as of 13 July 2026.