The Workflow Library

Library / Lead nurturing / lead-nurturing-014

Multi-asset drip branched by which lead magnet was downloaded

Lead nurturingContactMarketing Hub ProfessionalIntermediate~40 min to buildFull spec

Outcome. A contact who downloads any one of several gated assets gets a short follow-up built around that specific topic, instead of one generic sequence regardless of what they actually downloaded.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-014
flowchart TD
    A[Form submission: Guide A, B, or C] --> B{lead_magnet_downloaded?}
    B -- Guide A --> C[Follow-up 1] --> D[Delay 3d] --> E[Follow-up 2] --> F[Set completed = true]
    B -- Guide B --> G[Follow-up 1] --> H[Delay 3d] --> I[Follow-up 2] --> F
    B -- Guide C --> J[Follow-up 1] --> K[Delay 3d] --> L[Follow-up 2] --> F
    B -- blank/unrecognized --> M[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when 3 or more distinct lead magnets exist and each has a genuinely different topic worth its own 2-email follow-up.
  • UseUse hidden form fields, one static value per landing page or form, as the simplest way to capture which asset was downloaded without extra tooling.
  • SkipDo not use it for near-identical assets, such as two versions of the same guide. Branch only where the topic difference is real enough to justify separate emails.
  • SkipDo not enroll the same contact a second time for a different lead magnet while still mid-track on the first, without deciding how the two content tracks should interact, see Known pitfalls.
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.2 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.14 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.