Most teams I talk to already pay for Power Automate and have never opened it. That's a shame, because it's one of the fastest ways to take repetitive work off people's plates. In this guide we'll build one real, useful automation together, and I'll explain every click along the way.
When I taught design at CSU Monterey Bay, I noticed something: people learn a new tool fastest when they build one real thing with it, not when they read about every feature. So that's what we'll do. By the end you'll have a working flow, and more importantly, you'll understand how flows think, which makes every future automation easier.
Who this is for: anyone comfortable with Outlook, Teams and Excel. No coding, no IT background. If you can fill out a form, you can build this.
What Power Automate actually does
Power Automate is Microsoft's tool for connecting apps and letting routine work run on its own. Think of it as a very reliable assistant who follows instructions exactly, at any hour, without getting bored.
Every automation is called a flow, and every flow follows the same pattern: when this happens, do these things.
One automation, from start to finish.
The event that starts it, like "a form was submitted" or "every Monday at 9 a.m."
Something the flow does, like "send an email" or "add a row to Excel."
The bridge to an app: Outlook, Teams, SharePoint, Forms and hundreds more.
Information passed between steps, like the person's name from the form.
A log of every time the flow ran, and whether each step worked.
Three kinds of flows
Automated
Runs when something happens: a new email, form response or file. This is what we'll build.
Instant
Runs when you press a button, on your phone or in Teams.
Scheduled
Runs on a timer, like a reminder every Friday or a report on the 1st.
Before you start
Tick these off. It takes two minutes and saves twenty.
The flow we'll build
Here's the situation it solves. Requests come in through email, chat and hallway conversations. Someone has to notice them, copy the details somewhere, tell the team, and reply to the person. It's not hard, but it's constant, and things slip through the cracks.
⏳ Before
- Requests arrive in five different places
- Someone copies details by hand
- The team hears about it late, or never
- The person waits, wondering if anyone saw it
✨ After
- Every request comes through one simple form
- The team sees it in Teams within a minute
- The person gets an instant confirmation
- Nobody copies anything by hand
Step by step
Create the form
Go to forms.office.com and create a new form called Team request. Add three questions: Your name (text), Your email (text), and What do you need? (long answer). Make all three required.
👀 Tip: resist adding ten questions. Short forms get filled out; long ones get emailed around.
Start a new automated flow
Open make.powerautomate.com and sign in with the same work account. Choose Create, then Automated cloud flow. Name it clearly, for example Team request: alert and confirm. Future you will thank present you.
Choose the trigger
In the trigger search box, type Forms and choose When a new response is submitted. Select Create, then pick your Team request form from the Form Id dropdown.
👀 What you should see: one card at the top of the canvas with your form selected.
Get the answers
This is the step most beginners miss. The trigger only says "a response arrived"; it doesn't include the answers. Add a new step, search Forms again, and choose Get response details. Pick the same form, then click into Response Id and choose the Response Id from the dynamic content list.
Post it in Teams
Add Post message in a chat or channel from Microsoft Teams. Set Post as to Flow bot, Post in to Channel, then pick your team and channel. In the message box, mix text with dynamic content:
📥 New request from Your name: What do you need?
Send the confirmation
Add Send an email (V2) from Office 365 Outlook. Put the Your email answer in the To field. For the subject, try "We got your request." In the body, write it the way you'd actually talk:
Hi Your name, thanks for reaching out. We received your request and someone will follow up within one business day.
Rename every step
Click the title of each card and rename it: Get request answers, Alert the team, Confirm with requester. It takes a minute and makes the flow readable by anyone.
Save and test
Select Save, then Test → Manually. Open your form in another tab and submit a test response. Back in Power Automate, watch each step get a green check.
🎉 That's it. Check Teams and your inbox. You just built your first automation.
Labels change. Microsoft updates the Power Automate designer regularly, so buttons may look slightly different from these descriptions. The trigger and action names are the reliable part; search for those.
Make it smarter (when you're ready)
Once your team is using the basic version for a week or two, here are three upgrades worth adding:
Route urgent requests
Add a Condition step: if What do you need? contains "urgent," post to a different channel or @mention a lead.
Add an approval
Use Start and wait for an approval so a manager can approve or reject right inside Teams, then email the result automatically.
Keep a record
Add Create item (SharePoint) to save every request in a list you can sort, filter and report on.
Add AI carefully
Some plans include AI actions that can summarize or categorize text. Start with one simple use, and keep a person reviewing the results.
Troubleshooting
Every flow builder hits these at some point. Here's what usually fixes them.
My flow didn't run when I submitted the form.
First, make sure the flow is turned on and that the trigger points to the right form. Then give it a minute; triggers aren't always instant. Finally, open the flow's run history to see if it started and failed, or never started at all.
I can't find the form answers in the dynamic content list.
You're probably missing the Get response details step, or it's placed before the step you're editing. Add it right after the trigger and choose the Response Id from the trigger.
The confirmation email went to the wrong person.
Check the To field in the email step. It should use the 'Your email' answer from Get response details, not your own email or the form owner.
A step has a red error.
Open the failed run and click the red step. The error message usually names the problem: a missing permission, an empty field, or a channel the flow can't post to. Fix it, save, and use Resubmit to re-run it.
The flow stopped working after a colleague left.
Flows run under the account of the person who built them. For anything important, add a co-owner (in the flow's details page) so it keeps running when people change roles.
Mistakes I see most often
If the manual process is unclear, the automation will be too, just faster. Write the steps down first and remove the ones nobody needs.
Show the flow to the people who'll use it before you launch. They'll catch things you didn't think of, and they'll actually want to use it.
Look at the run history once a week for the first month. Small issues are easy to fix early.
One working flow that people use beats five half-finished ones.
Where to go next
Give your new flow two weeks of real use, then ask the team one question: what's still annoying? The answer is usually your next automation. For more ideas, read 5 workflows every small team should automate, and before you add AI to anything, take a look at writing an AI policy your team will actually read.
And if you get stuck, send me a note. Seriously. Helping people get unstuck is my favorite part of this work.