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 deal with a discount over the limit waits for approval: a Neblex task goes to a named approver, and the link reaches them in Slack
• A deal room channel is created for opportunities over a size, with the AE, SE, and manager invited and the deal summary posted
• Messages in the deal room are logged to the HubSpot deal as notes by a scheduled flow, 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

Started by the polled deal trigger, the run waits on an approval task whose link is posted to the approver in Slack.

1. 1
   Trigger: HubSpot New or updated deal, polled on the schedule you set, carrying dealId, amount, dealstage, hubspot_owner_id, and discount_percent.
2. 2
   Gate: if discount_percent is at or below the threshold for the deal's tier, do nothing. Otherwise continue.
3. 3
   Resolve approver: look up the deal owner's manager from a team map, and the manager's Slack user with Find user by email.
4. 4
   Ask: a Wait for form step creates the approval task for the manager with the deal name, amount, list vs net, and discount, a due time, and an escalation flow. A Slack message to the manager carries a button that opens the task.
5. 5
   On approve: set HubSpot deal properties discount_approved_by and discount_approved_at, post a confirmation in the channel, and let the deal proceed.
6. 6
   On 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 waits for an approver's decision in a Neblex task, with the link sent in Slack. (HubSpot to Slack)
• Deal room. Opportunities over a size get a channel with the AE, SE, and manager, and the deal summary posted. (HubSpot to Slack)
• Messages to notes. A scheduled flow reads new messages in each deal room and writes them to the deal as timestamped notes with the author. (Slack to HubSpot)

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

• Run history. Every alert, approval request, and decision is a run with the deal, the decider, and the fields written. A failed run can be replayed from the step that failed.
• Approval steps. The discount gate is a Wait for form task. The run holds until a named approver acts or the task times out, and the decision and decider are recorded.
• 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.