Power Automate: Power Apps (V2) Trigger
Runs a Flow from a Power App with typed inputs: text, numbers, files, booleans.
Here I share the best practices I use for the Power Platform tools, drawn from my own experience and plenty of learning from other people's mistakes so I don't repeat them. None of this is set in stone, so adjust it to fit how you work. Consistency matters, especially when several people share a platform. I see it constantly: SharePoint sites with mismatched naming, lists with convoluted names, and flows nobody can follow. When you agree on rules, everyone always knows what something means, and onboarding a new person becomes far easier. Even if you never adopt my conventions, at least write your own down. And even if you work alone, building your own reference makes you think, and you will often spot places where things could be better. That reflection is half the value.
Runs a Flow from a Power App with typed inputs: text, numbers, files, booleans.
Parses an XML document to extract nodes, attributes, and counts. Input must be XML type.
Fires when a new Outlook email mentions you.
Fires when a user picks a OneDrive file. Your Flow name appears in the file menu.
Fires when a user picks a SharePoint file. Your Flow name appears in the file menu.
Updates an Excel row matched by a key column. Works on SharePoint, Teams, and OneDrive files.
Fires when a SharePoint list item or file is modified.
Returns a single Excel row by key column value.
Returns the query string from a URL. Empty when there are no parameters.
Fires when a SharePoint list item is deleted. Returns who and when, not the item's columns.
Adds a key column to an Excel table so other Excel actions can reference rows.