Outcome. The minute a payment clears, the buyer becomes a customer in the CRM, the owner is told, a kickoff task and an onboarding ticket exist, and the welcome email goes out. Nobody has to watch a payments inbox to start the clock.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-049
flowchart TD
A[Contact has an associated payment with status Succeeded, Onboarding start date unknown] --> B{Contact owner known?}
B -->|Yes| C[Notify the contact owner]
B -->|No| D[Notify the onboarding lead]
C --> E[Set Lifecycle stage = Customer]
D --> E
E --> F[Stamp Payment received date and Onboarding start date]
F --> G[Set Onboarding status = Kickoff pending]
G --> H[Create kickoff To-do for the owner, due tomorrow]
H --> I[Create onboarding ticket at stage New]
I --> J[Delay 15 minutes]
J --> K[Send the welcome and next steps email]
When to use it, when not to
- UseUse it for self-serve or low-touch purchases where payment is the real start signal, not a signature or a manual stage change.
- UseUse it when onboarding today starts with somebody forwarding a receipt, which means it starts late and inconsistently.
- SkipDo not use it when onboarding should start at contract signature and payment lands weeks later. Trigger on the deal instead, see customer-onboarding-048.
- SkipDo not use it on recurring subscription charges without the guard filter in Enrollment, or every monthly renewal restarts onboarding for an existing customer.
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.9 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.11 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.6 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.
