HubSpot Deal Stage → Slack (branching)
Fires on every HubSpot deal stage change. Normalizes the event, enriches the deal from HubSpot, then routes to a per-stage branch that adds the gate checks and checklists documented for that stage, and posts one card to #gtm-pipeline-signals. Covers Sales, Renewals and Partner pipelines.
Shared by Rez · Brainfish.
Remixed 0 times on Ballet.
How it works
- Parse the HubSpot webhook payload into a deduped list of dealstage change events — Reading the HubSpot stage-change event
- Look up each deal, its previous stage, owner, company, amount and the gate fields each stage cares about — Pulling the deal and its gate fields from HubSpot
- Send the transition down the branch for the stage it landed in — Choosing the branch for this stage
- Stage 0: the only documented gate is a non-event, so flag the discovery clock — Applying the Stage 0 branch
- Stage 1: check the documented economic-buyer gate — Applying the Stage 1 branch
- Stage 2: start the 24-hour Mutual Action Plan clock — Applying the Stage 2 branch
- Stage 3: post the seven trial pre-conditions that gate Stage 4 — Applying the Stage 3 branch
- Stage 4: set the trial clock and name the Day 7 and Day 14 checkpoints — Applying the Stage 4 branch
- Stage 5: post the Post-Trial artifact list, since the stage itself is undocumented — Applying the Stage 5 branch
- Closed Won: the missing gate on the required handover fields — Checking the Closed Won handover fields
- Closed Lost: capture the stage lost at and the reason the win/loss debrief asks for — Capturing the loss debrief fields
- Catch-all: Renewals, Partner, an unmapped stage, or nothing to report — Applying the catch-all branch
- Post the transition card plus the section its stage branch produced — Posting the stage change to Slack
Sample output
Created by AI. Fictional demo data — not a customer run.
Remix this playbook