Power Automate: When an HTTP request is received Trigger
Turns a Flow into a web service. Accepts external calls with a JSON schema.
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.
Turns a Flow into a web service. Accepts external calls with a JSON schema.
Accesses each element inside repeating actions like Apply to Each.
Creates a Planner task: group, plan, title, dates, assignments, and labels.
Runs a Flow on demand with typed input parameters. Empty optional inputs aren't returned.
Returns the week number for a date. Start day is configurable.
Returns all tasks from a Planner plan as an array.
Fires when a new email arrives in any Outlook folder.
Returns the arithmetic mean of number columns. Up to 30 parameters.
Fires when a Forms response is submitted. Returns the response ID only.
Removes leading and trailing spaces. Inner spaces stay intact.
Modifies a Planner task: title, dates, progress, and assignments.