Outcome. A qualified contact lands in the sequence built for what they actually care about, instead of a generic one-size-fits-all outreach track.
Workflow map
Enrollment, branches and actions at a glance
sales-ops-043
flowchart TD
A[Lead status changes to Sales Qualified Lead] --> B{Owner and email known?}
B -->|No| C[Notify sales ops: missing owner/email]
B -->|Yes| D{Product interest = A?}
D -->|Yes| E[Enroll: Product A sequence]
D -->|No| F{Product interest = B?}
F -->|Yes| G[Enroll: Product B sequence]
F -->|No| H{Product interest = C?}
H -->|Yes| I[Enroll: Product C sequence]
H -->|No| J[Enroll: generic SQL sequence]
E --> K[Set Date entered sequence]
G --> K
I --> K
J --> K
When to use it, when not to
- UseUse it when more than one product or use case exists and a generic sequence undersells the specific value a contact is likely to respond to.
- UseUse it as the branching version of sales-ops-001, once you have more than one sequence ready and a reliable way to know which persona a contact belongs to.
- SkipDo not use it if
Product interestis inconsistently filled in; a contact with no known interest falls to a default branch, and if that happens often, your persona targeting is not actually working. - SkipDo not use it if you only have one sequence; there is nothing to branch between, use sales-ops-001 instead.
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.4 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.10 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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
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.
