Instant Triggers: Flows You Start Yourself
An instant trigger, often called a manual trigger, starts a flow only when a person deliberately initiates it, most commonly via the 'Manually trigger a flow' action inside the Power Automate mobile app, a button embedded in a Power App, or a 'Run flow' link surfaced in a SharePoint list or Teams message. Instant triggers can define input parameters, such as text, file, or a yes/no choice, which the user fills in at run time, letting the flow adapt its behaviour to whatever the user supplied that specific time it was launched.
Cricket analogy: It's like a captain calling for a DRS review by making the 'T' signal, a deliberate human action that starts a specific process only when someone chooses to invoke it.
Scheduled (Recurrence) Triggers
A scheduled trigger, implemented with the Recurrence trigger, fires on a timer defined by a frequency (Second, Minute, Hour, Day, Week, or Month) and an interval, with optional advanced options for specific times of day, days of the week, and time zone. For example, a frequency of Week with interval 1 and 'On these days' set to Monday and Thursday, combined with an 'At these hours' value of 9, runs the flow every Monday and Thursday at 9 AM in the configured time zone, making it ideal for recurring reports, nightly data syncs, or weekly digest emails.
Cricket analogy: It's like a cricket academy's fixed weekly nets schedule every Tuesday and Friday at 6 AM, running automatically on the calendar regardless of who shows up.
Configuring Recurrence
{
"type": "Recurrence",
"recurrence": {
"frequency": "Week",
"interval": 1,
"schedule": {
"weekDays": ["Monday", "Thursday"],
"hours": [9],
"minutes": [0]
},
"timeZone": "India Standard Time"
}
}Always set the timeZone property explicitly on a Recurrence trigger. If omitted, Power Automate defaults to UTC, which frequently causes flows to run at unexpected local hours, especially problematic for scheduled reports tied to a business's opening time.
Combining Manual Inputs with Scheduling
Instant and scheduled triggers can be layered inside the same solution: a scheduled flow might run nightly to compile a report, while a separate instant-triggered flow lets a manager re-run that same report on demand from a Teams command, both calling into a shared child flow to avoid duplicating logic. Designing the input parameters of an instant trigger carefully — using required fields, dropdown choices instead of free text where possible, and clear labels — reduces user error, since unlike a scheduled trigger's fixed configuration, instant trigger inputs are supplied fresh by a human every single run.
Cricket analogy: It's like a franchise having both a fixed pre-season training calendar (scheduled) and the option for a player to book an extra individual net session on demand (instant) using the same coaching staff.
Recurrence triggers can drift slightly over time due to platform load, and Power Automate does not guarantee exact-second precision; for time-sensitive business processes (e.g., financial cutoffs), build in tolerance rather than assuming the flow fires at the exact configured second.
- Instant triggers start a flow only when a person deliberately initiates it, often supplying input parameters at run time.
- Scheduled triggers use the Recurrence trigger to fire on a defined frequency, interval, and optional specific times/days.
- Always set an explicit time zone on a Recurrence trigger to avoid unexpected UTC-based run times.
- Instant and scheduled triggers can share the same underlying logic via child flows.
- Well-designed instant trigger inputs (dropdowns, required fields) reduce user error.
- Recurrence timing is not guaranteed to the exact second, so build tolerance into time-sensitive flows.
- Choosing manual versus scheduled triggers depends on whether a human decision or a calendar should govern execution.
Practice what you learned
1. What is the defining characteristic of an instant trigger?
2. Which trigger type is used to run a flow on a recurring calendar schedule?
3. Why should you explicitly set the timeZone property on a Recurrence trigger?
4. In the sample Recurrence JSON, what does weekDays: ['Monday', 'Thursday'] configure?
5. What should you consider when designing input parameters for an instant trigger?
Was this page helpful?
You May Also Like
Automated Triggers
Learn how automated triggers detect events in connected services and kick off Power Automate flows without any manual action.
Actions and Steps
Learn how actions form the sequential building blocks of a flow's logic, from simple connector calls to control-flow constructs like conditions and loops.
Expressions in Flows
Master Power Automate's Workflow Definition Language expressions to transform data, build conditions, and manipulate strings, dates, and arrays.
Related Reading
Related Study Notes in Programming
Browse all study notesApache Spark Study Notes
Programming · 30 topics
ProgrammingApache Flink Study Notes
Programming · 30 topics
ProgrammingHadoop Study Notes
Programming · 30 topics
ProgrammingSnowflake Study Notes
Programming · 30 topics
ProgrammingApache Airflow Study Notes
Programming · 30 topics
Programmingdbt (Data Build Tool) Study Notes
Programming · 30 topics