Power Automate Naming Conventions Coding Standards
Anyone with a search engine can create code computers can understand. We should endeavor to create code that human's can understand.
This document is a fork of Mathew Devaney's Power Automate Coding Standards For Cloud Flows. I've made adjustments to my own perferences.
Table of contents
Flows
A flow name should begin with a verb (action word), describe what outcome the flow will achieve and include the trigger type. Use proper case. Be as concise as possible.
When choosing the verb, use the PowerShell Approved Verbs list.
Examples:
- Send Daily Status Report (Scheduled)
- Get Currency Rates From Web (Automated)
- Change App Ownership (Instant)
Actions
A flow action name must always start with the action’s original description. It is important to include this so developers can understand which action was selected without having to expand it. Then add more details about what the action is doing within the context of the current flow.
Use proper case. Separate the action name and its context using a colon.
Examples:
- Get Items: Inspections Table
- Compose: Email message body
- Send Email (V2): Daily Report To Operations Leadership
Triggers
Automated flow trigger names should include the table or event name in the trigger name.
Example: When An Item Is Created: Safety Incidents
Scheduled flow trigger names must display the recurrence schedule.
Example: Recurrence: On The 1st & 15th Of The Month At 5PM
Instant flows trigger names should also describe the event that triggers them.
Example: Manually Trigger A Flow: When An Admin Wants To Create A New SharePoint Team Site
Power Apps flow trigger names should describe the event the app which triggers the flow to start.
Example: Power Apps (V2): When The User Submits A New File To Upload
Variables
A flow variable name should begin with a prefix of "var" and describe its subject/purpose in concise manner. Use camel case. with no spaces between each word. Be as concise as possible.
Examples:
- varQuantityInBox
- varEmployeeFullName
- varIsPastDue
Connection references
A connection reference name starts with a noun to describe the connection account. Then it is followed by the connection type, the solution name and a unique identifier. These are automatically added when building inside of a solution.
Examples:
- SvcAcct-SharePoint CurrencyExchangeRates-ac3d5
- SvcAcct-Dataverse CurrencyExchangeRates-be005
- SystemAlerts-Office 365 Outlook CurrencyExchangeRates-32a0c