Power Automate: Planner - When a task is completed Trigger
Fires when a Planner task is marked complete.
Every flow starts with a trigger, and getting the trigger right is half the battle. This is my dedicated reference for Power Automate triggers, kept separate from the action reference because triggers behave in their own particular ways. Here you'll find a deep dive into one trigger at a time, explaining how it fires, what data it hands you, and the best practices and limitations worth knowing before you rely on it. I cover the classic "Manually trigger a flow" trigger for on-demand runs, event-driven starters like the "When a new response is submitted" trigger for Microsoft Forms, and the "When an email is flagged" trigger for Office 365 Outlook. For Dataverse builders I explain the "When a row is added, modified or deleted" trigger and the settings that decide when it actually runs, plus the concurrency and trigger-condition tricks daily users miss.
Fires when a Planner task is marked complete.
Runs a Flow from a Power App. Power Platform handles parameter passing.
Fires when a SharePoint list item is created or modified. Polls on an interval, not instant
Runs a Flow on a schedule. Supports seconds to months, specific hours, days, and time zones.
Fires when a file is created in a SharePoint folder, library, or site page.
Turns a Flow into a web service. Accepts external calls with a JSON schema.
Runs a Flow on demand with typed input parameters.
Fires when a new email arrives in any Outlook folder.
Fires when a Forms response is submitted. Returns the response ID only.
Fires when a new RSS feed item is published.
Fires when a new task is created in a Planner plan.