The Workflow Library

Library / Sales ops / sales-ops-017

Auto-unenroll a contact from all sequences when they unsubscribe from all sales email

Sales opsContactSales Hub EnterpriseSimple~15 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Enterprise, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A contact who opts out of one-to-one sales email stops receiving sequence steps immediately, with no window where an already-queued step still goes out.

Workflow map Enrollment, branches and actions at a glance sales-ops-017
flowchart TD
    A[Sales email opt-out becomes true] --> B[Unenroll from sequence]
    B --> C[Set Sequence exit reason = Unsubscribed]
    C --> D[Add to Do not sequence list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on every portal that runs sequences. This is a compliance guardrail, not an optional nicety.
  • UseUse it as the single place that reacts to an opt-out, instead of trusting that sequences will simply skip a send (they generally do respect opt-out status at send time, but a queued step can still show as "active" until its send attempt, which is confusing for reps checking a contact's status).
  • SkipDo not treat this as a substitute for checking subscription status before any one-to-one email send outside of sequences; this workflow only manages sequence enrollment.
  • SkipDo not scope this narrowly to one sequence. The property this workflow watches applies portal-wide, so unenrollment should too.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the sales ops pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.