On this page
What HubSpot supports natively
HubSpot can show you which workflows need attention, but not which to fix first.
| Native view | What it shows | Limit |
|---|---|---|
| Workflows Health tab | Workflows set to “Needs review” and unused workflows (no enrollments for at least 90 days) | Professional or Enterprise; no ranking by impact |
| Review workflow issues | A list of issues in one workflow to fix or ignore | One workflow at a time |
| Action logs | Each action’s result, with timestamps, kept for 90 days | Doesn’t show conflicts with other workflows |
| Enrollment history | Enrollments up to 6 months old | Per workflow |
None of these tell you that two workflows are setting lifecycle stage to different values for the same contacts. That’s the kind of finding that matters most and is hardest to see one workflow at a time.
Where to start with hundreds of broken workflows
- Freeze new builds. Ask the team not to add workflows until triage is done. Otherwise the list keeps growing.
- Sort by customer and revenue impact. First: workflows that send marketing email, set lifecycle stage or lead status, rotate owners or create deals. A broken nurture email reaches customers; a badly named internal alert doesn’t.
- Fix live conflicts first. Two workflows writing different values to the same property, or a contact enrolled in both a customer and a prospect nurture, cause visible damage today.
- Turn off what nobody uses. Check unused workflows with their owner, then turn them off rather than delete them.
- Fix errors in what remains. Missing properties, deleted lists and failed email sends.
- Leave naming and folders for last. They help maintenance, not customers.
- Re-audit and compare. Count conflicts and low scores again so you can show progress.
For a general method that applies beyond workflows, see how to prioritize audit findings. If the list is so long that fixing looks slower than rebuilding, read fix or rebuild.
Common mistakes
- Fixing the noisiest workflow instead of the most harmful one.
- Deleting inactive workflows that are really seasonal.
- Changing a heavily connected workflow without checking what depends on it.
Where Jetstack AI fits
Jetstack AI’s Workflow Audit scores every workflow from 0 to 100, lists conflicts by severity (critical, high, medium, low) and maps which workflows depend on each other, so you can see the knock-on effect of a change before you make it. It doesn’t change the workflows. When a workflow is beyond repair, or a whole process needs redoing, build the corrected version with Projects, currently in limited release: describe the logic in a brief, approve the plan, then approve deployment separately. The new workflow is created switched off, so you can test it before you switch it on and turn off the old one; Projects doesn’t edit workflows it didn’t build. See understanding workflow audit results and deploying with Projects.
Sources
- Monitor your workflow health (HubSpot Knowledge Base)
- Understand your workflow details page (HubSpot Knowledge Base)
- Understanding workflow audit results (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.
Portal audits
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