The Workflow Library

Library / Marketing ops / marketing-ops-042

List-based nurture eligibility gate (marketing contact + subscription check)

Marketing opsContactMarketing Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A contact only continues through a nurture sequence while they are both a marketing contact and subscribed to the relevant subscription type, so nurture workflows stop wasting sends and enrollment slots on people who cannot legally or practically receive them.

Workflow map Enrollment, branches and actions at a glance marketing-ops-042
flowchart TD
    A[Nurture workflow reaches eligibility gate] --> B{Marketing contact AND opted in?}
    B -->|Yes| C[Continue in nurture workflow]
    B -->|No| D[Add to Nurture-ineligible list]
    D --> E[Unenroll from nurture workflow]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse as a reusable eligibility check placed at the start of, or as a periodic re-check within, any nurture workflow.
  • UseUse to consolidate a check that would otherwise be copy-pasted into every nurture workflow's enrollment criteria individually.
  • SkipDo not use this fiche to try to stop an email that HubSpot has already queued or sent from a marketing email tool outside a workflow context. A workflow cannot reach into an already-scheduled send and cancel it. This fiche only controls whether a contact continues through workflow-driven nurture steps; it detects ineligibility and exits or escalates, it does not retroactively block anything already sent.
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.3 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.4 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 marketing 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.