Naming convention in Make.com
Some say that 80% of a software developer's time is spent on coming up with names. And it applies to no-code development too.
Have you ever spent long minutes searching for this old Make scenario and not remembered the name? Or maybe you have seven connections with the same name? Yeah, I've been there, too.
A simple name convention is a tool that will save you a lot of time in the future.
Below is my approach to names. Copy it or modify it if you need to. Just make sure you and your team use one standard.
Scenarios:
[Domain/Customer][Sub-domain/multi scenario flow] Step number. Trigger -> Outcome
Example, simple scenario:
Example, complex multistep flow:
Scenario 1:
Scenario 2:
Connections:
[Domain/Customer] Application name (Date created)
Example:
Webhooks:
[Domain/Customer][Sub-domain/multi scenario flow] Step number. Event
Example, simple scenario:
Example, complex multistep flow:
Clarify if necessary
Sometimes, even with this naming convention, things might be confusing or require additional clarification.
For example, when working for a customer, I use my app connections, and then I want to switch everything to the customer. In that situation, I add at the end: - DEV/- PROD. Then, it's easy for me to spot any DEV connections that should be updated.
