Outcome. Every time the onboarding ticket moves to a new stage, the right people get notified and a timestamp is kept, so the ticket pipeline created in customer-onboarding-005 actually reflects live progress instead of sitting untouched after creation.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-011
flowchart TD
A[Ticket in Onboarding pipeline changes stage] --> B[Set Current Milestone Started Date]
B --> C{Stage = In Progress?}
C -->|Yes| D[Notify ticket owner: kickoff done]
C -->|No| E{Stage = Blocked?}
D --> E
E -->|Yes| F[Notify CS manager + create unblock task]
E -->|No| G{Stage = Completed?}
F --> G
G -->|Yes| H[Set Onboarding Completion Date, notify owner + rep]
G -->|No| I[End]
When to use it, when not to
- UseUse it once customer-onboarding-005 is in place and stages exist, this fiche is the workflow that reacts to stage changes, it does not create the pipeline itself.
- UseUse it when the team wants a record of how long onboarding sat in each stage, useful input for customer-onboarding-012 and customer-onboarding-035.
- SkipDo not use it if the pipeline has only two stages (open and closed), the branching adds little value at that point, a simple closed-ticket notification is enough.
- SkipDo not use it if stage changes happen too rarely to be a meaningful signal, for very long or ad hoc onboarding projects a manual status update might serve better.
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.5 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
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.
