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

# Salesforce and Slack

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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:** Sales Cloud, plus a Slack workspace you can install apps into

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

## The short version

Salesforce owns Slack, and this is the only integration in the directory where that is true. It shows in the depth: record search and updates from inside Slack, channel-to-record association, alerts driven by Flow, and Slack as a surface for approvals rather than only for notifications. It does not show in the setup, which is still a Salesforce admin project rather than a toggle.

## Check the plan before anything else

Rows: Salesforce edition. Columns: Slack plan. Most of the reports that this integration is broken are a pairing from this grid that was never going to work.

| Salesforce edition | Free | Pro or Business+ | Enterprise Grid |
|---|---|---|---|
| Professional | Check API access first | Check API access first | Check API access first |
| Enterprise | One org | Up to 21 orgs | Up to 21 orgs |
| Unlimited or Performance | One org | Up to 21 orgs | Up to 21 orgs |

- **Check API access first.** Salesforce does not name Professional on the permission-scopes page for the Salesforce for Slack app, which lists Enterprise, Performance, Unlimited and Developer, and the older Slack-built Salesforce app documents an API Access add-on as a requirement on Professional. Price that add-on before you plan the project, and confirm it against your own contract rather than against a feature page.
- **One org.** One Salesforce org paired with this workspace, which is the whole feature set for most companies. The limit is on how many orgs you pair, not on what the pairing does.
- **Up to 21 orgs.** The same connection plus up to 20 additional Salesforce orgs, which is what a group running more than one org needs.

Counted off that grid, of nine pairings: three give you check API access first, two give you one org, four give you up to 21 orgs.

The gate on this pair is on the Salesforce side and the ceiling is on the Slack side, which is why "do we have the right plan" gets answered wrong so often: the two halves are bought by different people.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Record search and updates | Two-way sync | Find and edit Salesforce records from Slack, so updates happen where the conversation is. |
| Flow to channel | One way, out | Flow can post to Slack on any record event, which is the general-purpose alerting path. |
| Channel to record | Two-way sync | Channels associated with opportunities or accounts, so the deal room and the record are the same thing. |
| Approvals | Two-way sync | Approval requests actioned in Slack and written back, which is the feature that changes cycle time. |

## Which field lands where

This pair maps people and surfaces rather than field to field. The account mapping decides who can do anything at all, and the object mapping decides what a channel can be attached to.

| In Salesforce | In Slack | What to know about the match |
|---|---|---|
| Slack member | Salesforce user | Matched on Email or SAML NameID, whichever you picked at setup, or mapped by hand or CSV. An unmapped member gets none of the app, which looks like a broken install rather than a missing row. |
| Opportunity | Channel, with the record attached | The deal room and the record become the same thing, which is the feature most teams are actually buying. |
| Account | Channel, with the record attached | Same mechanism at account level, for teams that run a named-account motion rather than a deal motion. |
| Approval request | Slack message with the actions on it | Actioned in Slack and written back to the record, which is the half that changes cycle time rather than visibility. |
| Any record event, through Flow | A channel or direct message | The general-purpose path. Flow decides what fires, so anything you can express in Flow you can send. |

**What does not cross:**

- Slack Connect channels. Sales Cloud for Slack does not support them, so a shared channel with a customer in it is outside this integration.
- Government Cloud orgs. Salesforce documents that you cannot connect Slack to one.
- More than one org per workspace on Slack Free. The connection itself is available on every Slack plan, but additional orgs are not.

## Connect it, in this order

**Who has to do it:** A Slack workspace owner or admin and a Salesforce system admin, passing it back and forth. Neither can finish it alone.
**How long:** An afternoon for the connection and the permission sets, longer if you are activating flows.

### 1. Request the connection from the Slack side

*Where:* Slack: workspace name, Tools and settings, Manage Salesforce Organizations

Click Connect Salesforce Org, enter your org URL, and choose whether accounts map on Email or on SAML NameID. Pick the mapping field deliberately: it decides which Slack member becomes which Salesforce user, and changing your mind later means remapping everybody.

### 2. Approve it from the Salesforce side

*Where:* Salesforce Setup: Platform tools, Slack, Manage Slack Connection

Select the same mapping field under User Configuration, accept the terms, and click Approve. The admin doing this needs Modify All Data and the Connect Salesforce with Slack permission.

### 3. Activate the pending connection back in Slack

*Where:* Slack: Manage Salesforce Organizations

Select the pending connection, review it and click Activate. Until this third step, the first two look finished and nothing works, which is where most of the confusion on this pair starts.

### 4. Decide how members get mapped

*Where:* Slack: Manage Salesforce Organizations, Users tab

Automatic mapping matches on the field you chose. Otherwise add people individually or by CSV, and export the User Mapping CSV from the same tab to see who is still unmatched. Anyone on a Unified Employee license can only be mapped automatically, so turn automatic mapping on if your org uses it.

### 5. Give each user the Salesforce permission they need

*Where:* Salesforce Setup: permission sets

Every Slack user, including the workspace owner who installs the app, needs a permission set on their Salesforce licence carrying Connect Salesforce with Slack. Using Sales Cloud for Slack needs the Slack Sales User permission on top. If the licence does not support the permission, Salesforce throws an error when you try to assign the set rather than when the user tries to work.

