How to Create a Scheduled Flow in Microsoft Power Automate Easily 2026

From My flows, select New flow, or from the Create page, you're offered several starting points: Automated cloud flow, Instant cloud flow, Scheduled cloud flow, Describe it to design it (Copilot), Desktop flow, and Process mining. Scheduled cloud flow is built specifically for time-based automation, its subtitle reads "You choose when and how often it runs", which separates it from Automated (triggered by an event) or Instant (triggered manually).

If you have Copilot access, you can also describe the schedule in plain language instead of building it screen by screen; this guide follows the manual path. Community templates below the blank-start options, things like "Schedule a reply to send at the perfect time", are worth a scan in case one already does most of what you need.

Naming your flow and picking Scheduled cloud flow asks for two things upfront: a Starting date and time, and how often to Repeat every (an interval in minutes, hours, days, weeks, or months). Confirming these drops you into the designer canvas with a single Recurrence block sitting at the top.

For anything more specific than a plain interval, a particular time of day, particular days of the week, open the Recurrence trigger and select Show advanced options; that's where Time zone, At these hours, At these minutes, and, for a weekly schedule, On these days actually live. Everything else in the flow builds downward from this block using the plus icon underneath it.

Click the plus icon below Recurrence to add your first action. In the example flow, that's Get file metadata, connected to OneDrive for Business; the parameters panel on the left lets you browse folders to pick the exact file the flow should check each run.

This is the pattern for every action you add: configure its connection, point it at the right file or data source, and let it feed into whatever comes next, whether that's generating a report, sending an email, or writing to another system. Worth noting for licensing: most file and email connectors are standard, but if an action you add is a premium connector, the flow's owner will need a Premium or Process license to keep it running.

Power Automate saves flows under the name given at creation, "Weekly Project Report" in this walkthrough, and that name shows up in My flows, in run history, and in any notifications tied to it. Pick something that describes what the flow does and how often, not a generic placeholder; you'll be scanning a list of flow names later when something needs troubleshooting, and a vague name won't help.

Once saved, open the flow's details page to see its Status (On), Type (Scheduled), owner, connections, and a 28-day run history table listing every execution with its start time, duration, and status. In the example, a manual test run completed in a few seconds and shows "Test succeeded" in the Status column, confirmation the flow is wired correctly before it runs unattended on its own schedule. This page is also where a failure shows up early: a red "Failed" status means fixing the flow now, not waiting for someone to notice a report never arrived.

After the first successful run, check the run history periodically rather than assuming a scheduled flow will quietly work forever; connections can expire, source files can move, and permissions can change. The same details page used to confirm the test run is where every future execution logs its status, so bookmarking it, or checking My flows regularly, is enough to catch problems before they turn into a pattern of missed reports.