Outcome. A contact who came in through a specific partner or referral source gets a nurture sequence that acknowledges that relationship, instead of the same generic messaging used for direct organic or paid traffic.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-027
flowchart TD
A[Filter: partner source known, not customer] --> B[Send: thanks via partner, personalized]
B --> C[Delay 3 days]
C --> D[Send: getting started, partner-aware]
D --> E[Set partner_nurture_completed = true]
When to use it, when not to
- UseUse when partner-sourced volume is high enough, and the relationship valuable enough, that co-branded or partner-aware messaging is worth building and maintaining.
- UseUse it to strengthen the referral relationship and shorten time to trust, not as a replacement for whatever nurture track the contact's actual funnel stage calls for.
- SkipDo not use it if partner attribution data is unreliable. A branch fed by mostly-guessed source data undermines the whole point of a partner-aware message.
- SkipDo not build a separate track per partner if there are more than 3 or 4 active partners; a shared "referred by a partner" message that inserts the partner name as a token scales better than a fully separate branch each.
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 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.
