Outcome. A new customer who has not logged into the product a set number of business days after onboarding started triggers an alert to their CS owner, catching silent non-adoption before it becomes a churn risk nobody noticed.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-028
flowchart TD
A[Onboarding Start Date known, no First Login Date yet] --> B[Delay 5 business days]
B --> C{Still no First Login Date?}
C -->|Yes| D[Alert Onboarding Owner]
D --> E[Create outreach task]
E --> F[Set No Login Alert Sent = true]
C -->|No| G[End, contact logged in during the wait]
When to use it, when not to
- UseUse it when your product can report login activity to HubSpot (see
customer-onboarding-027 for the scoring version of this dependency), and
Onboarding Start Dateis reliably set at the start of the relationship. - UseUse it as an early, blunt signal, not a full health score, this fiche answers one question only: has this person logged in at all.
- SkipDo not use it if
First Login Dateis not populated reliably in your portal, this workflow will alert on every contact, including ones who did log in but whose activity was never synced, fix the integration first. - SkipDo not use it for contacts who are not the primary product user (a
billing contact who never needed to log in), scope enrollment to a
Primary Product Userflag if your customer has more than one contact.
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.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.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.
