---
name: hubspot-slack-integration
description: Connect HubSpot and Slack: what syncs, which editions carry it, the setup order, and the failures to expect. Covers activities, messages, deals, companies. Use when the user wants to set up, audit or troubleshoot HubSpot and Slack together, or asks why data is not moving between them.
---

# HubSpot and Slack

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** HubSpot Professional or Enterprise to create a channel from a workflow

**What moves:** activities, messages, deals, companies, events only.
**How it is built:** native, marketplace app. **Effort:** minutes.

## The short version

Install it in five minutes, then meet the gap within a week. The workflow action sends to a channel you pick at design time. There is no built-in option to send to the channel associated with the deal that triggered the workflow, even when that association exists on the record. Teams solve it with one channel per segment, or by routing through n8n and calling the Slack API directly.

## What works, in which kind of channel

Rows: HubSpot tier. Columns: Kind of channel. Slack sets no plan gate on this integration, so the grid that matters is not editions: it is which HubSpot tier you hold against the kind of channel you are sending to.

| HubSpot tier | Public channel | Private, app added | Slack Connect |
|---|---|---|---|
| Free or Starter | Notifications and associations | Notifications and associations | Nothing |
| Professional | Plus workflow actions | Plus workflow actions | Nothing |
| Enterprise | Plus workflow actions | Plus workflow actions | Nothing |

- **Nothing.** Slack Connect channels, the shared ones with a customer in them, are outside this integration entirely. Nothing logs and nothing can be associated.
- **Notifications and associations.** Personal notifications, record-to-channel associations with per-activity choices, live chat routing and slash commands. All of it without a workflow, and without Professional.
- **Plus workflow actions.** The same, plus the Slack workflow action and workflow-created channels, which is where notifications stop being per record and become a rule.

Counted off that grid, of nine pairings: three give you nothing, two give you notifications and associations, four give you plus workflow actions.

The free column is wider than people expect: the association, the notifications and the slash commands are all there, and Professional buys you the ability to make them a rule rather than a habit.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Workflow to channel | One way, out | Send Slack message is a workflow action. Any trigger can fire it: score threshold, stage change, deal gone quiet. |
| Record to channel association | Two-way sync | A deal or company record can be associated with a Slack channel, with per-activity-type notifications. |
| Channel creation | One way, out | A workflow can create a channel and associate it with the record. HubSpot Professional or Enterprise. |
| Slash commands | One way, in | Look up records and log activity from Slack, so the CRM gets updated by people who will not open it. |

## Which field lands where

There are no fields to map here. What there is instead is a set of surfaces, each with its own rule about where a message can go.

| In HubSpot | In Slack | What to know about the match |
|---|---|---|
| Workflow action | A fixed channel you pick | Static only. There is no option to send to the channel associated with the current record, which is the most requested thing on this pair. |
| Record association | The channel attached to that deal or company | Public channels, and private ones where the HubSpot app is a member. Activity types are chosen per association rather than globally. |
| Live chat and help desk conversation | An inbox channel | Routed per inbox, and a reply sent in the Slack thread still logs into the HubSpot inbox. |
| Personal notification | A direct message | Per user, configured by that user, and invisible to an admin who assumes they set it up for the team. |
| Slash command | A record lookup or a logged activity | The one direction that writes back, so the CRM gets updated without anybody leaving the conversation. |

**What does not cross:**

- The channel associated with the record, as a workflow destination. Documented as unsupported, with branch-per-channel workflows as the workaround.
- A channel association on a merged record, unless it was on the primary record. The association follows the primary, so pick the primary deliberately or attach the channel to it first.
- Conversations in a Slack Connect channel with a customer. Nothing in this integration logs them.

## Connect it, in this order

**Who has to do it:** A HubSpot admin for the app and the workflows, and whoever owns the Slack workspace for the app approval.
**How long:** Twenty minutes to connect it. The rest of the day goes on deciding what should notify.

### 1. Install the HubSpot app in Slack

*Where:* HubSpot: Marketplace, Slack

Standard marketplace install and a Slack authorisation. If your workspace requires admin approval for apps, that approval is the long pole rather than anything in HubSpot.

