The Workflow Library

Library / Lead nurturing / lead-nurturing-040

Content syndication / third-party source nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Contacts who arrive through a paid content syndication vendor get a nurture sequence that starts by re-establishing who the company is, since these contacts often do not remember opting in the way a direct-form lead does.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-040
flowchart TD
    A[lead_source_detail contains Content Syndication] --> B[Send: who we are]
    B --> C[Delay 2 days]
    C --> D[Send: your requested resource]
    D --> E[Delay 3 days]
    E --> F{Clicked either email?}
    F -- Yes --> G[Create task: engaged, follow up]
    F -- No --> H[Send: last note, low pressure]
    G --> I[Set syndication_nurture_completed = true]
    H --> I
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse for leads delivered by a content syndication or lead-gen vendor (gated asset placed on a third-party network, delivered as a batch of contact records).
  • UseUse this specifically because syndicated leads convert differently from direct-form leads: lower immediate recall of the brand, higher early unsubscribe risk, and a real need for a soft re-introduction before anything sales-facing.
  • SkipDo not use this for leads captured on the company's own site, even if a paid ad drove the click; those already know which brand they engaged with and belong in lead-nurturing-001 or lead-nurturing-002 instead.
  • SkipDo not skip the re-introduction email even under time pressure; sending a hard sales pitch as the first touch to a syndicated lead produces disproportionately high spam complaints.
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.8 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.