How to Use Power Automate (Flows, Triggers and Actions)

Power Automate is Microsoft's tool for making apps do jobs for you: save every email attachment to a folder, send a reminder every month, post to Teams when a form is submitted. It sounds technical, but the core idea is a single sentence: when this happens, do that. Here's how to build your first flow, the vocabulary that makes the screens make sense and how to avoid automations that quietly do the wrong thing.

The two words that matter: trigger and action

Microsoft defines a cloud flow as one that performs one or more tasks automatically when an event triggers it. A trigger is the event that starts the flow. Actions are what the flow does afterwards. 'When a form is submitted' is a trigger. 'Send me an email' is an action. Everything else is detail.

Way 1: describe the flow to Copilot

1. Sign in to Power Automate and make sure Home is selected.
2. In the Create your automation with Copilot field, describe the flow in plain language, as specifically as you can.
3. Select Generate. Copilot proposes a trigger and actions.
4. Select Keep it and continue.
5. Check your connected apps and services. A green checkmark means the connection is valid; some will ask you to sign in.
6. Select Create flow, then Save.

Microsoft adds a reminder worth taking seriously: make sure a human reviews AI-generated content to verify it's accurate and appropriate. Read what Copilot built before you switch it on.

Way 2: build it from scratch

Microsoft's tutorial builds a scheduled flow that sends a monthly email. The steps show you the pattern for any flow.

1. Select Create in the left menu.
2. Under Start from blank, choose Scheduled cloud flow.
3. Enter a flow name, set the starting date and time, and choose how often it repeats, such as every month.
4. Select Create. The designer opens with a Recurrence trigger.
5. Add an action: select the plus below the trigger, search for Send an email (V2) and choose the Microsoft 365 Outlook version.
6. Fill in the To, Subject and Body fields.
7. Select Save in the command bar. A green message confirms it's saved.

You can send to more than one person by entering several addresses in the To field. And you can use either the new designer or the classic designer, because Microsoft says the steps are similar in both.

Test before you trust it

Microsoft recommends testing every flow after you save it. Run it manually and check what happened: did the email arrive, did it go to the right person, did it say the right thing? A flow that sends the wrong email on a schedule is worse than no flow. Start with yourself as the only recipient, and widen it only when the result is right.

Ideas for a first flow

Idea	Trigger	Action
Monthly reminder	Recurrence (once a month)	Send an email
New form response	A response is submitted	Post a message to your team
Important email	An email arrives from a key client	Add the details to a task list
Weekly summary	Recurrence (once a week)	Send yourself a checklist

Keep your automations safe

• Start with low-risk jobs such as reminders, not anything that deletes or sends to customers.
• Name flows clearly so you know what each one does six months later.
• Check connections periodically. A connection that has expired will stop a flow silently.
• Limit who can edit flows that touch company data.
• Review your flows every few months and switch off the ones you no longer need.

Is it worth the effort?

If you do the same small task more than a couple of times a week, it's worth automating. If you do it once a month and it takes two minutes, probably not. My guide to Microsoft tools for small businesses shows where Power Automate fits, and Power BI data governance covers the sensible controls to put around data your automations touch.

A worked example: a monthly reminder

Say you send clients a progress update on the first of each month and always forget. Create a scheduled cloud flow called 'Monthly reminder', set it to start on the first and repeat every month, add the Send an email action and send the message to yourself with a subject line like 'Time to send the client updates'. Save it, run a test and check it arrives. It takes ten minutes and it'll never forget, and you won't have to think about it again. That's the whole spirit of Power Automate: take a small, dull task off your mind.

Connections are where flows break

Every app a flow touches needs a connection, and connections can expire or lose permission. If a flow that used to work suddenly doesn't, check the connections first. Microsoft shows a green checkmark when a connection is valid, and some will ask you to sign in again. Make it a habit to open your important flows every few months and confirm the checkmarks are green.

Before you automate something

1. Write the task out as 'when this happens, do that'.
2. Do it manually a few times so you know what a good result looks like.
3. Build the flow with yourself as the only recipient.
4. Test with real examples, including awkward ones.
5. Only then point it at real customers or colleagues.

My verdict

Start with a template or a plain-language description, and read what's been generated. Pick one boring repeating task, build a flow for it, test with yourself as the recipient and review it every few months. Small, safe automations beat clever ones nobody understands, and you'll trust them more.

Frequently asked questions

How do I use Power Automate?

Sign in, choose Create, pick a template or start from blank or describe the flow to Copilot. Add a trigger and actions, connect your apps, save and test.

What is a trigger in Power Automate?

An event that starts a cloud flow, such as a schedule or a new email.

What is an action?

What the flow does after the trigger, such as sending an email.

How do I know a connection is working?

A green checkmark on the connection indicates that it's valid. Some connections ask you to sign in.

Should I test a flow?

Yes. Microsoft recommends testing after you create it, and reviewing any AI-generated content.