Outcome. When the primary internal champion at an account shows signs of having left the company, the associated account gets flagged for renewal risk and the deal owner is notified, instead of the departure going unnoticed until the renewal conversation itself.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-027
flowchart TD
A[Champion = true, email hard bounce reason populates] --> B[Set Champion Departure Suspected = true]
B --> C[Set company Renewal Risk Flag = true]
C --> D[Create high-priority verification task]
D --> E[Notify deal owner]
When to use it, when not to
- UseUse it on contacts explicitly marked as a champion, where an email hard bounce with a departure-style reason is the practical signal HubSpot can detect natively.
- UseUse it as an early warning, not a confirmed fact. A hard bounce suggests a departure; it does not confirm one, and this workflow's task step is there specifically to get a human to verify it.
- SkipDo not use it as the sole way departures are tracked. Sales conversations and account notes are often the first place a departure surfaces; the flag on a checkbox depends on that being logged.
- SkipDo not use it on contacts who are not marked as a champion. Any contact's email can hard bounce for unrelated reasons, and flagging renewal risk on every bounce would 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.4 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 renewal and expansion 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.
