Outcome. The moment a new customer's contact record shows a first product login, a custom coded action pulls a quick usage snapshot from the product and adds a login-based component to the onboarding health score, so "did they actually start using it" is measured, not assumed.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-027
flowchart TD
A[First Login Date known, Login Health Component unknown] --> B[Custom code: call product API]
B --> C[Set Login Health Component]
C --> D[Set Features Used At First Login]
D --> E{Custom code result_code = error?}
E -->|Yes| F[Alert Operations owner with error message]
E -->|No| G[End]
When to use it, when not to
- UseUse it when your product can write a login timestamp to a HubSpot contact property, either through an existing integration, a native webhook trigger, or a scheduled sync, and you want that event to feed into onboarding health scoring rather than sit unused.
- UseUse it alongside customer-onboarding-018, this fiche produces one
input component,
Login Health Component, meant to feed a broader health score, it does not replace the full score. - SkipDo not use it if your product has no way to report login events to HubSpot at all, there is no workaround inside HubSpot for detecting activity in a system it cannot observe, get the integration piece built first.
- SkipDo not use it if a simple "logged in yes/no" checkbox is enough, skip the custom code and just set a checkbox directly from the integration, save the custom code action for when you need the richer usage snapshot this fiche pulls back.
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.6 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.
