Outcome. The moment a contact books a meeting, every nurture track they are in gets a single, shared signal to stop, so no one keeps getting drip emails while a real conversation is already scheduled.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-013
flowchart TD
A[Meeting booked event] --> B[Set nurture_paused_reason = Meeting Booked]
B --> C[Add to list: Suppressed - meeting booked]
When to use it, when not to
- UseUse as a small, shared utility workflow that every other nurture fiche in this category references, instead of building the same exit logic separately in each one.
- UseBuild this the same day a meetings tool or a "book a meeting" form goes live, before any nurture workflow does, so the suppression list and property already exist when nurture starts.
- SkipDo not treat this as a substitute for lead-routing. Booking a meeting should also trigger assignment or notification logic; that lives in lead-routing, not here.
- SkipDo not skip wiring the unenrollment trigger into each individual nurture workflow. This workflow alone does not reach into other workflows and stop them, see Steps and 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.2 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.
