HubSpot Workflow Docs

Paste a key. Get every workflow as a Markdown doc.

HubSpot key

Needs automation and crm.objects.contacts.read. Goes through this site to HubSpot, used once, never stored.

How to get a key

In HubSpot, go to Development → Keys → Service keys and click Create service key. You need to be a super admin or have Developer tools access.
Name it (say, "Workflow docs"), click Add new scope and tick automation and crm.objects.contacts.read. Leave the automation.sequences.* scopes off; they are for sequences.
Click Create, open the key, click Show then Copy, and paste it above.
Done? Delete the key, or Rotate → Rotate and expire now. The key's View logs shows every call this tool made (reads only).

No Service keys menu? Use a legacy private app instead: Settings → Integrations → Private apps, same scopes, copy its access token. Workflows need a Professional or Enterprise hub.

About

Paste a HubSpot key and see how many workflows the portal has, then download each one as a Markdown document, or all of them in a zip. Each doc opens with a plain-English summary (who gets in, what happens, when it ends, which workflows it connects to), then lists the enrollment triggers, every action in order with its branches, the goal and settings. The zip adds a map of how the workflows connect. Handy for audits, handovers and change reviews.

What key do I need?: A HubSpot service key (Development, Keys, Service keys) or a legacy private app token, with the automation and crm.objects.contacts.read scopes. The tool only reads. Delete or rotate the key when you are done.
Why does it show fewer workflows than HubSpot does?: HubSpot quietly leaves out any workflow whose records the key cannot read. There is no error; they are just missing. Edit the key and add read scopes for the records your workflows use (crm.objects.companies.read, crm.objects.deals.read, tickets, crm.objects.custom.read, and the sensitive-data versions if you use sensitive properties), then fetch again. When the count matches HubSpot's workflow list, nothing is hidden.
How does it know which workflows are connected?: Two ways. Certain: a workflow names another one, with an Enroll in another workflow step or a trigger on another workflow's enrollment. Possible: one workflow sets a property or adds to a list that another enrolls on, for the same record type. Possible links are marked as guesses, because they only fire when the values match. Finding them needs every workflow, so they are in Download all (.zip), not in single downloads.
Does my key leave my browser?: Yes, unlike most tools here. HubSpot does not let browsers call its API directly, so your key goes through this site's server to HubSpot for each request. It is used for that request only: not stored, not logged, not cached. The Markdown itself is made in your browser. If that is not acceptable, use a key you can revoke once you are done.
Which HubSpot plans work?: The workflows API needs a Professional or Enterprise hub, the same plans that have workflows. On other plans HubSpot refuses the request and the tool says so.
Why do emails, lists and forms show up as IDs?: The workflow definition only stores IDs. Turning them into names takes more scopes and many more API calls, so this version leaves them as IDs. Tick Include raw JSON to add every detail HubSpot returned to the end of each doc. Workflow names are the exception: they come from the list, so links between workflows are shown by name.
Can it change my workflows?: No. It only calls HubSpot's two read endpoints: list workflows and read one workflow.