Skip to content
Home » Blog Archive » Best Practices for Naming Your Workflows in n8n, Zapier and Make.

Best Practices for Naming Your Workflows in n8n, Zapier and Make.

When it comes to logically naming workflow automation processes or jobs in tools like n8n, Make (formerly Integromat) and Zapier, it’s important to use a naming convention that is clear, descriptive, and consistent.

Here are some best practices we use here at SPACEtag for naming workflow automation processes:

Use Descriptive Names

Choose names that clearly describe the purpose or function of the workflow automation process. This makes it easier to understand and identify the process at a glance. For example, instead of using a generic name like “Job 1,” consider using a descriptive name like “New Lead Notification.”

Include Relevant Keywords

Include relevant keywords in the name to make it more searchable and easily identifiable. For example, if the workflow automation process is related to customer onboarding, you could include keywords like “Onboarding” or “Customer Setup” in the name.

Follow a Consistent Format

Establish a consistent naming format for your workflow automation processes. This helps maintain clarity and consistency across different processes. For example, you could use a format like “[Trigger] – [Action]” or “[Source] > [Destination]” to indicate the purpose of the process.

Use Abbreviations or Acronyms

If your workflow automation processes are part of a larger system or involve multiple systems, you can use abbreviations or acronyms to represent those systems. However, make sure the abbreviations are widely understood within your team or organisation.

Add Version Numbers or Dates

If you anticipate making changes or updates to a workflow automation process over time, consider adding a version number or date to the name. This helps to differentiate between different iterations and track the evolution of the process. Whilst some platforms have versioning (e.g. Zapier) making this obvious in the title can be helpful.

Group Related Processes

If you have multiple workflow automation processes that are related or part of the same workflow, consider using a common prefix or suffix to group them together. This makes it easier to navigate and manage processes within your automation tool. If possible group them in virtual folders if your platform allows.

Keep It Concise

While it’s important to be descriptive, try to keep the names concise and avoid unnecessary details. Long and complex names can be cumbersome and make it harder to scan and understand the list of processes.

Make it Easy

Remember, the goal of naming workflow automation processes is to create a system that is easy to understand, maintain, and search within your automation tool. Choose a naming convention that works best for your team or organisation and ensures clarity and consistency across your processes.

Example Naming Convention

When developing Zapier Zaps on behalf of a client or for ourselves internally, we could the following naming convention:

[Status] Source/Trigger > Destination App: Task (Work Item ID)

For example:

[InDev] WooCommerce > QuickFile: Post Order Invoice (973)

Essentially this tells me that a trigger on WooCommerce will affect the QuickFile Accounting Platform – and in fact it will create an Invoice for an order that’s been created.

The status [InDev] tells me that it’s in development. Other statuses would be:
[InTesting] It’s being tested.
[Prod] It’s in production (i.e. Live)
[Offline] It’s currently not being used.
[ForDeletion] It’s no longer being used and can be deleted.

As there is a quota on the number of Zaps that can be on the account, purging unwanted jobs and general housekeeping is important.

The final part is (973). This is the Process Automation project task ID in our OpenProject tool – this is important so that it can be crossed-referenced back to the development, and any issues, comments, features can be logged there.


Choosing the right names for your workflow automation processes in tools like n8n, Zapier and Make can greatly enhance efficiency and organisation. By following these best practices and adopting a clear and consistent naming convention, you can create a system that is easily understandable, searchable, and manageable.

Descriptive and concise names, along with the inclusion of relevant keywords, will streamline your workflow and help you navigate through processes effortlessly. Take control of your automation journey by implementing these naming strategies, and unlock the full potential of workflow automation in your business.

Share this post