Choosing the wrong flow type is the #1 mistake beginners make in Power Automate — and it's completely avoidable once you understand how triggers work. This lesson teaches you exactly how Automated, Instant, and Scheduled flows differ, and gives you a decision framework you can apply to any real-world scenario before you build a single step.
You've just been handed a new responsibility: every time a customer submits a support ticket through your company's web form, someone needs to log it in a SharePoint list, send an acknowledgment email, and notify the support team in Microsoft Teams. Right now, that someone is you — manually, every single time. It's 47 steps that take 8 minutes each, and tickets come in at all hours.
This is exactly the kind of problem Power Automate was built to solve. But when you open Power Automate for the first time and see the options for creating a flow, you hit an immediate fork in the road: Automated flow, Instant flow, Scheduled flow, and a few others. Which one do you pick? Pick wrong, and your automation either runs at the wrong time, requires manual babysitting, or simply never fires at all.
By the end of this lesson, you'll understand not just what each flow type does, but why it works the way it does — so you can confidently match any business problem to the right flow type before you build a single step.
What you'll learn:
Before we can compare flow types, we need to build a mental model of what a flow is. Think of a flow as an automated worker who sits at a desk waiting for their specific job signal. When they get that signal, they execute a pre-defined sequence of steps. The signal is called a trigger, and the steps that follow are called actions.
Every single flow in Power Automate — regardless of type — follows this same pattern:
Trigger → Action 1 → Action 2 → Action 3 → ...
The trigger is the heartbeat of the flow. It determines when the flow wakes up and starts doing work. The flow types you'll choose between are really just different categories of triggers. When Microsoft says "Automated flow," they're really saying "a flow that wakes up automatically when something happens in a connected system." When they say "Scheduled flow," they mean "a flow that wakes up on a calendar schedule." When they say "Instant flow," they mean "a flow that wakes up when a human manually tells it to."
Once you internalize this — that flow types are fundamentally about what starts the flow — the whole decision becomes much cleaner.
An Automated flow is triggered by an event in a connected service. The flow is always listening in the background, and the moment something specific happens — a file lands in a folder, an email arrives with a certain subject, a row gets added to a database table — the flow fires automatically, without any human intervention.
This is the "if this, then that" model of automation. The trigger is always some version of "when X happens."
Automated flows are the right choice when:
Going back to our support ticket scenario from the introduction: a customer submits a form at 2:17 AM on a Tuesday. You can't predict that. You need a flow that's watching for submissions around the clock. That's an Automated flow, triggered by something like "When a new response is submitted" in Microsoft Forms, or "When an item is created" in a SharePoint list.
Power Automate has hundreds of connectors, each with their own triggers. Here are triggers you'll encounter constantly:
In the Power Automate portal (flow.microsoft.com), click + Create in the left navigation bar. On the creation page, select Automated cloud flow. A dialog will appear asking you to name your flow and choose your trigger. Type a keyword into the trigger search box — try "SharePoint item created" — and select "When an item is created" from the list. Click Create.
You'll land in the flow designer, where your trigger card is already placed. You'll need to connect it to your SharePoint site and list by filling in those fields. Then you click + New step to add your first action — maybe "Send an email" from the Outlook connector.
Tip: When you connect a trigger to a SharePoint list, Power Automate creates a subscription to that list. SharePoint will notify Power Automate every time a new item appears. This is called a webhook relationship, and it's why automated flows respond in near-real-time rather than checking every few minutes.
A Scheduled flow doesn't watch for events. Instead, it runs on a regular cadence — every hour, every morning at 8 AM, every Monday, on the first day of each month. You define the schedule when you build the flow, and Power Automate's internal clock becomes the trigger.
Think of this like setting an alarm. The alarm doesn't care what's happening in the world — it goes off at 7:00 AM no matter what.
Scheduled flows are the right choice when:
Here are some real scenarios that call for Scheduled flows:
Notice the pattern: these tasks are about processing data at a regular interval, not reacting to something unexpected.
In the Power Automate portal, click + Create, then select Scheduled cloud flow. A dialog prompts you to name your flow and configure the schedule immediately: you set the start date and time, and then pick a recurrence — every X minutes, hours, days, weeks, or months.
For example, to create a flow that runs every weekday morning at 7 AM:
Click Create, and you land in the designer with a "Recurrence" trigger card already placed. Every action you add below it will execute on that schedule.
Warning: A common beginner mistake is using a Scheduled flow for something that needs to happen immediately when an event occurs. If a customer submits a support ticket at 2 PM and your flow runs at 6 AM, that customer waits 16 hours for an acknowledgment. Use Automated flows when timing relative to the event matters.
In a Scheduled flow, you almost always follow the Recurrence trigger with a data-fetching action. The most common pattern looks like this:
Recurrence (every day at 6 AM)
→ Get items from SharePoint list (where Status = "Pending")
→ Apply to each (loop through each pending item)
→ Send email to the assigned team member
→ Update item Status to "Notified"
This batch processing pattern — fetch a set of records, loop through them, act on each one — is the signature move of Scheduled flows.
An Instant flow (sometimes called a manual flow or button flow) is triggered by a human, deliberately, in the moment. There's no watching for events, no clock — a person pushes a button, and the flow runs.
This sounds less impressive than the other two types, but instant flows are surprisingly powerful. The key insight is that sometimes the trigger is a human decision, not a system event or a schedule.
Instant flows are the right choice when:
Here are real scenarios:
One underrated feature of Instant flows is the ability to collect user input when the flow is triggered. When building the flow, you can add input fields to the trigger itself — text fields, number fields, date fields, dropdown choices. When the user triggers the flow, they fill in those inputs, and the flow uses those values throughout its actions.
For example, an instant flow for "Send announcement to team" might ask:
The flow then uses those inputs to format a Teams message with appropriate formatting based on urgency.
Instant flows can be run from:
Tip: The SharePoint "For a selected item" trigger is one of the most practical instant flow entry points. You open a SharePoint list, select a row, click the Power Automate button in the toolbar, and choose your flow. The flow receives that specific row's data automatically. This is incredibly useful for record-by-record processing decisions.
In the Power Automate portal, click + Create, then select Instant cloud flow. You'll be asked to name the flow and choose how to trigger it. You'll see options like "Manually trigger a flow," "For a selected item" (SharePoint), "For a selected file" (OneDrive), and others. Select the one matching your scenario, then click Create.
If you choose "Manually trigger a flow," you'll land in the designer with that trigger card. Click on the trigger card itself to expand it and add optional user inputs using + Add an input.
Now let's put this together as a practical decision-making tool. When you encounter a new automation scenario, ask yourself three questions in order:
Question 1: Is the trigger a specific event happening in a system? → If yes: Automated flow → If no: keep going
Question 2: Is the trigger the passage of time (a schedule)? → If yes: Scheduled flow → If no: keep going
Question 3: Is the trigger a human choosing to run the automation right now? → If yes: Instant flow
Let's run a few scenarios through this framework:
| Scenario | Key Question | Flow Type |
|---|---|---|
| Send a Teams alert when a SharePoint item is marked "Urgent" | A status change triggers it | Automated |
| Email each salesperson their weekly pipeline summary every Friday | Runs on a schedule | Scheduled |
| Allow a manager to approve an expense with one click | Human decision triggers it | Instant |
| Sync product prices from an external API every 4 hours | Runs on a schedule | Scheduled |
| Log a support ticket when a form is submitted | Form submission triggers it | Automated |
| Let an admin generate an on-demand status report | Human chooses when | Instant |
Let's build a small but complete Scheduled flow to make these concepts concrete. We'll create a flow that runs every weekday morning and sends you a reminder email if you have any SharePoint tasks due today.
Step 1: Navigate to flow.microsoft.com and sign in with your Microsoft 365 account.
Step 2: Click + Create in the left panel, then select Scheduled cloud flow.
Step 3: In the dialog that appears:
Daily Task ReminderStep 4: You'll see the Recurrence trigger card. Below it, click + New step and search for "Get items." Select Get items from the SharePoint connector.
Step 5: In the Get items card, enter your SharePoint site URL and choose a list that has a "Due Date" column. In the Filter Query field, enter:
DueDate eq 'formatDateTime(utcNow(), 'yyyy-MM-dd')'
This filters the list to only return items where the due date equals today's date. (In a real flow, you'd use the Expression editor to build this properly, but this gives you the pattern to aim for.)
Step 6: Click + New step and search for "Send an email." Select Send an email (V2) from the Office 365 Outlook connector. In the To field, enter your own email address. In the Subject field, type: Tasks due today: and then click into the dynamic content picker to insert the count of items returned.
Step 7: Click Save, then click Test in the upper right. Select Manually to trigger a test run immediately, then click Run flow. Check your email.
Tip: If the flow fails during testing, click the failed run in the flow's run history. Each action card will show a green checkmark (success) or red X (failure). Click the failed card to see the exact error message — this is how you debug almost every flow problem.
Mistake 1: Using Scheduled flow when Automated would work better "I'll just check every 15 minutes for new form submissions." This works, but it means you're potentially waiting up to 15 minutes after a trigger event before the flow acts. Automated flows using proper event triggers respond in seconds. Always use Automated flows when the connector supports event-based triggers.
Mistake 2: Using Automated flow for batch processing If you use "When an item is created" to process new orders, and 500 orders come in simultaneously, your flow fires 500 separate times — potentially overwhelming downstream systems or hitting API rate limits. Batch scenarios (process all pending orders each night) belong in Scheduled flows.
Mistake 3: Forgetting that Instant flows require human action Beginners sometimes build an Instant flow and then wonder why it's not running automatically. Instant flows only run when someone triggers them. If your process needs to happen without human intervention, you need Automated or Scheduled.
Mistake 4: Not testing with real data Power Automate's test mode lets you use data from a previous run ("Use data from a previous run") rather than triggering a real event. This is convenient, but it can mask problems with live data. Always do at least one end-to-end test with real, live conditions before deploying a production flow.
Mistake 5: Ignoring time zones in Scheduled flows By default, Power Automate's Recurrence trigger uses UTC time. If you set a flow to run at 8:00 AM and you're in New York (UTC-5), it will actually fire at 3:00 AM your time. Use the Start time field in the Recurrence trigger and specify your local time, or use the convertTimeZone function in your actions to handle this properly.
Let's anchor what you've learned. Every Power Automate flow follows the same Trigger → Actions structure. The three main cloud flow types differ only in how the trigger works:
The most important skill you've built here is the diagnostic habit: before building anything, ask "what starts this process?" The answer tells you exactly which flow type to reach for.
Where to go from here:
You now have the mental framework to look at any business process and identify which Power Automate flow type belongs there. That's not a small thing — it's the foundation everything else is built on.