Outcome. The sales channel gets a Slack message the moment a deal that was previously Closed Lost moves back into an open stage, so a reactivated opportunity is visible without someone noticing it by chance in a pipeline view.
Workflow map
Enrollment, branches and actions at a glance
reporting-alerts-048
flowchart TD
A[Deal stage changes to Closed Lost] --> B[Set deal_was_closed_lost = true]
C[Deal stage changes to an open stage] --> D{deal_was_closed_lost = true?}
D -->|no| Z[Exit, ordinary progression]
D -->|yes| E[Send Slack: deal reactivated]
E --> F[Set deal_was_closed_lost = false]
When to use it, when not to
- UseUse it on a portal where lost deals occasionally get reopened, a prospect comes back, a budget frees up, and the team wants immediate visibility rather than finding out at the next pipeline review.
- UseUse it to trigger a manual sanity check on reactivated deals, confirming the reopening was intentional and not a misclick.
- SkipDo not use it if deal reactivation is a routine, high-volume part of this portal's sales motion (for example a subscription renewal pattern that naturally reopens deals); in that case the alert becomes routine noise rather than a meaningful flag.
- SkipDo not treat this as a data-quality check on WHY the deal was reactivated; it only flags THAT it happened.
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.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.5 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.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.
