Skip to content
Automation Squad
HSMade to order

Notifications & alerts

HubSpot deal moves to Closed Won → announcement in Slack #wins

Every closed deal announced in Slack with the amount, the rep and the company.

A deal moves to Closed Won in HubSpot. Within a minute a message lands in the Slack channel you choose: deal name, company, amount, the rep who closed it and a link to the record. Other stage changes are ignored. For sales leaders who want wins seen as they happen rather than in Monday's pipeline review.

How it works

  1. H

    Trigger

    deal.propertyChange webhook fires when dealstage changes

    HubSpot

  2. if

    Step 1

    Keep only moves into Closed Won

    The new dealstage value in the webhook is compared with the Closed Won stage ID for your pipeline, set once in a workflow variable; anything else stops here.

  3. H

    Step 2

    Fetch the deal, its company and its owner

    Three lookups: the deal (name, amount, close date, pipeline), the company associated with it, and the owner record that turns hubspot_owner_id into the rep's name.

  4. S

    Step 3

    Post the win to the channel

    Sends a message to #wins, or any channel you choose, with deal name, company, amount, rep and a link to the deal in HubSpot.

What changes once it runs

  • A minute at most between the stage change in HubSpot and the post in Slack.
  • Only wins post; every other stage change is dropped at the first step.
  • Each message names the deal, company, amount and rep, with one link to the HubSpot record.
  • Custom pipelines work, because the Closed Won stage ID is a variable rather than a hard-coded value.

What you get

  • The n8n workflow export with the stage filter, the HubSpot fetch and the Slack post
  • Setup guide covering the developer app, its webhook subscription and install, the private app scopes and finding your Closed Won stage ID
  • A recorded walkthrough moving a test deal to Closed Won and watching the post arrive
  • One message template you can edit without touching the workflow logic
  • 30 days of email support for setup questions

Before you start

  • HubSpot: an account with deals in use (the free CRM is enough for the Deals API)
  • A free HubSpot developer account and app, installed into your HubSpot account, so n8n's HubSpot Trigger can subscribe to deal property changes
  • One HubSpot private app with read scopes for deals, companies and owners, used by the fetch step
  • Slack: a workspace where you can install an app with the chat:write scope, plus the channel

Built for

Questions before you buy

Can it post to a different channel per pipeline or per rep?
The channel is a value in the last step, and the setup guide shows how to switch it on pipeline ID or owner with one lookup table. Most teams start with a single #wins channel and split later.
Do I need a HubSpot developer account?
For the instant trigger, yes; it is free, and the guide covers creating the app, subscribing it to deal property changes and installing it into your account. The alternative is a HubSpot workflow that calls an n8n webhook, but the webhook action in workflows needs Operations Hub Professional or above.
Does it hand the deal to finance or onboarding?
No. This is the announcement only. Creating the invoice, the onboarding project or the customer record in another system is the job of the Sales & CRM hygiene packages, which can run alongside this one on the same trigger.
What happens if a deal is moved to Closed Won twice?
Each move into the stage fires the webhook, so a deal moved out and back in posts twice. If that bothers you, the guide shows a small addition that records posted deal IDs in the workflow's static data and skips any it has seen.
Is it instant on Make and Zapier too?
Make can subscribe to the same HubSpot webhook, so yes there. Zapier's HubSpot triggers poll, so on Zapier the post can lag by the polling interval of your plan; the message itself is the same.

Nearby on the shelf

Whole catalog