Outcome. A contact always sits on exactly one stage-tracking static list matching their current lifecycle stage, and gets removed from every other stage list automatically, keeping list-based reporting and sends accurate with no manual list cleanup.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-012
flowchart TD
A[Lifecycle stage changes] --> B{Which stage?}
B -->|Lead| C[Add Active - Lead, remove from others]
B -->|MQL| D[Add Active - MQL, remove from others]
B -->|SQL| E[Add Active - SQL, remove from others]
B -->|Opportunity| F[Add Active - Opportunity, remove from others]
B -->|Customer| G[Add Active - Customer, remove from others]
B -->|Other stage| H[No action or extend]
When to use it, when not to
- UseUse when a reporting tool, sales playbook, or campaign build needs a static list per lifecycle stage specifically, not a live filter.
- UseUse when you need membership history preserved (who was ever on the "Active - MQL" list matters even after they move on) in a way a dynamic list filtered on current lifecycle stage cannot show.
- SkipDo not build this if a simple active (dynamic) list filtered
directly on
Lifecycle stagealready meets the need. That approach needs no workflow at all and stays correct automatically; only add this workflow when something beyond current lifecycle stage matters, such as combining it with other criteria or needing a static snapshot. - SkipDo not use this as a substitute for the lifecycle stage property itself in reporting. The lists exist for list-based tools and sends, not as the source of truth for stage.
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.1 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.27 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 marketing ops 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.
