On this page
What HubSpot supports natively
| Contact’s situation | Suppression list (contact workflows) | Unenrollment triggers (company, deal, ticket and other workflows) |
|---|---|---|
| In the list or meets the conditions, not enrolled | Won’t enroll, even if it meets the triggers, and can’t be enrolled manually | Won’t enroll, even if it later meets the triggers |
| Enrolled, then added to the list or meets the conditions | Unenrolled immediately; remaining actions don’t run | Unenrolled immediately |
| Enrolled and not in the list | Stays enrolled | Stays enrolled |
Contact-based workflows can also unenroll contacts that no longer meet the enrollment criteria, or that meet the workflow’s goal. These settings sit in the enrollment trigger’s settings in the workflow editor.
Suppression only works within one workflow. There’s no portal-wide suppression across all workflows, and HubSpot can’t unenroll a record from all workflows at once.
How to use suppression lists in HubSpot workflows
- Write the “never” rule for the workflow. “Never send prospect nurture to customers.” “Never route a lead that already has an owner.”
- Build or reuse a list for it. Keep a small set of standard suppression lists, such as current customers, competitors, internal staff, and contacts in an active sales sequence, and reuse them across workflows.
- Add the list as the workflow’s suppression list, or the matching unenrollment trigger for other objects.
- Add a goal for “the job is done” cases, so contacts leave once they convert.
- Check overlaps between workflows. Two workflows that should never both act on a contact need suppression in at least one of them. See how HubSpot handles automation conflicts.
- Review the lists when your definitions change, for example a new customer lifecycle stage.
Common mistakes
- Using suppression as a one-off unenroll tool and forgetting it. Contacts stay blocked from enrolling for as long as they’re in the list. That’s sometimes what you want; document it.
- Suppressing on a list nobody maintains. A static list from last year doesn’t include this year’s customers.
- Relying on unsubscribes alone. Email subscription status stops emails, not property updates, tasks or routing.
Where Jetstack AI fits
HubSpot shows suppression one workflow at a time. A Jetstack AI Workflow Audit maps it across all of them: every suppression list and suppression filter in every workflow, indexed by list, so for any list you see which workflows suppress with it and which enroll from it. It flags enabled workflows that enroll from the same list, re-enrolling workflows with neither a goal nor suppression, and email workflows with no goal, each naming the workflows involved. Your “never” rules decide which gaps matter, and the audit puts every candidate in one view so you apply them across the portal in minutes. See how to read the findings.
To set up the standard suppression lists described above, and new workflows built around each one’s “never” rule, use Jetstack AI Projects. Write each list’s criteria and each workflow’s rule in the brief, review the plan, then approve generation and deployment separately and check the receipt read back from HubSpot. Lists that update automatically start filling straight away; workflows are created switched off. Projects doesn’t change workflows built elsewhere, so add a new list to an existing workflow’s settings in HubSpot. It’s currently in limited release; see what Projects can build.
Sources
- Set unenrollment triggers and suppression (HubSpot Knowledge Base)
- Manage workflow enrollment settings (HubSpot Knowledge Base)
- Understanding Workflow Audit results: suppression (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