You already know which flow you run every day. You also know the route: open a browser tab, wait for make.powerautomate.com to load, click My flows, scroll, click Run. Three minutes of setup kills that for good, because the flow can live in the Teams rail you already have open.
How to do it
- In Teams, click the Apps icon in the left rail and search for Workflows. That is the Power Automate app, renamed. Same flows, same run history, fewer syllables.
- Open it, then right-click its icon in the rail and choose Pin. It stays there across restarts and across devices signed in with the same account.
- Make sure the flow you want is an instant flow, meaning its trigger is Manually trigger a flow. Scheduled and automated flows will appear in the app, but they have no Run button - there is nothing for you to press.
- Open the pinned app, go to your flow list, and hit Run. If the flow takes inputs, add them as trigger parameters on the manual trigger and Teams renders them as a small form.
- Optional, and the part people miss: in a channel, click + to add a tab and pick the Workflows app to surface the flow for the whole team. One flow, one visible button, no explaining the URL in chat again.
Why it works
Nothing changes about the flow itself. Teams is just another client hitting the same manual trigger endpoint that the mobile app and the web portal hit. That is why the requirement is the trigger type, not the app: the Workflows app can only show you a Run button if the flow was built with a trigger that waits for a human to press one.
Which also means the fix for "my flow isn't showing a Run button" is almost never in Teams. It is in the trigger.
When not to use it
If the flow needs a file, a selected row, or a specific record to work against, running it from a generic sidebar button gives it no context. Those belong on the thing they act on - a button in Excel, a flow launched from a SharePoint item, or an automated trigger that already knows what changed.
The same trigger logic makes the flow runnable from your pocket, which is a separate three-minute win worth taking. And if the words "manual trigger" are still doing a lot of unexplained work, triggers aren't events, they're a question your flow keeps asking.