On this page
What HubSpot supports natively
The mess is rarely HubSpot’s fault, but it helps to know which controls exist.
| Control | What it does |
|---|---|
| Edit vs Publish permissions | Creating and editing workflows needs Edit permission; turning them on needs Publish permission |
| Folders, saved views, descriptions | Organize workflows and record their purpose |
| Unused tab | Lists workflows that are off or haven’t executed any actions in the last 90 days |
| Needs review tab | Lists workflows that hit errors in the last 7 days |
| Revision history | Shows what changed in a workflow, when, and who made the change |
| Connections tab | Shows the assets one workflow uses |
What HubSpot doesn’t do is enforce any of it. There’s no required naming pattern, no owner field that must be filled, and no warning when a new workflow writes a property three other workflows already set.
Why every HubSpot portal turns into a mess
The pattern is the same in most portals:
- Workflows are cheap to create and nobody retires them. A campaign ends, the workflow stays on.
- Many builders, no owner. Marketing, sales ops and an agency all build automation for their own goals.
- Key properties get several writers. Lifecycle stage, lead status and owner are set by forms, integrations, HubSpot settings and several workflows. Values flip and nobody knows why. See why lifecycle stage keeps changing.
- Clones multiply. A working workflow is cloned for a new region or product with small edits, and the copies drift apart.
- No documentation of intent. The next admin can see what a workflow does, not why, so they leave it on.
How to keep a portal from turning into a mess
- Give every key property one owner. One workflow (or one setting) sets lifecycle stage. Others request the change through a flag property.
- Restrict Publish. Let people draft; let a small group turn workflows on after a review.
- Use a naming convention and require a description with owner and purpose. See HubSpot workflow naming conventions.
- Review the Unused and Needs review tabs monthly. Turn off or delete what nobody claims. See managing unused workflows.
- Keep an inventory with purpose, owner and the properties each workflow writes.
If the portal is already past this point, see whether to fix or rebuild a messy portal.
Where Jetstack AI fits
A Jetstack AI Workflow Audit gives you the starting inventory for that cleanup: every workflow with a health score, findings such as competing actions and circular enrollment, and a map of which workflows share properties. You record keep / improve / investigate / retirement-candidate decisions per workflow and they carry over to the next audit, so the review becomes routine. The Workflow Audit overview explains what it checks.
For workflows the review marks for replacement, Jetstack AI Projects builds the corrected version as a new asset. Describe its job, the property it owns and who it must exclude in the brief, approve the plan, then approve deployment separately and check the receipt read back from HubSpot. The new workflow is created switched off, and you retire the old one in HubSpot once the replacement is tested. Projects is currently in limited release; see what Projects can build.
Sources
- Create workflows: permissions (HubSpot Knowledge Base)
- Organize your workflows (HubSpot Knowledge Base)
- View and revert changes to your workflow (HubSpot Knowledge Base)
- Workflow Audit overview (Jetstack AI documentation)
Checked October 29, 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