Outcome. The onboarding owner gets a fresh check-in task every week for as long as the onboarding ticket stays open, capped at a fixed number of cycles, instead of relying on memory to schedule regular touchpoints.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-013
flowchart TD
A[Ticket open, Next Check-in Date known] --> B[Delay until Next Check-in Date]
B --> C{Completed or Check-in Count >= 8?}
C -->|Yes| D[End]
C -->|No| E[Create check-in task]
E --> F[Increase Check-in Count]
F --> G[Set Next Check-in Date = +7 days]
G -.re-enrolls on property change.-> A
When to use it, when not to
- UseUse it when onboarding regularly runs long enough (several weeks or more) that a single kickoff task and a completion notice leave a gap in between with no prompted touchpoint.
- UseUse it when the team is comfortable with a workflow that loops on itself through a re-enrollment trick, this is a more advanced building pattern than most fiches in this category.
- SkipDo not use it for short onboarding (under two weeks), the overhead of building the loop is not worth it, use a couple of fixed-delay tasks instead, as in customer-onboarding-003.
- SkipDo not use it if the team already runs check-ins from a shared calendar cadence, adding a parallel task-based reminder would just be noise.
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.5 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.
