Outcome. Once a month, customer success leadership gets an email showing how many customer accounts fall into each health score band, so account health trends are visible at a portfolio level without opening each company record.
Workflow map
Enrollment, branches and actions at a glance
reporting-alerts-039
flowchart TD
A[Monthly schedule: first business day, 08:00] --> B[Report: active customers grouped by health score band]
B --> C[Sorted healthiest to least healthy]
C --> D[Email sent to CS leadership distribution list]
When to use it, when not to
- UseUse it on a portal that already populates a customer health score property (native HubSpot customer health scoring, or a custom scoring property built and maintained elsewhere), and where leadership wants a monthly distribution view rather than a per-account check.
- UseUse it to spot a shift in the overall portfolio, for example a growing share of accounts sliding into an at-risk band, month over month.
- SkipDo not use this fiche to build the health score itself. It assumes a health score property already exists and is kept current; if it does not exist yet, that scoring logic needs to be designed and built first.
- SkipDo not use it as a substitute for individual account reviews. A distribution summary tells leadership WHERE the portfolio sits, not which specific account needs attention today.
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.2 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.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 reporting and alerts 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.
