Skip to content
Book a build

What naming conventions should you use for HubSpot workflows?

A good HubSpot workflow naming convention puts the same facts in the same order: team or process, what the workflow does, the object, and a status tag when needed, for example "Sales | Route inbound demo requests | Contact". HubSpot doesn't enforce any naming rules, so write the pattern down, use the description for owner and purpose, and rename workflows during reviews.

On this page

What HubSpot supports natively

FeatureHow it helps naming
Name and descriptionFree text. Dashboard search matches both
FoldersGroup workflows; set a folder as your default view
Saved views and filtersFilter by object type, creator, team, folder, status and action type
Workflow Filing Agent (Enterprise)Files unfiled workflows into folders automatically

HubSpot doesn’t enforce a pattern, check for duplicates, or require a description. Because search matches the name and description, a consistent convention is what makes the dashboard usable once you pass a few dozen workflows.

A HubSpot workflow naming convention you can adopt

Pattern: Team or process | What it does | Object | Tag

Examples:

  • Marketing | Nurture webinar registrants | Contact: says who owns it and what it does.
  • Lifecycle | Set MQL from score | Contact: shows it writes a key property.
  • Sales | Route inbound demo requests | Contact: routing workflows are easy to find.
  • Service | Escalate overdue tickets | Ticket: the object is visible without opening it.
  • Ops | Normalize country values | Company | Utility: tags a helper workflow other workflows enroll into.
  • Events | Follow-up 2026 summit | Contact | Temporary: marks a workflow that should be retired.

Rules that keep it useful:

  1. Verb first in the middle part. “Route”, “Set”, “Notify”, “Nurture”. It tells you what the workflow changes.
  2. Name the key property it writes when it owns one: lifecycle stage, lead status, owner.
  3. Use a small, fixed tag list: Utility, Temporary, Retired, Test. Nothing else.
  4. Put the rest in the description: business owner, purpose in one sentence, the date it was last reviewed, and a link to documentation.
  5. Match folders to the first part of the name, so a folder and a search return the same set.
  6. Don’t reuse names. A clone should get its own name before it’s turned on, not “Copy of…”.

Common mistakes

  • Names that describe the trigger only. “Form submission – contact us” says what starts it, not what it does.
  • Personal names as owners. People leave. Use a team or role.
  • Conventions nobody wrote down. Put the pattern in your workflow documentation, next to your property naming conventions.

Where Jetstack AI fits

A Jetstack AI Workflow Audit includes an AI naming analysis: it reads the names of up to 300 workflows, works out the naming patterns your portal already uses, points out the workflows that break them, and suggests a standardized name for each one it points out. Separately, each workflow’s health score checks that it has a name of more than a few characters and a description, and the portfolio governance score shows what share of workflows have both. Naming findings are suggestions, so the convention stays yours. See how to read the findings. If you roll out a standard, well-named workflow set to client portals, Portal reuse lets you deploy the same setup to multiple destination portals, reviewing each portal’s mappings.

For new workflows, put the pattern in the brief of a Jetstack AI Project. Jetty uses the exact names you give it, and the plan lists every asset it will create before anything is built, so you check the convention at review. Deployment is a separate approval, workflows are created switched off, and the receipt lists each asset with its result, read back from HubSpot. Projects doesn’t change workflows built elsewhere, so rename existing ones in HubSpot during reviews. It’s currently in limited release; see the Projects quickstart.

Sources

Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Workflows & automation

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

Workflows & automation

Related questions.

What naming conventions should you use for HubSpot workflows?

A good HubSpot workflow naming convention puts the same facts in the same order: team or process, what the workflow does, the object, and a status tag when needed, for example "Sales | Route inbound demo requests | Contact". HubSpot doesn't enforce any naming rules, so write the pattern down, use the description for owner and purpose, and rename workflows during reviews.

Should the name include the date or version?

Not normally. HubSpot's revision history already records when a workflow changed and who changed it. Put a date only on time-bound workflows, such as one event's follow-up.

Should I rename existing workflows to the new convention?

Yes, gradually. Renaming doesn't change how a workflow runs. Start with active workflows that write key properties, then do the rest during regular reviews.