On this page
What HubSpot supports natively
HubSpot workflows have four kinds of enrollment trigger: filter-based, event-based, scheduled and webhook-based, plus manual enrollment.
| Property value changed (event) | Filter-based on a property | |
|---|---|---|
| Fires when | One property changes from one value to another | The record meets the filter conditions |
| Existing records | Not enrolled for past changes | Can be enrolled when you turn the workflow on |
| Extra conditions | AND filters checked at the moment of the change | AND / OR filter groups |
| Historical operators (“updated in last X days”) | Not supported | Supported |
| Re-enrollment | “Yes, re-enroll every time the trigger occurs” | Re-enrolls when the record goes from not matching to matching a selected trigger |
| Testing | Enrollment can’t be tested; only AND filters are checked | Test criteria shows whether a record qualifies |
Multiple event triggers in one workflow are combined with OR. Event filters are only checked when the event happens; later property changes don’t re-evaluate it.
How to trigger a HubSpot workflow when a property changes
- Create the workflow for the right object (the property must belong to it, in general).
- Add the Property value changed trigger and choose the property.
- Add AND filters for the value you care about, for example “Lead status is Connected”. Remember they’re checked at the moment of the change.
- Decide on re-enrollment. If it should run every time the property changes, turn it on for the trigger.
- Test with a real change on a test record after turning the workflow on, since event enrollment can’t be previewed.
- For records that already have the value, enroll them manually or create a separate filter-based workflow and choose to enroll existing records.
Common mistakes
- Triggering on a property your workflow also writes. With re-enrollment on, that’s a loop. See circular HubSpot workflows.
- Triggering on a property several tools write. Every import, form or integration update fires the workflow. Check which workflows and tools edit the property first.
- Using “is known” for re-enrollment on a filter trigger: it re-enrolls on every change, which may be more than you want. See how re-enrollment works.
Where Jetstack AI fits
A Jetstack AI Workflow Audit marks potential handoffs: one workflow writes a property that another workflow reads on the same object. Those are the property-change chains to check before adding a new trigger. It doesn’t confirm the same records and timing line up; it shows where to look. See dependency relationship types.
To build the workflow itself, use Jetstack AI Projects. Describe the property change that should start it and the filters it needs in the brief, and check that Jetty’s plan shows the trigger you meant before you approve it. Jetty builds in dependency order, so a new property comes before the workflow that uses it, and deployment is a separate approval with a receipt read back from HubSpot. The workflow is created switched off, so the live test in step 5 still happens in HubSpot. Projects is currently in limited release; see what Projects can build.
Sources
- Set event enrollment triggers (HubSpot Knowledge Base)
- Add re-enrollment triggers to a workflow (HubSpot Knowledge Base)
- Create workflows: trigger types (HubSpot Knowledge Base)
- Workflow Audit API: potential handoffs (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