The Workflow Library

Library / Customer onboarding / customer-onboarding-048

Lifecycle stage update to customer post-signature

Customer onboardingContactMarketing Hub ProfessionalSimple~15 min to buildFull spec

Outcome. Every contact associated with a deal that closes won gets moved to the Customer lifecycle stage automatically, keeping reporting and list segmentation accurate without a manual step.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-048
flowchart TD
    A[Associated deal reaches Closed Won] --> B{Lifecycle stage already Customer?}
    B -->|Yes| C[No action]
    B -->|No| D[Set Lifecycle stage to Customer]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as a small, foundational piece almost every other fiche in this category and the marketing-ops category assumes is already in place, if lifecycle stage does not update reliably, filters built on Lifecycle stage = Customer elsewhere will quietly miss records.
  • UseUse it when a single deal's closed-won moment should apply to all of its associated contacts, not only the primary one.
  • SkipDo not use it if your portal already sets lifecycle stage to Customer through another mechanism (a native deal-to-contact lifecycle stage sync setting, if enabled), check Settings > Objects > Deals first to avoid two systems fighting over the same field.
  • SkipDo not combine this with customer-onboarding-014 into a single workflow, keep the nurture-removal logic there separate from this pure property update, so each is simple to audit on its own.
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.1 numbered action
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 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.