Get instant Slack notifications when a deal moves to a new stage in HubSpot. Include deal value, contact info, and the stage transition so your team always knows the pipeline status.
1. In HubSpot, go to Settings > Integrations > Webhooks. Create a new webhook subscription for the "deal.propertyChange" event, filtering on the "dealstage" property.
2. Set the webhook target URL to your automation platform's webhook endpoint. Complete the verification handshake if required.
3. In your automation platform, create a workflow triggered by the incoming HubSpot webhook.
4. Add a conditional node that checks whether the "propertyName" in the payload equals "dealstage". If not, skip the execution (this filters out other property changes).
5. Add a HubSpot API node to fetch the full deal details (name, amount, associated contacts) using the deal ID from the webhook payload. This enriches the notification.
6. Add a second conditional branch: if deal amount > $10,000, route to #big-deals channel; otherwise route to #pipeline-updates.
7. Add two Slack nodes (one per branch) that post a formatted message including: Deal Name, Amount, Previous Stage, New Stage, Owner, and a direct link to the deal in HubSpot.
8. Test by manually changing a deal's stage in HubSpot and verifying the Slack notification arrives within 15 seconds.
Troubleshooting
**Webhook not received:** HubSpot webhooks require HTTPS endpoints. If testing locally, use a tunnel service like ngrok. Verify the subscription is active in HubSpot Settings > Webhooks — inactive subscriptions show a paused icon.
**Stage names showing as IDs:** HubSpot sends deal stage as an internal ID (e.g., "appointmentscheduled"), not the display label. Map stage IDs to labels by calling the HubSpot Pipeline API (/crm/v3/pipelines/deals) and building a lookup table in your workflow.
**Missing deal details in notification:** The webhook payload only contains changed properties, not the full deal. Add a separate HubSpot "Get Deal" API call using the deal ID to fetch the amount, name, and associated contacts.
**Duplicate notifications:** HubSpot may retry webhook delivery if your endpoint responds slowly (>5 seconds). Ensure your workflow responds with HTTP 200 immediately. Add deduplication by storing the last processed event ID and skipping duplicates.