Standards

Power Automate Naming Standards

Naming guidance for triggers, scopes, actions, variables, Compose steps, and child flows.

Power Automate naming standardscloud flow standardsflow action names

Who this helps

Flow builders who need supportable run history and readable troubleshooting.

What to standardize

Name actions by business intent.
Prefix scopes by stage such as Try, Catch, Finally.
Use Compose names that describe transformed values.
Keep flow names searchable by system and outcome.

Examples

Readable flow action names

Make run history understandable without opening every action.

Formula / code

Flow: Requests - Send approval reminder
Scope: Try - build reminder email
Compose: Compose - formatted due date
Condition: Condition - request is still pending
Scope: Catch - log reminder failure

Expected result: Support owners can scan failed runs quickly.

Common mistakes

Leaving action names as Compose 7
Renaming only the first few actions
Using vague names such as Process Data