Outcome. A failed payment, chargeback, or cancellation reported by the external billing system flags the account as at risk within minutes, instead of the finance team's monthly dunning report being the first place anyone notices.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-045
flowchart TD
A[External Billing Signal changes to a non-None value] --> B{Notified in the last 24h?}
B -->|Yes| Z[No action, avoid duplicate alert]
B -->|No| C[Set Renewal Risk Flag = true]
C --> D[Set Billing Signal Notified At = now]
D --> E[Create task for owner]
E --> F[Notify owner]
When to use it, when not to
- UseUse it when the billing system (Stripe, Chargebee, a homegrown billing service, or similar) can push events out to a receiving endpoint the moment they happen.
- UseUse it as the fast, event-driven counterpart to
renewal-expansion-028's payment-status workflow, which assumes a
Payment Statusproperty is already kept current by some existing sync; this fiche documents how that property actually gets updated in near real time. - SkipDo not use it if the billing system has no outbound webhook or event-push capability at all; in that case, a periodic pull (see renewal-expansion-044's pattern, adapted to a billing API) is the realistic alternative, not a workflow waiting for something that will never arrive.
- SkipDo not use it to auto-cancel or auto-downgrade an account; this fiche only raises a flag and a notification, since acting on a single billing event without human review risks reacting to a transient card decline rather than a real churn signal.
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.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.
