The Workflow Library

Library / Lead nurturing / lead-nurturing-047

Nurture branch by preferred content format (video vs. article vs. podcast)

Lead nurturingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A nurture sequence delivers the same core topics in each contact's preferred format, video, article, or podcast, instead of assuming one format works for everyone.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-047
flowchart TD
    A[On audience list] --> B{Format preference?}
    B -- Video --> C1[Send: Topic 1 video]
    B -- Article --> C2[Send: Topic 1 article]
    B -- Podcast --> C3[Send: Topic 1 podcast]
    B -- No pref --> C4[Send: Topic 1 article default]
    C1 --> D[Delay 5 days]
    C2 --> D
    C3 --> D
    C4 --> D
    D --> E{Format preference?}
    E -- Video --> F1[Send: Topic 2 video]
    E -- Article --> F2[Send: Topic 2 article]
    E -- Podcast --> F3[Send: Topic 2 podcast]
    E -- No pref --> F4[Send: Topic 2 article default]
    F1 --> G[Set content_format_nurture_completed = true]
    F2 --> G
    F3 --> G
    F4 --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when the account genuinely produces the same core content in more than one format (a topic covered as both a blog article and a video, for example), so the branch is a real choice, not a workaround.
  • UseUse when preference can be captured directly (a form field asking format preference) or inferred confidently (a contact who has only ever engaged with video content, never articles).
  • SkipDo not use this if the account only has one format available; there is nothing to branch on, and this becomes a placeholder step with no real effect.
  • SkipDo not infer preference from a single engagement; require a pattern (multiple visits to one format type) before setting the preference property, or ask directly on a form.
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.12 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 lead nurturing 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.