The Workflow Library

Library / Customer onboarding / customer-onboarding-014

Remove contact from sales nurture on becoming customer

Customer onboardingContactMarketing Hub ProfessionalSimple~20 min to buildFull spec

Outcome. The moment a contact's lifecycle stage becomes Customer, they stop receiving pre-sale nurture emails meant for prospects, and they are added to a suppression list so future nurture sends skip them automatically.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-014
flowchart TD
    A[Lifecycle stage becomes Customer] --> B[Unenroll from active nurture workflows]
    B --> C[Add to Exclude From Nurture list]
    C --> D[Set Nurture Suppressed Date]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it whenever prospect nurture workflows exist and there is no current mechanism stopping a contact from receiving them after they buy.
  • UseUse it as a small, standalone fiche that pairs well with any welcome or onboarding sequence, such as customer-onboarding-004.
  • SkipDo not use it if lifecycle stage is not a reliable signal in your portal, for example if it is set manually and inconsistently, fix that data quality issue first (see the data-quality category).
  • SkipDo not use it if nurture workflows already exclude customers via their own enrollment filters, this fiche is redundant in that case, though the suppression list can still help with future workflows.
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.3 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

or the customer onboarding 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.