How to Audit a Complex HubSpot Portal With 100+ Workflows
You have been handed a client portal with 134 workflows. Some are active. Some are inactive. Most have no descriptions, no naming convention, and were built by people who are no longer at the company. You need to know what is connected to what, what is broken, and what is safe to change. Auditing a complex HubSpot portal means mapping every workflow connection, scoring portal health, and identifying duplicate, stale, and circular automation logic before you touch anything, so you can present findings to the client without guessing.
This post walks through a full audit of a real portal using Howly, from the first list view to a client-facing report.
The starting point: the native list view tells you almost nothing
The portal in this audit belongs to a marketing and branding agency. Open their workflow section in HubSpot and you get the standard list view: workflow names, enrolled contact counts, and creation dates. That is useful for confirming volume. It is useless for understanding structure.
Immediately the familiar problems surface. Descriptions are missing. Naming conventions have collapsed. Workflows date back to 2022 and are still active. The list confirms there are 134 workflows and that some of them are very old. It cannot tell you whether one workflow enrolls contacts into another, whether a property change triggers a cascade, or whether two workflows are quietly fighting over the same lifecycle stage.
That is the gap. The native view shows you the inventory. It hides the dependencies. And the dependencies are where the risk lives.
Step 1: See every workflow on a canvas, grouped by object type
Connect the portal to Howly via OAuth and the same workflows render as nodes on a canvas instead of rows in a list. The nodes are grouped by object type: 78 contact workflows, 20 deal workflows, 2 company workflows.
This is the first thing the list view cannot do. You are looking at the entire automation surface of the portal at once, organized the way HubSpot actually thinks about it, in a single screen.
Step 2: Run the Health Checker before you map anything
Before mapping connections, get a baseline. The Health Checker analyzes every workflow and returns an overall portal score out of 100, plus a breakdown of warnings and informational flags.
In this portal the score came back at 54. Underneath that number: 93 warnings and 88 info items. The score is driven by stale workflows, duplicate actions, and empty workflows. Inactive workflows and possible duplicates do not lower the score directly. They surface as immediate action items instead.
The headline finding was blunt: 91 workflows had not been modified in six or more months. That is the definition of a stale workflow, and at that volume it points to automation logic that no longer matches the business.
Step 3: Toggle all connections and find the clusters
With a baseline in hand, turn on all connections. The canvas immediately shows where the density is. Some contact workflows reach into company workflows. Some contact workflows reach into deal workflows. The outliers and the large clusters become obvious at a glance.
This is the moment that replaces Lucidchart, Miro, and the manual whiteboard. You are not redrawing the portal by hand. The map already exists. You are just deciding how to read it.
Step 4: Build the dependency map by isolating clusters
Drag the connected nodes apart to trace each customer journey. Start a cluster in the top left, pull its downstream workflows out beside it, and the structure resolves itself.
Two findings landed fast in this portal:
A race condition on lifecycle stage. Two separate workflows were both setting lifecycle stage to Customer. That is an immediate consolidation opportunity, and exactly the kind of conflict that is invisible in the list view.
A circular dependency. One workflow set lead status to Connected, and another workflow set the same property to the same value, with each capable of starting the other. In a healthy portal, automation follows the lifecycle upstream to downstream. It does not loop back on itself.
Click any node and the sidebar shows its exact connections: how many workflows it starts, which ones, and the enrollment trigger for each. Click through to HubSpot from the same panel and you land directly on that workflow, ready to edit. Any change you make in HubSpot reflects back in Howly across connections, status, and properties.
Watch the full 28-minute portal audit walkthrough.
Step 5: Use the Impact Analyzer to find the highest-risk properties
The Impact Analyzer ranks the most-used properties across every workflow in the portal, contextual to that specific portal. For this agency the heaviest hitters were deal stage, pipeline, list membership, lead status, and lifecycle stage.
Click into deal stage and you see the blast radius: 27 workflows trigger enrollment on it. The analyzer separates what triggers enrollment from what modifies the property, so you know before you change a deal stage value exactly how many workflows will react. You can jump straight from the analyzer to the node on the canvas, and from there into HubSpot.
This is the difference between changing a property and changing a property safely.
Step 6: Run the AI Audit for a documented second opinion
The AI Audit, powered by Claude, reads the full portal and returns a structured writeup in about 15 seconds: a description, the major issues, gaps, opportunities, and recommendations.
For this portal it confirmed what the manual mapping had already surfaced and added detail:
A healthy 73 percent active ratio, with focus on lead magnet delivery and form follow-up
Duplicate deal stage workflows, cloned from the same stages
Multiple duplicate form workflows
An inactive 20-week nurture campaign with 40 actions and 20 emails, built but apparently abandoned
Heavy reliance on single-action property-setting workflows, a clear consolidation target
Minimal conditional branching, where more branching would reduce workflow proliferation
The recommendations read like a scope of work: consolidate duplicate deal stage workflows, review the single-action form submission workflows, map the enrollment chain dependencies, and archive the inactive and empty workflows. Download the audit and drop it straight into Claude to draft the SOP or the client report.
Step 7: Export the report and the map for the client
Two artifacts close out the audit. From the canvas, export the connection map as a PNG. From the Health Checker, download the full PDF report, which can be white-labeled for agencies.
The report packages everything: the 54 health score, the active and inactive counts, the warnings and info items, top priorities, workflow counts by type, and the full workflow inventory broken down by status, object type, action count, and last update date.
It also includes portal benchmarks, comparing this portal against others of similar size. This portal sat well above the median on stale and standalone workflows. The median portal carried around 14 stale and 9 standalone. This one carried far more, which is the kind of specific, defensible finding a client takes seriously.
The common workflow: hand the PDF to the client as the audit, then run the same report through Claude to generate next steps and a statement of work.
What the audit found, in plain terms
In under 30 minutes, a portal that looked like an undifferentiated wall of 134 workflows resolved into a clear picture:
Stale logic everywhere. 91 workflows untouched in six-plus months, including a four-year-old nurture program still feeding outdated offers to contacts.
Conflicting and circular automation. Two workflows racing to set the same lifecycle stage, and a property loop where two workflows wrote the same value to lead status.
Consolidation opportunities at scale. Duplicate deal stage workflows and a long tail of single-action property setters that could collapse into far fewer, branched workflows.
None of this is visible in the native list view. All of it is visible the moment the connections are mapped.
Frequently Asked Questions
How do I see which HubSpot workflows are connected to each other?
HubSpot's native workflow tool shows workflows as a list with no view of how they connect. To see connections, you need a tool that detects the three workflow connection types: direct enrollment, list-based, and property-based. Howly maps all three onto a canvas, grouping workflows by object type and drawing the links between them, so you can see which workflows enroll contacts into others and which property changes trigger downstream automation.
How long does it take to audit a HubSpot portal with 100+ workflows?
A full audit of a 100-plus workflow portal, including health scoring, dependency mapping, property impact analysis, an AI audit, and a client report, takes under 30 minutes with the right tooling. Howly loads a full portal workflow map in 10 to 25 seconds depending on portal size, which removes the hours normally spent rebuilding the map by hand in Lucidchart or Miro.
What is a stale HubSpot workflow?
A stale workflow is an active workflow that has not been modified in six or more months. Stale workflows are a primary signal of automation drift: the logic was correct when built but may no longer match the current business process, product offering, or messaging. In the portal audited here, 91 of 100 analyzed workflows were stale, including a nurture program last updated in 2022.
Can I change my HubSpot workflows directly from an audit tool?
Howly is read-only and cannot write, edit, or change anything in your portal. It connects via OAuth 2.0 and only reads workflow data. To make a change, you click through from any node on the Howly canvas straight to that workflow in HubSpot, where you edit it natively. Once you do, the change reflects back in Howly across connections, status, and properties.
What is a circular dependency in HubSpot workflows?
A circular dependency is when workflows trigger each other in a loop instead of following a clean upstream-to-downstream path. In this audit, two workflows both set lead status to Connected and were each capable of starting the other. Circular logic makes automation hard to troubleshoot and can cause workflows to re-enroll contacts unexpectedly. Mapping connections on a canvas is the fastest way to spot it.
Summary
Auditing a complex HubSpot portal comes down to three things the native interface will not give you:
The connections. See every workflow on one canvas, grouped by object type, with direct enrollment, list-based, and property-based links drawn in.
The risk. Score portal health, find stale and duplicate and empty workflows, and use property-level impact analysis to know the blast radius before you change anything.
The documentation. Export a branded report and an AI audit you can hand to the client and run through Claude to build the statement of work.
A portal of 134 workflows is not unmanageable. It is just undocumented. Connect the portal to Howly and see the full dependency map before your next change.
Start with a 7-day free trial, no credit card required.
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.
