Last reviewed: September 15, 2026

A trigger is the event that starts a cloud flow. Every flow has exactly one trigger, and choosing the right kind, automated, instant or scheduled, decides how and when your automation runs.

TL;DR: Automated flows start when an event happens (a new email, a new SharePoint item). Instant flows start on demand, you tap a button or run them from an app. Scheduled flows start on a clock, at set times or intervals. Pick the trigger that matches what makes the work need to happen.

The three cloud flow trigger types

Trigger type	Starts when	Example
Automated	An event occurs	New SharePoint item arrives
Instant (manual)	You run it on demand	Tap a button to start it
Scheduled	A clock/recurrence fires	Send a daily report

Automated triggers

🔸 Automated flows are initiated automatically based on an event or condition, for example “When a new email arrives” or “When an item is created”.

🔸 Most connectors expose prebuilt triggers (Outlook, SharePoint, Dataverse, Teams). This is the workhorse pattern: something changes, and the flow reacts.

🔸 Use this when the work should happen the moment an event occurs, with no human kicking it off.

Instant (manual) triggers

🔸 Instant flows are started on demand, with a tap of a button on your mobile device, a button in an app, or the “manually trigger a flow” trigger.

🔸 They’re good for human-in-the-loop actions: a user decides now is the time, for example to start an approval, send a reminder or trigger a task.

🔸 Instant flows can also be called from a Power App or another flow, passing in parameters.

Scheduled triggers

🔸 Scheduled flows run on a schedule, at a specific time, or on a repeating interval such as every hour, daily or weekly.

🔸 Use these for recurring, time-based work: nightly data syncs, daily digest emails, periodic clean-up jobs.

🔸 The schedule is defined on the Recurrence trigger (interval plus frequency, with an optional start time).

Comparison at a glance

	Automated	Instant	Scheduled
Typical triggers	When a new email arrives (V3), When an item is created, When a row is added, modified or deleted	Manually trigger a flow, For a selected item, Power Apps (V2)	Recurrence
Data from the trigger	Details of the event (the mail, the item, the row)	Inputs you define or the selected item	None, fetch the data yourself
Connections	The connections saved in the flow	Manual trigger needs the connection of the person who starts it	Can run on the flow maker’s connections
Typical use	Route incoming mail, start an approval on a new item	Reminder, approval from a list or app	Daily report, weekly clean-up, nightly sync

How to choose

Ask one question: what starts the work?

🔸 “When X happens, do Y” points to Automated.

🔸 “When I (or a user) decide, do Y” points to Instant.

🔸 “Every day/hour, do Y” points to Scheduled.

🔸 Beyond cloud flows, desktop flows (RPA) can also be started manually, by a cloud flow, or on a schedule; see the flow-types guide.

⚠️ Watch out

🔸 A flow has exactly one trigger. If you need several entry points, use child flows or an instant flow that other flows call.

🔸 Automated triggers can fire a lot. High-volume event sources mean many runs, so add trigger conditions/filters so the flow only runs when it truly should. See #PowerPlatformTip 11.

🔸 Scheduled isn’t real-time. A recurrence that runs hourly can lag events by up to an hour; use an automated trigger when you need immediacy.

🔸 A scheduled flow carries no data. The Recurrence trigger only says “it is time”, so add a Get items or List rows action with a filter, for example on a status column or a modified date.

🔸 Shared instant flows run on the connection of the person who starts them. If a flow works for the owner but not for a colleague, check that colleague’s connections and license first.

🔸 Expressions in a trigger, such as utcNow(), are calculated when the flow is saved, not at every run. Don’t use them to build a moving date window in the trigger.

🔸 Triggers don’t fire for files in SharePoint subfolders (for example When a file is created or modified). Create additional flows if you need subfolders covered.

Licensing and run context

🔸 Whether you need a Premium license depends on the connectors in the flow. A flow without premium connectors can run on a Microsoft 365 license.

🔸 The trigger type decides whose license counts. Automated and scheduled flows run in the context of the flow owner, so only the owner needs Premium when a premium connector is used. Instant flows run in the context of the invoking user, so every user who runs them needs Premium, unless the flow has a Process license.

🔸 Source: Microsoft Learn, Power Automate licensing FAQ. Details and exceptions for Power Apps and Dynamics 365 context are in Types of Power Automate licenses.

🛠️ FAQ

What’s the difference between automated and instant? Automated flows start by themselves when an event occurs; instant flows start because a person runs them (button, app, manual trigger).

Which trigger sends a daily report? A scheduled (Recurrence) trigger set to run once a day.

Can I change the type of an existing flow? There is no type switch. You delete the trigger and add one of the other kind, as described in Microsoft Learn under “Replace the trigger in an existing cloud flow”. Actions that used dynamic content from the old trigger then need rework, so for large flows a new flow is often cleaner.

Is a flow started from a Canvas App an instant flow? Yes, it uses the Power Apps (V2) trigger, see #PowerPlatformTip 34.

Can one flow have multiple triggers? No, each cloud flow has a single trigger. Split logic into child flows or an instant flow that others call.

How do I stop an automated flow running too often? Add trigger conditions (or filter columns) so the flow only starts for the rows/events you care about.

🔗 Related

🔸 Cloud Flows vs Desktop Flows, flow categories and licensing.

🔸 #PowerPlatformTip 126: User Context for Automated Tasks, what to do when a scheduled flow needs a user’s context.

🔸 #PowerPlatformTip 190: A Yes/No Trigger Column That Starts a Flow and Resets Itself, a deliberate trigger instead of a noisy automated one.

🔸 Standard vs Premium vs Custom Connectors, what your triggers connect to.

🔸 All Power Automate tips · Knowledge base overview

Last checked: 2026-10-08. Details reflect Microsoft Learn at time of writing. Always confirm current behavior in the Microsoft Power Automate documentation.