Search for a command to run...
You open the client's HubSpot portal for the first time. They've asked you to document everything — all the workflows, how they connect, what they do, who owns them.
No comments yet. Be the first to comment.
Agencies and RevOps teams showing how they use Howly in their day-to-day work. Real portals, real results, no fluff.
MAVN Marketing, a HubSpot RevOps agency managing 18 portals, reduced workflow audit time from 15 hours to 90 minutes using Howly, transforming their pre-sales process and enabling visual client presentations that close deals faster.
Quick Answer: A HubSpot workflow audit is the process of inventorying every workflow in a portal, mapping how they connect through direct enrollment, list membership, and property changes, and scoring
Quick Answer: A HubSpot workflow audit for a new client starts with taxonomy, not automation. Before touching a single workflow, an experienced consultant maps the naming conventions, separates workfl
July's Howly release removes the 50-workflow cap on free accounts, so the entire portal is visible on the free plan. Data agent and agent hub actions now surface directly on the workflow canvas. The audit report has been rebuilt with best practice recommendations, one-click links back into HubSpot, and full brand customization. Navigation also got faster, with a new search box, a Recent Changes panel, and trigger-type filtering.
A repeatable process for inventory, dependency mapping, and impact analysis, built for portals too large to hold in one person's head.
Nine workflow visibility gaps that hide broken automation and risky dependencies
You click into Automation.
There are 160 workflows.
Some are active. Some are inactive. Half of them are named things like "Copy of Copy of Lead Nurture — FINAL v2." You have no idea who built them or when. And you have two other clients waiting on the same deliverable.
This is the situation nobody warns you about when you start doing HubSpot consulting. Here is exactly what to do.
The problem is not the number of workflows. The problem is that HubSpot shows you workflows one at a time, in a flat list, with no indication of how they relate to each other.
You can open a workflow and see its triggers and actions. What you cannot see — from inside HubSpot — is whether that workflow feeds into three others, whether it shares a list trigger with another automation running in parallel, or whether the property it updates is being overwritten by something else thirty seconds later.
Mapping workflows manually means opening each one, taking notes, cross-referencing properties and lists, and trying to build a picture in your head — or in a spreadsheet — of a system that was never designed to be understood this way. For a portal with 50 workflows, that takes most of a day. For a portal with 150, it takes several.
And when you are managing five client portals at once, you do not have several days per client.
The instinct is to start at the top of the list and work down. Resist it.
Reading workflows sequentially gives you a list of facts with no structure. You will finish the audit knowing what each workflow does in isolation, but you will not know how the system behaves as a whole — which is what the client actually needs to understand.
Start with structure, not content.
Before you read a single workflow, export a full inventory. In HubSpot, you can filter by object type and status, but there is no native export. You will need to either build the list manually or use a tool that pulls it automatically.
What you need in your inventory:
Workflow name
Object type (Contact, Company, Deal, Ticket, custom)
Status (active or inactive)
Last modified date
Enrollment count
This gives you the skeleton before you try to understand the details.
Once you have the inventory, the next job is dependency mapping — figuring out which workflows connect to which others.
There are three connection types to look for:
Direct enrollments. Workflow A contains an "Enroll in workflow" action that sends records into Workflow B. These are the most obvious and the easiest to find, but they still require opening every workflow to check.
List-based connections. Workflow A adds contacts to a HubSpot list. Workflow B uses that list as an enrollment trigger. These connections are invisible unless you cross-reference every list used as a trigger against every workflow that modifies list membership. In a portal with 80+ workflows and dozens of active lists, this is where manual mapping breaks down completely.
Property-based connections. Workflow A sets a property to a specific value. Workflow B triggers when that property hits that value. These are the hardest to find because the connection exists only in the data layer — there is no visual link between the two workflows inside HubSpot.
Completing this mapping gives you a dependency map of the portal. That map is the actual deliverable the client needs — not a spreadsheet of workflow names, but a picture of how the system connects.
A workflow map is useful. A workflow map with a prioritized issues list is what gets you rehired.
While you are mapping, flag:
Empty workflows. Active workflows with no actions. Records may be enrolling into them with nothing happening.
Orphaned workflows. Active workflows with no upstream or downstream connections that do not appear to serve a standalone purpose. These are candidates for deactivation.
Stale workflows. Active workflows that have not been modified in over six months and whose logic may no longer reflect current business processes.
Duplicate workflows. Workflows with identical or near-identical names or logic. Common in portals that have been managed by multiple people over time.
Conflicting property writes. Two or more workflows updating the same property with potentially different values. This is one of the most common causes of bad CRM data and one of the hardest to find without tooling.
Delivering this issues list alongside the map turns a documentation project into a strategic audit. That is a different service level — and a different price point.
The single-client version of this is already time-consuming. At agency scale — managing five, ten, or twenty client portals — the manual approach does not work.
The compounding problem is not just time. It is context-switching. Every time you move between client portals, you are rebuilding your mental model of a completely different automation system from scratch. Spreadsheets and Miro boards do not travel well between clients, and they go stale the moment the client's team makes a change.
What you need is a tool that:
Connects to multiple HubSpot portals under a single account
Automatically builds the workflow inventory and dependency map when you connect
Stays current without requiring you to manually refresh the documentation
Produces a shareable output you can hand to the client or present in a review call
Howly is built for exactly this. Connect a client portal via OAuth and Howly loads every workflow across every object type onto a single canvas, automatically maps all three connection types, and flags structural issues — empty workflows, stale automations, conflicting logic — in the same view.
For agencies, every client portal gets its own workspace under a single Howly account. You can move between clients without rebuilding anything. The map is always current because it syncs directly from HubSpot.
The workflow map exports to PDF, PNG, or Lucidchart for client deliverables. Most agencies use the export as the foundation of their audit report — the visual map as the centerpiece, the issues list as the action plan.
The deliverable for a workflow audit has three parts:
The map. A visual representation of the workflow system showing all active workflows, their connections, and their object types. This is what the client looks at when they want to understand how their automation is structured.
The issues list. A prioritized list of structural problems — empty workflows, stale logic, duplicate automations, conflicting property writes — with a recommended action for each. This is what the client acts on.
The dependency reference. A written record of every cross-workflow connection: which workflows feed into which, via what mechanism, and what the linking list or property value is. This is what the client's team refers to before making any future change.
Together, these three components give the client something they almost certainly did not have before you arrived: a complete, current picture of how their HubSpot automation actually works.
Manually, for a portal with 50 to 100 workflows, expect one to two full days of work to complete a thorough inventory, dependency map, and issues list. For larger portals, add time accordingly. With a tool like Howly, the inventory and dependency map are generated automatically when you connect the portal — most consultants can complete a full audit review in two to three hours regardless of portal size.
The most useful handoff documentation includes a visual workflow map showing all connections, a written inventory with status and ownership for each workflow, a dependency reference showing cross-workflow relationships, and an issues list with recommended actions. Howly's PDF and Lucidchart export covers the visual map and can be supplemented with a written summary for the full package.
The key is a tool that supports multiple portal connections under a single account and keeps documentation current without manual effort. Spreadsheets and static diagrams go stale immediately and do not scale past two or three clients. Howly's multi-portal support is designed for this use case specifically.
The three dependency types to look for are direct enrollments (one workflow enrolling records into another), list-based connections (one workflow adding to a list that another uses as a trigger), and property-based connections (one workflow setting a value that triggers another). HubSpot does not surface any of these natively — finding them requires either opening every workflow manually or using a tool that maps them automatically.
A complete workflow audit should cover: a full inventory of all workflows across all object types, a visual dependency map showing cross-workflow connections, a health assessment flagging structural issues, an impact analysis showing what would break if specific workflows or properties were changed, and a prioritized list of recommended actions. The audit is the foundation for any cleanup, migration, or handoff project.
When a client asks you to map their HubSpot workflows and you open the portal to find 160 automations with no documentation, the answer is not to start reading them one by one. The answer is to build structure first — inventory, then dependency map, then issues list — and to use tooling that does the heavy lifting automatically rather than rebuilding the same picture manually for every client.
The deliverable that actually serves the client is not a spreadsheet. It is a visual map of how their automation system connects, a clear list of what is broken or stale, and a reference they can use before making any future change.
If you are managing more than two or three client portals, doing this manually is not a sustainable workflow. Connect your client portals to Howly and see the full dependency map before your next audit call.
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.
