How to Run a HubSpot Workflow Audit, Step by Step
How to Run a HubSpot Workflow Audit, Step by Step
Quick answer: A HubSpot workflow audit means inventorying every workflow in a portal, mapping how each one connects through direct enrollments, active lists, and shared properties, then scoring every workflow for health, stale, orphaned, empty, or duplicate, before anyone changes anything. Done by hand, that takes a team days, sometimes weeks, depending on portal size. Done with a dependency-mapping tool, a full audit could take just under thirty minutes.
The rest of this guide is the five steps that make up a complete audit, in the order that actually works.
What counts as a full workflow audit
A workflow audit is not the same thing as scrolling through the workflows list and reading names. It has five parts, and skipping any one of them leaves a gap that shows up later, usually as a broken automation nobody can explain.
A complete audit covers:
Inventory and mapping. Every workflow, plus every connection between them: direct enrollment, list-based, and property-based.
Health scoring. Which workflows are stale, orphaned, empty, or likely duplicates, and what a change to any one of them would actually touch.
Prioritization. A ranked list of what to fix first, not just a pile of flagged workflows with no order to them.
Documentation. The purpose and risk level of each workflow, written down somewhere other than one person's memory.
Reporting. A version of all of the above that a client or a leadership team can actually read.
Portals that reach a few hundred workflows tend to have accumulated all of this risk without anyone deciding to build it in. A shared property gets added to a list-based workflow built by one team and a property-based workflow built by another, and neither team knows the other one exists. Nobody notices until a field update sets off both at once.
Step 1: Inventory every workflow and map how they connect
Start with a complete list. Every workflow, active and inactive, across every object type, Contacts, Companies, Deals, Tickets, and any custom objects. Most portals have never had this list assembled in one place before, which is itself a finding worth writing down.
From there, map connections. There are three kinds:
Direct enrollment, where one workflow enrolls records into another.
List-based, where a workflow is triggered by membership in an active list.
Property-based, where a workflow is triggered by a property value changing.
A sequence of workflows linked by direct enrollment is an enrollment chain. Chains are usually easy to trace inside a single workflow's settings. What is much harder to see by hand is a list-based or property-based connection between two workflows that were built months apart by people who never talked to each other. That's where manual audits lose the most time, and where most of the real risk in a large portal actually lives.
On a portal with hundreds of workflows, building this map by opening each one individually is not a realistic option. Howly connects to a portal and builds the full map on one visual canvas, direct enrollment chains, list-based triggers, and property-based triggers, without opening a single workflow.
Step 2: Score health and trace every dependency
Once the map exists, score it. Four categories catch most of what goes wrong in a workflow system over time:
Stale. Active, but not modified in six or more months.
Orphaned. Active, with no upstream or downstream connections to anything else.
Empty. Configured, but containing no actions.
Duplicate. Flagged by name similarity to another workflow, usually a sign of a copy nobody cleaned up.
A portal health score puts a single number on the result: 70% and above is healthy, 50 to 69% needs attention, and anything below 50% means the automation system has more risk in it than the team can currently see.
Health scoring only tells you what's wrong. Dependency tracing tells you what a fix would touch. Before turning off an orphaned workflow or changing a property that feeds a dozen others, trace its full upstream and downstream dependency chain first. An orphaned workflow with no connections is safe to remove. A workflow that looks unused but still feeds three others downstream is not, and the only way to know the difference is to trace it before acting, not after.
Step 3: Rank findings by priority
A list of forty flagged workflows is not an action plan. It's a bigger list. The step most manual audits skip, mostly because it takes real time to do by hand, is turning that list into an order: what to fix first, what can wait, and what's actually fine once you look closer.
This is where an AI audit earns its place in the process instead of being a novelty on top of it. Howly's AI audit, powered by Claude, reads the full portal and returns a ranked list of findings, issues, gaps, and opportunities, in about fifteen seconds. Howly is also the only HubSpot workflow tool with native MCP support, which means findings can be queried directly from Claude Desktop instead of only inside a separate dashboard.
If a team is already using AI agents to build workflows through HubSpot's Workflows API, ranking matters even more. Automation built by an agent still needs the same dependency check as automation built by a person, arguably more, since there's no one to ask why it exists. (More on that governance question in our post on using Claude Code with the HubSpot Workflows API.)
Step 4: Document what the map alone can't show
A dependency map shows what's connected. It doesn't show why a workflow exists, who it's for, or what breaks if it's wrong. That context usually lives in one person's head, which is fine until that person leaves.
Add a purpose and a risk level to every workflow as you go. Over time this compiles into a documented system instead of a folder of tribal knowledge, and a coverage summary shows exactly what's documented and what's still a black box. This is the step that pays off six months later, when someone new inherits the portal and needs to know what a workflow does without having to ask the person who built it, because that person is gone.
Step 5: Export a report someone outside the audit can use
An audit that lives only in a dashboard doesn't help the people who need to sign off on the next change. Export the health score, the AI findings, the dependency maps, and the documentation coverage into a report a client or a leadership team can actually read, benchmarked against similar-sized HubSpot portals so the numbers mean something in context. Howly exports to PDF, PNG, or Lucidchart, with agency branding on the report where that matters.
How long a workflow audit should actually take
For a portal with a few hundred workflows, mapping every enrollment chain, list trigger, and property trigger by hand, then tracing dependencies for each flagged workflow, is realistically days of work, more for a portal with no naming convention or documentation to start from.
With Howly, a full workflow audit, mapped, scored, prioritized, and documented, takes under thirty minutes. Teams using it see workflow audits run 70% faster, workflow-related problems drop by 45%, and discovery calls that used to take days move 3 to 5 times quicker. MAVN Marketing, an agency managing eighteen HubSpot portals with a team of three, cut audit time from fifteen hours to ninety minutes, which changed their pre-sales process enough to run live audits during client calls instead of promising a report later.
As James Winters, a HubSpot Solutions Partner, put it: "Saved me hours of untangling messes across workflows, especially ones triggering each other."
Where a tool fits into this process
Everything above can be done by hand. It's just slow, and slow gets worse as the portal grows. A dependency-mapping tool exists to compress steps 1 through 3 from days to minutes, so the time a team actually spends goes toward steps 4 and 5, the documentation and the decisions, instead of toward building the map itself.
Howly connects to a HubSpot portal through read-only OAuth 2.0. It cannot write, edit, or change anything in the portal, it only reads and maps what's already there. It's compatible with HubSpot Professional and Enterprise portals, including Sandbox, supports unlimited connected client portals under one agency account, and access can be revoked at any time from HubSpot's Connected Apps settings. It's available as a featured app on the HubSpot Marketplace, with a 7-day free trial and no credit card required.
If a portal has reached the point where nobody's fully sure what would happen if a given property changed, connect it to Howly and see the full dependency map before the next change goes out, not after.
Frequently Asked Questions
What is a HubSpot workflow audit? A HubSpot workflow audit is the process of inventorying every workflow in a portal, mapping how they're connected through direct enrollment, list-based triggers, and property-based triggers, and scoring each one for health, stale, orphaned, empty, or duplicate, so a team knows what a change will affect before making it. A complete audit also includes documenting each workflow's purpose and risk level, and producing a report that people outside the audit itself can use.
How long does a HubSpot workflow audit take? By hand, a portal with a few hundred workflows typically takes a team days to fully map and score, longer if there's no existing documentation or naming convention to work from. With a dependency-mapping tool like Howly, a full audit, mapped, scored, prioritized, and documented, takes under thirty minutes.
What's the difference between a stale workflow and an orphaned workflow? A stale workflow is active but hasn't been modified in six or more months. An orphaned workflow is active but has no upstream or downstream connections to any other workflow. A workflow can be one, both, or neither, which is why the two are tracked as separate categories rather than combined into a single "old" label.
Does auditing HubSpot workflows require giving a tool write access to my portal? No. Howly connects through read-only OAuth 2.0 and cannot write, edit, or change anything inside a HubSpot portal. It only reads workflow configurations to build the dependency map and health score. Access can be revoked at any time from HubSpot's Connected Apps settings.
Can I run a workflow audit on a HubSpot Sandbox portal? Yes. Howly is compatible with HubSpot Professional and Enterprise portals, including Sandbox portals, which makes it usable for testing a change before pushing it to production.
How often should HubSpot workflows be audited? At minimum, before any portal migration, client handoff, or major integration, since those are the moments when an unmapped dependency is most likely to cause a problem. Portals that add workflows regularly are worth auditing on a quarterly cadence, so sprawl and undocumented risk get caught early instead of accumulating for years.
Summary
A HubSpot workflow audit has five parts: inventory and map every workflow and its connections, score each one for health and trace its dependencies, rank findings by priority, document what the map can't show on its own, and export a report someone outside the audit can actually use. Done by hand, that process takes days on a portal of any size. Done with a dependency-mapping tool, it takes under thirty minutes, and the time saved goes toward the documentation and decisions that actually reduce risk, not toward building the map itself.
Automation without visibility is guesswork. Connect a portal to Howly and see the audit run in real time.
Howly is a read-only HubSpot workflow mapping and audit tool. It maps workflow connections, flags structural issues, and shows the impact of property changes before you make them. Used by RevOps teams and HubSpot agencies managing complex portals at scale.
