As with all things with labels, it’s a good idea to have a naming convention for your flows.
A proper convention allows you and your clients to find what they are looking for easily. It also makes things easier to support, and to create a sense of structure.
If multiple consultants and admins are building flows, you don’t want the results to look like there were dozens of cooks in the kitchen.
Below is a naming convention you are free to use.
For record-triggered flows, start with the object name, then the trigger, then the action performed.
Examples:
- “Contact Updated – Set Custom Field”
- “Account Created – Set Primary Contact”
For all other flows, start with a verb, then the object name. For verbs, keep to a small list, such as
- Get
- Create
- Update
- Delete
- Process
- Search
- Manage
Examples:
- “Get Campaigns”
- “Manage Attendance”
- “Create Payment from Opportunity”
The takeaway
Keeping to simple and concise naming convention for your flows keeps things in order.