Skip to content

Slack alert: previously Closed Lost deal reactivated (visibility notification)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal4 stepsUpdated for HubSpot seat pricing
OutcomeThe 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 mapreporting-alerts-048
Deal stage changes to Closed Lost leads to Set deal_was_closed_lost = true. Deal stage changes to an open stage leads to deal_was_closed_lost = true?. deal_was_closed_lost = true? leads to no: Exit, ordinary progression; yes: Send Slack: deal reactivated. Send Slack: deal reactivated leads to Set deal_was_closed_lost = false. no yes Deal stage changes to Closed Lost Deal stage changes to an open stage Set deal_was_closed_lost = true deal_was_closed_lost = true? Exit, ordinary progression Send Slack: deal reactivated Set deal_was_closed_lost = false
Deal stage changes to Closed Lost leads to Set deal_was_closed_lost = true. Deal stage changes to an open stage leads to deal_was_closed_lost = true?. deal_was_closed_lost = true? leads to no: Exit, ordinary progression; yes: Send Slack: deal reactivated. Send Slack: deal reactivated leads to Set deal_was_closed_lost = false. no yes Deal stage changes to Closed Lost Set deal_was_closed_lost = true Deal stage changes to an open stage deal_was_closed_lost = true? Exit, ordinary progression Send Slack: deal reactivated Set deal_was_ closed_lost = false

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use 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.
  • Use it to trigger a manual sanity check on reactivated deals, confirming the reopening was intentional and not a misclick.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do not treat this as a data-quality check on WHY the deal was reactivated; it only flags THAT it happened.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 5 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library