### 6. Enable the app and its features in Salesforce

*Where:* Salesforce Setup

Turn on Slack apps, then turn on Sales Cloud for Slack and configure the features you want. Users who will create sales channels from Slack need access to the Swarms object; creating them from Salesforce takes further setup.

### 7. Have your Slack admin install the app in the workspace

*Where:* Slack App Directory

Installing for everyone needs administrative access to the Slack account. Some workspaces only let admins authorise apps at all, and some require admin approval per request, so check which of those you are before promising a date.

### 8. Activate the notification flows you actually want

*Where:* Salesforce Flow Builder

Notifications are flows, and they ship as templates you copy and activate. Two feed channels are predefined, Deals to Watch and Deals Won. Editing a copied flow after saving it can stop the notification firing or leave its text describing something it no longer does, and Deals to Watch is the one flow Salesforce documents as safe to customise.

The shape to notice is the handshake: request, approve, activate, across two admin consoles. Everything after that is permission sets and flows, which is ordinary Salesforce project work rather than anything Slack-specific.

## How to check it worked

- Check the connection reads as active in Manage Salesforce Organizations rather than pending. A pending connection is the single most common cause of "we installed it and nothing happened".
- Export the User Mapping CSV and count the unmapped members. Those people will see nothing, and they will report it as the integration being broken.
- Have one non-admin open a record from Slack and change a field. That tests the permission set rather than your own access.
- Trigger one activated flow deliberately and confirm the message arrives in the channel you expected rather than in a default one.

## 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 |
|---|---|---|
| Everything is set up and nothing happens in Slack | The connection is still pending. It takes three moves in two consoles, and the Slack-side Activate is the one people miss because the first two steps report success. | Open Manage Salesforce Organizations in Slack, select the connection and click Activate. Confirm it reads active before you debug anything else. |
| The app works for admins and not for the team | Each user needs a permission set on their Salesforce licence carrying Connect Salesforce with Slack, and Sales Cloud for Slack needs Slack Sales User on top. An admin testing with their own access never sees this. | Assign the permission sets, then test as a non-admin. If assigning the set throws an error, the user licence does not support the permission, which is a licensing answer rather than a configuration one. |
| Some members are not matched to a Salesforce user | Automatic mapping matches on Email or SAML NameID only. Anyone whose Slack email differs from their Salesforce username falls out, and Unified Employee licence users cannot be mapped any other way. | Export the User Mapping CSV from the Users tab, map the stragglers individually or by CSV, and switch automatic mapping on if you use Unified Employee licences. |
| Features fail intermittently for no visible reason | Salesforce IP restrictions. Slack documents them as a cause of features not working as expected, which presents as flakiness rather than as a permission error. | Check the org IP restrictions against the Slack connection before spending a day in debug logs. |
| The connection broke after a Salesforce change | The org URL changed. The stored connection still points at the old one. | Update the connection in Slack with the new org URL. |
| A notification stopped firing, or says the wrong thing | A copied flow template was edited after it was saved. Salesforce documents that this can stop the notification or leave its text describing behaviour it no longer has. | Re-copy the template and apply your change in the one place it is supported, the Deals to Watch feed channel flow, or keep the edit outside the template. |
| A shared channel with a customer gets none of this | Sales Cloud for Slack does not support Slack Connect channels. | Keep the record-linked channel internal and treat the customer channel as a separate surface. There is no setting that changes this. |

## What breaks, from the vendors' own docs

- **Still a Salesforce admin project.** Common ownership has not made this a self-serve install. Flow work, permission sets and a change window are all still required.
- **Alert volume is the real constraint.** The same failure mode as every CRM-to-Slack pair: a channel that fires constantly gets muted, and a muted channel is worse than no alerting because everyone assumes it works.
- **The connection is a three-step handshake across two consoles.** Slack requests it, a Salesforce admin approves it, and Slack activates it. The first two steps report success on their own, so a connection that is still pending looks exactly like a finished install that does nothing.
- **One workspace to one org, and Slack Free stops there.** Sales Cloud for Slack pairs a single Slack workspace with a single Salesforce org. Up to 20 additional orgs can be connected on Slack Pro, Business+ and Enterprise Grid, and on Free you get the one.
- **Slack Connect channels and Government Cloud are out.** Sales Cloud for Slack does not support Slack Connect, so a shared channel with a customer in it is outside the integration, and Salesforce documents that Slack cannot be connected to a Government Cloud org at all. Neither is a setting.

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

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

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

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

### 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

- Slack Help Center: connect Salesforce and Slack: https://slack.com/help/articles/30754346665747-Connect-Salesforce-and-Slack
- Salesforce Help: considerations for Sales Cloud for Slack: https://help.salesforce.com/s/articleView?id=sf.slack_apps_sales_review_considerations_for_sales_cloud_for_slack.htm&language=en_US&type=5
- Salesforce Help: enabling Sales Cloud for Slack in Salesforce: https://help.salesforce.com/s/articleView?id=sf.slack_apps_sales_enable_sales_cloud_for_slack_in_salesforce.htm&language=en_US&type=5
- Slack Help Center: connect Salesforce and Slack: https://slack.com/help/articles/30754346665747-Connect-Salesforce-and-Slack
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-slack-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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.*