### 2. Add the HubSpot app to every private channel you intend to use

*Where:* Slack: the channel itself

Records can only be associated with public channels, and with private channels where the HubSpot app is already a member. A private deal room without the app in it simply will not appear in the picker, which reads as a bug and is not one.

### 3. Turn on personal notifications

*Where:* HubSpot: Settings, Notifications, Other apps

Toggle Slack on under How you get notified, then pick what you want under What you get notified about. This is per user rather than account-wide, so a rollout means telling people to do it rather than doing it for them.

### 4. Route live chat and help desk conversations to a channel

*Where:* HubSpot: Connected Apps, Slack, General settings

Under Bring conversations to Slack, switch on the inboxes whose conversations should appear. Replies can go back through the Slack thread and still log in the inbox, which is the part that makes it worth doing rather than just an alert.

### 5. Associate channels with the records that matter

*Where:* A company or deal record, Slack card in the right sidebar

Associate an existing channel or create one from the record, choosing visibility, a description and exactly which activity types notify. Doing this per record is deliberate: it is the only way to get a notification into the room where the deal is discussed.

### 6. Build the workflow notifications last, and point each one at a fixed channel

*Where:* HubSpot: Workflows

Workflows need Professional or Enterprise. The Slack action sends to a static, pre-selected channel, so if you want the message to land in the deal's own room you either use the record association above or branch the workflow once per channel.

The order matters in one place only, and it is the second step: adding the app to the private channels first turns the association step from debugging into picking from a list.

## How to check it worked

- Associate a test deal with a private channel. If it is missing from the dropdown, the app is not in that channel.
- Trigger one workflow notification and check it lands in the channel you named rather than in a default one.
- Reply to a live chat from the Slack thread and confirm the reply appears in the HubSpot inbox against the same conversation.
- Merge two test records where only one has a channel association, and confirm you know which association survives before you do it to a real deal.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| A private channel does not appear when associating a record | The HubSpot app is not a member of it. Associations only work with public channels and private channels the app has been added to. | Add the app in that Slack channel, then refresh the record. No HubSpot setting substitutes for it. |
| The workflow posts to the wrong room | The Slack workflow action takes a static channel. It cannot resolve the channel associated with the record being processed. | Use the record association for per-deal messages, or branch the workflow and give each branch a fixed channel. The second only scales to a handful of channels. |
| A deal lost its channel after a merge | The Slack channel association comes from the primary record in a merge. | Associate the channel with the record you will keep as primary before merging, or choose the record that already has it as the primary. |
| Notifications arrive for one person and not the team | Personal notification settings are per user, under Settings, Notifications, Other apps. | Tell people to turn their own on. An admin cannot do it for them, which makes this a rollout communication rather than a configuration task. |
| The channel is noisy and now everybody has muted it | Every activity type was ticked when the channel was associated. | Re-open the association and uncheck everything that is not acted on. A muted channel is worse than no channel, because the team believes alerting works. |
| Nothing from a shared channel with a customer is in the CRM | Slack Connect conversations are not covered. | There is no setting. Either keep deal discussion in an internal associated channel, or accept that the customer-facing thread is outside the record. |

## What breaks, from the vendors' own docs

- **The workflow action cannot follow the record.** The Slack workflow action sends to a static, pre-selected channel. There is no built-in option to send to "the channel associated with this deal", even with the association already on the record. This is the single most requested thing on this pair and it is not there.
- **Channel creation is gated.** Using a workflow to create a Slack channel automatically requires a Professional or Enterprise subscription. Associating an existing channel by hand does not, which is the workaround at lower tiers.
- **Notifications are a volume problem before they are a feature problem.** The integration will happily post every activity type you tick. A channel that fires forty times a day gets muted, and a muted channel is worse than no integration because everyone believes the alerting works.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

**Rules that will cost you time if you skip them:**

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- HubSpot knowledge base: manage your notifications in Slack: https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack
- HubSpot community: Slack notification to the channel associated with the deal: https://community.hubspot.com/t5/CRM/Slack-notification-in-Workflows-Send-to-the-channel-associated/m-p/1177859
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
