Connect HubSpot to Slack

Deals live in HubSpot. The team talks in Slack. Without a link, reps post "just closed a big one" by hand, managers find out about a deep discount after it is quoted, and the useful context that gets shared in Slack never makes it back to the CRM.

• Deal stage changes and new deals over a value threshold post to the pod's channel with amount, stage, owner, and a link, no manual sharing
• A quote or deal with a discount over the limit pauses and asks a named approver in Slack to approve or reject before it moves on
• A deal room channel is created for opportunities over a size, with the AE, SE, and manager added and the deal summary pinned
• A reply in the deal room is written back to the HubSpot deal as a note, so the CRM keeps the context

The approval flow most teams turn on first.

A deal discounted past the limit waits for a yes or no in Slack

Triggered on the HubSpot property change, the run pauses until the Slack action.

1. 1Trigger: HubSpot deal property discount_percent changed, carrying dealId, amount, dealstage, hubspot_owner_id, and the associated company.
2. 2Gate: if discount_percent is at or below the threshold for the deal's tier, do nothing. Otherwise continue.
3. 3Resolve approver: look up the deal owner's manager from a team map, and the manager's Slack user ID by email.
4. 4Ask: Slack Send message to the manager (or a #deal-approvals channel) with the deal name, amount, list vs net, discount, and Approve / Reject buttons. The run pauses here.
5. 5On approve: set HubSpot deal property discount_approved_by and discount_approved_at, post a confirmation in the channel, and let the deal proceed.
6. 6On reject or timeout: set discount_status to "Rejected", create a task for the owner to revise, and post the reason back to the deal as a note.

The starting map for the HubSpot deal alert and the approval write-back.

• Deal alerts. Stage changes and new deals over a threshold post to the pod channel with amount, stage, owner, and a link. (HubSpot to Slack)
• Discount approval. A discount past the limit pauses the deal for an approver's decision in Slack. (HubSpot to Slack)
• Deal room. Opportunities over a size get a channel with the AE, SE, and manager, and the deal summary pinned. (HubSpot to Slack)
• Reply to note. A message in the deal room is written back to the deal as a timestamped note with the author. (Slack to HubSpot)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every alert, approval request, and decision is an event log entry with the deal, the actor, and the fields written. Replay without re-posting to Slack.
• Approval steps. The discount gate is a first-class pause. The run holds until a named approver acts or it times out, and the decision and actor are recorded on the deal.
• Scoped access. HubSpot uses a private app scoped to deals, companies, owners, and engagements. Slack uses a bot token with chat, channels, and users scopes.
• Environments. Build against a HubSpot test account and a Slack test workspace, then promote the same flow to production.