# How to Document HubSpot Workflows # How to Document HubSpot Workflows **Quick answer:** Documenting HubSpot workflows means recording what each workflow does, why it exists, and how it connects to other workflows across the portal. HubSpot's native internal notes let you flag a single workflow. They do not show you the dependency map. A tool like [Howly](https://howly.io) reads the connections between every workflow in the portal, lets you attach risk-rated notes directly on the map, and exports the result as a portal-wide SOP report. * * * ## The problem: HubSpot doesn't show you the connections A RevOps practitioner posted [this on Reddit](https://www.reddit.com/r/hubspot/comments/1ufqyth/comment/otxs8jg/) recently: *"Has anyone used a tool that helps capture all workflow documentation from their HubSpot portal? We're scaling our team, and there has to be an easier way to document our existing framework of properties, syncs, and automations."* There is. Here's what HubSpot gives you natively, and where it stops. * * * ## What HubSpot gives you natively Open any workflow and look at the enrollment step. There's an internal note field sitting right there. It works well for single-workflow context. Flag a workflow as in progress. Mark one for archiving. Tag whoever's responsible. Leave a note explaining why something built two years ago was never turned on. What it does not do: show you how that workflow connects to the other 74 in the portal. A workflow that sets lifecycle stage to Customer might also be starting three other contact workflows through enrollment, list membership, or property changes. The internal note field has no visibility into any of that. Neither do you, unless you trace every workflow by hand, which is exactly the problem the Reddit poster raised. * * * ## Step 1: Map the full workflow system This is the gap Howly fills. Instead of opening workflows one at a time, Howly pulls the entire portal onto a single canvas, organized by object type (Contacts, Companies, Deals, Tickets, and any custom objects), with the connections between workflows drawn automatically. A portal with 75 workflows loads as 75 nodes on a map. The lines show which workflows start other workflows, which fire from list membership, and which are wired together through property changes. Click into one workflow, say a workflow that fires when lifecycle stage changes to MQL, and the map shows both directions at once: what starts it, and what it starts downstream. That's the blast radius. Turn this workflow off, and you can see immediately which workflows stop firing, because they were only enrolling contacts through this one path. This answers the question the internal note box can't. Not just what a workflow does, but what breaks if you touch it. * * * ## Step 2: Flag broken enrollment chains Dependency mapping surfaces problems that don't show up in the workflow list. A common one: a workflow is switched on, has no errors, and looks healthy. But the workflow upstream of it is inactive, so nothing ever reaches the enrollment list. The downstream workflow has been enrolling zero contacts for months, and nothing in HubSpot flags it. This is a broken enrollment chain: an active workflow whose only enrollment path runs through an inactive upstream workflow. When you find one, note it on the workflow and set the risk level. "This workflow is on, but it isn't enrolling anyone because the workflow that starts it is off. Review whether it should be reactivated." Mark it high risk, save it, then go to the inactive workflow upstream and leave a matching note there. Run this across a full portal and a pattern shows up fast: which workflows are load-bearing, which are decorative, and which are quietly misleading anyone who checks the workflow list without checking connections. * * * ## Step 3: Rate risk, not just status Documentation that only records active or inactive doesn't help anyone prioritize. A risk rating tells the next person, or your future self, what to look at first. * **High**: workflow is broken, misconfigured, or should be removed * **Medium**: workflow works but has a design question worth reviewing, for example sending an email as a first step when a separate nurture already covers that * **Low**: workflow is stale (not modified in six or more months) or tied to a campaign that may no longer be relevant, but isn't causing active harm A manually-triggered campaign workflow from an old quarterly promotion, still active with no enrollment criteria firing it, is a clean low-risk note: "Review: this campaign is from 2020. Confirm whether it should stay active." Nothing is broken. It's aging, and someone should decide on purpose whether it stays. * * * ## Step 4: Run the Health Checker before you finish Manual notes catch what you happen to click into. Howly's Health Checker catches what you'd otherwise miss: broken enrollments, duplicate workflows, stale workflows untouched for 14 or more months, and standalone workflows with no connections at all. It also produces an overall portal health score. Every flagged item links directly to the workflow in question, so reviewing the health report and adding notes happens in the same pass. * * * ## Step 5: Export the report Once notes are in place, the exported report is the SOP document, not a summary written about the work. A finished report shows the portal health score, total workflow count, and a documentation summary: for example, 9 of 75 workflows manually documented, 4 flagged high risk, 66 undocumented. It lists every workflow with object type, action count, active or inactive status, last-modified date, and the risk-rated note attached to it, along with AI-generated insights on the portal as a whole. That report, an inventory with benchmarks, AI audit, and SOP notes in one file, is specific enough to hand to a new hire, an agency taking over the account, or your own team six months from now when nobody remembers why a workflow called "Set MQL Workflow" exists. * * * ## Watch the full walkthrough %[https://youtu.be/IW160e9obmY] * * * ## Frequently Asked Questions **How do I document HubSpot workflows for my team?** Start with HubSpot's native internal notes to flag status and ownership on individual workflows. Then map the full portal in a connected tool like Howly to see how workflows enroll into each other through direct enrollment, list membership, or property changes. Add a risk-rated note to any workflow with a problem, whether it's broken, part of a broken enrollment chain, or simply worth reviewing, and export the full workflow inventory as a report. That report, combined with your notes, functions as your SOP document. **What is a broken enrollment chain in HubSpot?** A broken enrollment chain is an active workflow whose only path to enrolling contacts runs through an upstream workflow that has since been turned off. The downstream workflow shows as active and error-free in HubSpot's workflow list, but it isn't processing any contacts because nothing is feeding it. These are common in portals that have been through team turnover, since the person who built the enrollment chain often isn't the one who later deactivated a piece of it. **Does HubSpot show how workflows are connected to each other?** Not natively. HubSpot's workflow list shows each workflow individually, and the enrollment step includes an internal note field for flagging status. There is no native view that shows direct enrollment, list-based, or property-based connections between workflows across the full portal. Seeing those connections requires either tracing each workflow's enrollment and action steps by hand, or connecting a dependency-mapping tool that reads the portal and builds the map automatically. **How long does it take to document 75 HubSpot workflows?** Manually, expect several hours to a full day, depending on how many workflows have unclear naming or undocumented enrollment logic. With a connected mapping tool, the portal loads in 10 to 25 seconds, and the time investment shifts to reviewing connections and writing notes rather than reconstructing them, typically closing the gap to under an hour for a portal in the 50 to 100 workflow range. **What should a HubSpot workflow SOP include?** A complete workflow SOP should list every workflow by name and object type, its active or inactive status, when it was last modified, what triggers it, what it does, and how it connects to other workflows upstream and downstream. It should also include a risk rating for anything needing review, whether broken, part of a broken enrollment chain, redundant, or stale, along with a note explaining why. A workflow list alone isn't an SOP. It's an inventory. * * * ## Summary Native HubSpot internal notes are useful for single-workflow context, but they don't show how a portal's automation logic fits together. Documenting HubSpot workflows properly means three things: mapping the connections between workflows, flagging problems with a risk rating as you find them, and exporting the result as a report your team can actually use. Connect the portal to Howly and see the full dependency map, add notes directly on the workflows that need attention, and export a portal-wide SOP report before your next handoff, migration, or audit. *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.* [**Start your 7-day free trial**](https://howly.io). No credit card required.