On this page
What HubSpot supports natively
HubSpot stores some documentation for you, but only per workflow.
| Native feature | What it gives you | What it doesn’t |
|---|---|---|
| Name and description | A searchable label per workflow (dashboard search matches both) | Any structure: it’s free text |
| Folders and saved views | Grouping by team, object or process | Relationships between workflows |
| Export view on the workflows dashboard | A spreadsheet of the workflow list, with some metrics such as enrollments | Triggers, actions or what each workflow writes |
| Export as .PNG in a workflow | An image of one workflow, with branches | Performance data, history, other workflows |
| Connections tab | The lists, properties and other assets one workflow uses | A portal-wide view |
| Revision history | What changed, when, and by whom | Why it changed |
So the per-workflow facts are available. The architecture, meaning how 200 workflows depend on each other, is not.
How to document HubSpot workflow architecture
- Export the inventory. Use Export view on the workflows dashboard as your starting sheet. See getting a report of all workflows.
- Add the columns HubSpot doesn’t export. For each workflow: business purpose (one sentence), owner, object type, enrollment trigger in plain words, properties it writes, workflows it enrolls records into, and a keep / fix / retire decision.
- Group by process, not by team. Lead capture, lifecycle and routing, onboarding, renewals. A process page lists its workflows in order and the property that hands a record from one to the next.
- Map the connections. Draw two kinds of edges: one workflow enrolling records into another (the “Go to workflow” action), and one workflow writing a property that another reads. The second kind is the one people miss, and the one behind most surprises.
- Record the single owner of each key property. Lifecycle stage, lead status, owner. If more than one workflow writes it, note why.
- Link back from HubSpot. Put the doc link and the owner in each workflow’s description.
- Review on a schedule. Use revision history and the Unused tab on the dashboard to find what changed or stopped running since the last review.
Common mistakes
- Screenshots as documentation. An image of one workflow goes stale on the next edit and says nothing about what else depends on it.
- Documenting actions, not intent. “Sets lead status to Open” is in the workflow already. “Hands new inbound leads to SDRs” is what the next admin needs.
- No naming convention. Documentation is much easier to keep current when names follow a pattern. See HubSpot workflow naming conventions.
Where Jetstack AI fits
A Jetstack AI Workflow Audit builds the inventory and the connection map from the portal itself: a plain-language brief per workflow, the assets each one reads and writes, explicit enrollment paths, and shared writers. Your team can save notes and keep / improve / investigate / retirement-candidate decisions against each workflow, and they carry over to the next audit of the same portal. See how to read the dependency map.
Sources
- Organize your workflows (HubSpot Knowledge Base)
- Export your content and data (HubSpot Knowledge Base)
- View and revert changes to your workflow (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.
Workflows & automation
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