Consent withdrawal cascades to suppress from active lists and stop nurture
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.
OutcomeThe moment a contact withdraws consent, whether through a subscription unsubscribe or a manual request, the withdrawal cascades to a shared suppression list and force-unenrolls them from the specific nurture workflows named here, instead of leaving them mid-flight in a sequence that a single opt-out never touched.
Workflow mapmarketing-ops-014
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
When to use it, when not to
Use it
Use once marketing-ops-004 (unified unsubscribe tracking) is live
and you have found that contacts still receive one or two more nurture
emails after unsubscribing,...because the nurture itself only checked
eligibility at enrollment.
Use when you can name the specific active nurture and broadcast
workflows that need a forced unenroll step, and are willing to keep that
list current as new nurtures launch.
Read more on when to use itShow less
Skip it
Do not expect this workflow to reach into a workflow built after
this one without being updated. There is no native "stop everything,
everywhere" action; every workflow this fiche should protect has to be
named explicitly, both here and in its own suppression list
configuration.
Do not use this in place of setting each nurture workflow's own
suppression list correctly. This fiche's shared list only works if every
relevant nurture also lists it as a suppression source.