Ever come back to your Power Automate environment and have no idea what half your flows do? A little housekeeping goes a long way. In this quick tip, I’ll share my naming convention for keeping flows organised and easy to find.

Keeping things nice and tidy

The Problem with Default Names

It sounds pretty obvious really, you build a solution and you give it a meaningful name or next time you return to your environment you cannot remember what on earth your automatically named flow does or what it was for?

Name that flow?

My Naming Convention

I tend to include 3 things in my flow name (where applicable)

  1. The owner or purpose of the solution as sometimes you can have multiple flows for one solution
  2. An order and total number of flows in a solution. For instance, if I have 3 flows for a solution and if they were to run in some sort of order, I would call them 1 of 3, 2 of 3 etc.
  3. The main purpose of the flow - a brief description of the flow

An example Flow Name

Why It Matters

At the moment there is nothing you can do to sort or organise your flows, therefore keeping the naming convention strict means you will be able to find what you are looking for and recall what each flow does should it develop problems in the future.

What’s your top tip for Power Automate house keeping? Leave a comment below.

Back to Top Tips