What Is an Automated Trigger?
An automated trigger is the starting point of a cloud flow that fires the moment a specified event happens in a connected service, such as a new email arriving in Outlook, a file being added to a SharePoint library, or a row being inserted into a SQL table. Unlike instant triggers, which need a human to press a button, an automated trigger runs entirely in the background, polling or subscribing to the connector's event source so the flow reacts within seconds of the event occurring.
Cricket analogy: It behaves like a third umpire's automatic no-ball detection system at the crease, which fires the instant the bowler's front foot crosses the line, with no on-field umpire needing to raise a hand.
Common Trigger Types
Power Automate ships automated triggers for most first-party and third-party connectors: 'When a new email arrives' (Outlook), 'When a file is created in a folder' (SharePoint/OneDrive), 'When an item is created or modified' (SharePoint lists, Dataverse), and 'When a new response is submitted' (Microsoft Forms) are among the most used. Each trigger is implemented either as a polling trigger, where Power Automate checks the connector's API on a schedule (commonly every 1-5 minutes), or as a webhook (push) trigger, where the external service calls Power Automate's endpoint directly the instant the event occurs, giving near-instant latency.
Cricket analogy: Polling versus webhook triggers are like the difference between a scorer manually checking the scoreboard every over versus Hawk-Eye pushing ball-tracking data to the broadcast the instant a delivery is bowled.
Configuring a Polling Interval
{
"type": "ApiConnectionNotification",
"inputs": {
"host": {
"connectionName": "shared_sharepointonline",
"operationId": "OnNewFile",
"apiId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline"
},
"parameters": {
"dataset": "https://contoso.sharepoint.com/sites/Finance",
"folderId": "/Shared Documents/Invoices"
}
},
"recurrence": {
"frequency": "Minute",
"interval": 3
}
}Most SharePoint and OneDrive triggers default to a 3-minute polling interval on standard plans; per-flow licensing (Power Automate Premium) can shorten this to as low as 1 minute, but most webhook-based triggers such as Dataverse's 'When a row is added' bypass polling entirely and fire in near real time.
Trigger Conditions and Filtering
To avoid a flow running on every single event, you can attach a trigger condition, an expression evaluated in the trigger's Settings pane that must resolve to true before the flow body executes. For example, on the 'When an item is created or modified' SharePoint trigger you might add @equals(triggerOutputs()?['body/Status/Value'], 'Approved') so the flow only proceeds when a status column changes to Approved, rather than firing (and burning API calls) on every edit to any column.
Cricket analogy: It's like a DRS review only being triggered when the on-field umpire's decision is challenged within 15 seconds, filtering out every routine delivery that doesn't need scrutiny.
Trigger conditions are evaluated before the flow run is even created, so if the condition is false the run won't appear in run history at all — this makes debugging tricky. Test conditions with a temporary Compose action first, or check the trigger's raw inputs in a successful run to confirm the exact property path and casing you need.
- Automated triggers start a flow in response to an event in a connected service, with no manual action required.
- Triggers are implemented as either polling (checked on an interval) or webhook/push (event pushed instantly).
- Standard polling intervals are often around 1-5 minutes depending on the connector and licensing tier.
- Trigger conditions let you filter which events actually start the flow, saving API calls and avoiding unnecessary runs.
- A false trigger condition prevents a run from being created at all, so it won't show up in run history.
- Common examples include new email arrival, new SharePoint file, new Dataverse row, and new Forms response.
- Choosing the right trigger type directly affects both automation latency and the number of API calls consumed.
Practice what you learned
1. What distinguishes an automated trigger from an instant trigger in Power Automate?
2. What are the two main implementation styles for automated triggers mentioned in the topic?
3. What happens when a trigger condition evaluates to false?
4. In the sample JSON, what does the 'recurrence' property with frequency 'Minute' and interval 3 configure?
5. Why might you add a trigger condition on a SharePoint 'item created or modified' trigger?
Was this page helpful?
You May Also Like
Instant and Scheduled Triggers
Understand how manually-launched instant triggers and time-based scheduled triggers give you full control over when a flow runs.
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.
Dynamic Content
Learn how to pass outputs from triggers and earlier actions into later steps using Power Automate's dynamic content picker and underlying expressions.
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