Outcome. Every time fresh product usage data lands on a contact, a checklist of core feature adoption milestones updates automatically, giving CS a concrete view of what a new customer has actually turned on, not just whether they logged in once.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-041
flowchart TD
A[Usage Data Last Synced changes, Product User Id known] --> B[Custom code: query usage API, set feature checkboxes]
B --> C{Features Adopted Count = 3?}
C -->|Yes| D[Set checklist complete, add to Fully Adopted list]
C -->|No| E[No further action]
When to use it, when not to
- UseUse it once customer-onboarding-027 is in place (usage data reaching HubSpot at all) and you want more than a single login signal, a small set of specific feature milestones.
- UseUse it when your product can report which of a short list of core features a user has touched, through its own API or an existing sync tool.
- SkipDo not use it if you cannot yet get usage data into HubSpot at all, build customer-onboarding-027 first.
- SkipDo not use it for more than a handful of features, this pattern does not scale well past 4 or 5 checklist items without becoming unreadable, use a percent-complete calculated property instead for a longer list (see customer-onboarding-026 for the pattern, adapted to contact-level usage).
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.8 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.9 numbered actions
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, 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.
