On this page
What HubSpot supports natively
HubSpot gives you three places to look. Each answers part of the question.
| Where | What it shows | Limits |
|---|---|---|
| Property settings, Usages tab | Where the property is used in the CRM, plus its fill rate | Needs Data Hub Professional or Enterprise to see the details. Doesn’t say how each workflow uses the property. |
| Property settings, Data sources tab | Tools that update the property | Same subscription requirement. Tells you which tools write, not which workflow steps do it. |
| Workflow editor, Connections tab | The asset types a workflow uses, including properties and lists | One workflow at a time. Doesn’t separate “reads” from “sets”. |
| Record property history | Each change to a value, with its date and source | One record at a time. Shows what happened, not what is configured. |
The gap is the distinction most admins care about: which workflows edit the property, and which only reference it. A workflow can touch a property in an enrollment trigger, a branch condition, an Edit record action, a Clear property action, a copy action or a personalization token. HubSpot’s views list the workflow; you still open it and find the step.
How to see which workflows use a property, and which edit it
- Start from the property. Open Settings, find the property, and read its Usages tab. Write down every workflow listed.
- Check whether each one is on. Filter the workflows dashboard by On or Off. An inactive workflow that uses the property still matters if someone turns it back on.
- Open each workflow and classify the reference. Look at the enrollment triggers, every branch, and every action. Mark it as a writer (Edit record, clear or copy into the property) or a reader (trigger, branch, filter, token).
- Confirm with real records. Open a few records where the value changed recently and view the property history. The Source column shows which tool made each change.
- Look for more than one writer. If two or more workflows set the same property, that’s where values flip back and forth. See how HubSpot handles automation conflicts.
Common mistakes
- Only checking active workflows. Turned-off workflows don’t run, but they get cloned and switched back on.
- Forgetting other writers. Forms, imports, integrations and HubSpot settings also update properties. Lifecycle stage is the usual example: see why a contact’s lifecycle stage keeps changing.
- Treating “used in” as safe to change. Renaming an option’s label doesn’t affect workflows, but merging options does: HubSpot doesn’t update the branches, segments and filters that compare against the merged value, so you have to fix them by hand.
Where Jetstack AI fits
A Jetstack AI Workflow Audit reads every workflow in the portal and lists each property, list, form, email, owner and pipeline they reference, with the number of distinct workflows that use, read and write it. For any property you can open the individual workflow references, and the dependency view marks workflows as shared writers or potential handoffs. The audit only reads your portal. See the Workflow Audit API’s asset views for what each relationship means.
Sources
- Create and edit properties (HubSpot Knowledge Base)
- View workflow connections (HubSpot Knowledge Base)
- View a record's property history (HubSpot Knowledge Base)
- Manage enumeration property options (HubSpot Knowledge Base)
- Workflow Audit API: assets and references (Jetstack AI documentation)
Checked October 30, 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