Microsoft Power Automate is a cloud-based automation platform within the Microsoft Power Platform ecosystem that enables users to create automated workflows connecting apps, data, and services. It combines cloud flows for API-driven automation with desktop flows for robotic process automation (RPA), allowing organizations to automate repetitive tasks without extensive coding. Power Automate integrates deeply with Microsoft 365, SharePoint, Dynamics 365, and Dataverse, while also supporting hundreds of third-party connectors. Understanding trigger types (automated, instant, scheduled), control flow logic (conditions, loops, parallel branches), and licensing tiers (standard vs premium connectors) is essential for building efficient, scalable automations that reduce manual work and increase productivity.
What This Cheat Sheet Covers
This topic spans 14 focused tables and 128 indexed concepts, 96 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Flow Types and Triggers
Power Automate offers three primary flow types distinguished by how they start: automated flows respond to events, instant flows require manual activation, and scheduled flows run on a timer. Each trigger type serves different automation scenarios β automated for event-driven processes, instant for on-demand tasks, and scheduled for recurring operations. Choosing the correct trigger ensures your flow activates exactly when needed.
| Type | Example | Description | |
|---|---|---|---|
When an item is created (SharePoint)When a new email arrives (Outlook) | β’ Triggered automatically by an event in a connected service β’ runs without user interaction when the specified condition occurs | ||
Manually trigger a flowFor a selected item | β’ Started manually by a user through a button in Power Automate mobile app, Power Apps, SharePoint, or Microsoft 365 β’ also called button flows. | ||
Recurrence: Daily at 9 AMEvery Monday at 8:00 AM | β’ Runs on a fixed schedule defined by recurrence trigger β’ supports intervals from seconds to months with time zone configuration | ||
UI automation recording Web scraping actions | Robotic process automation (RPA) that automates repetitive tasks on Windows desktop applications using UI element interaction or image recognition. | ||
Dataverse trigger Custom table changes | β’ Dataverse-specific trigger that fires when records change β’ supports filtering by columns and scope (organization, business unit, user). | ||
Model-driven app action Selected records in view | β’ Enables users to select one or more records in a Dataverse view and trigger a flow β’ appears as an action button in model-driven apps | ||
Webhook endpoint POST https://...logic.azure.com/... | β’ Creates a webhook URL that external services can call β’ supports JSON schema for request body validation and returns responses via Response action | ||
Third-party webhook Subscribe/unsubscribe pattern | β’ Implements the webhook pattern with subscribe and unsubscribe callbacks β’ used for building custom webhook connectors |