On this page
What HubSpot supports natively
| Tool | What it does | What it doesn’t |
|---|---|---|
| Test criteria | Shows whether a record meets the enrollment triggers (a record only needs to match one group) | Run anything |
| Test (preview) | Pick a record and Automatic or Manual enrollment; see the simulated outcome and timestamp of each action and the path highlighted | Execute actions; branches that depend on a previous action’s output may need choosing by hand |
| Send preview on an email action | Sends you the emails on the preview path | Send to the contact |
| Turn-on choice | Enroll existing records that meet the criteria now, or only future ones | Let you turn on for one record only |
Branch conditions are evaluated in order, and the record follows the first one it meets. To test another branch, pick it from the dropdown or choose a record that matches it. Testing uses the current version of the workflow, and timing settings can reschedule actions in real runs.
For event triggers such as Property value changed, enrollment can’t be tested; only the AND filters are checked.
How to test a HubSpot workflow before turning it on
- Create test records that represent each path: one per branch, plus one that should not enroll.
- Run Test criteria on each to confirm who qualifies.
- Run Test with each record and check every action’s simulated outcome, especially Edit record values and owner assignments.
- Send preview emails to yourself and check personalization tokens against the test record.
- Check settings: timing windows, suppression list, goals, re-enrollment.
- Narrow the trigger for a live test. Add a temporary filter such as “Email contains your test domain”, turn the workflow on with “only enroll after turning on”, and trigger it with a test record.
- Read the action log for the test record, then remove the temporary filter.
- Decide on existing records when you remove the filter: enrolling them can send emails to everyone who qualifies today.
Common mistakes
- Testing one happy path. Most problems are in the branch nobody tested.
- Testing without the other workflows. A workflow can pass every test and still be overwritten by another workflow afterward. See why a workflow isn’t working with no errors.
- Removing the test filter with “enroll existing” selected on a workflow that sends email.
Where Jetstack AI fits
HubSpot’s test shows one workflow in isolation. A Jetstack AI Workflow Audit maps the configuration around it across every workflow in the portal, switched-off drafts included: which other enabled workflows enroll from the same lists or write the same properties, which send records into this one, and which read the properties it writes. For the workflow itself, it flags contradictory branches, branches that don’t match the enrollment criteria, re-enrollment with no goal or suppression, and the most emails one path can send in seven days. You walk into your live test knowing exactly which other workflows to check. See how to read the findings.
Sources
- Test your workflow (HubSpot Knowledge Base)
- Set event enrollment triggers (HubSpot Knowledge Base)
- Create workflows (HubSpot Knowledge Base)
- Understanding Workflow Audit results (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