The one pair where the same company owns both sides.
Sales Cloud, plus a Slack workspace you can install apps into
Deals, Activities, Messages, Contacts, events only.
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.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Record search and updates | Both ways | 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 | Both ways | Channels associated with opportunities or accounts, so the deal room and the record are the same thing. |
| Approvals | Both ways | Approval requests actioned in Slack and written back, which is the feature that changes cycle time. |
Three of those four rows move in both directions. The one that does not is Flow to channel, and those are the rows that decide how you design around this rather than the ones in the brochure.
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. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the four vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Because the mapping is people-first, the commonest failure is not a field going to the wrong place, it is a person who was never matched and therefore sees an app that does nothing.
Three Salesforce editions against three Slack ones, and what each pairing gives you. Pick the two you own and the grid marks the answer.
Pick an edition on each side.
| 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 |
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.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
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.
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.
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.
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.
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.
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.
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.
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.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/salesforce-slack/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-slack.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThe 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.
WhyEach 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.
WhyAutomatic 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.
WhySalesforce 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.
WhyThe org URL changed. The stored connection still points at the old one.
Update the connection in Slack with the new org URL.
WhyA 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.
WhySales 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2020 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
I live in slack more than SFDC CRM. If I could just access CRM data/objects in Slack I wouldn't ever need to login to CRM lol. If I could assign and link slack channels to specific opportunity so that information flows seamlessly between them, then I would be happy.
r/salesforce·November 2025·18 points
Both of those shipped. Record access from Slack and channels linked to an opportunity are in the table above, which makes this a discovery problem rather than a product one, and it is the strongest argument for the internal announcement being part of the rollout.
You can. The slack and Salesforce integration can do that out of the box. Look at opportunity and account channels on the slack documentation. I don't think you need extra licenses for that if you are on Salesforce EE
r/salesforce·November 2025·25 points
A correct answer with a hedge in the middle of it, upvoted 25 times. The grid above is there because this is the question the documentation answers in four places and nobody reads all four.
Made a quick tutorial on how to setup a direct Slack integration with Salesforce via Flows, it was surprisingly difficult
r/salesforce·November 2023·55 points
The most upvoted thing in the set is a tutorial that exists because the documented path was harder than expected. Budget the afternoon rather than the lunch break, and do the three-step handshake before you touch Flow.
Salesforce is horrible at actually consuming its purchases. We all thought that when they bought tableu; reporting in salesforce would truly be amazing. Wrong.
r/salesforce·November 2025·31 points
Worth holding next to what the integration actually does, which is deeper than any other pair in this directory. The scepticism is about the pattern rather than about this product, and on this one the depth is real while the ease is not.
SF employee here. Most of our slack customers are also also Teams/Microsoft shops. This isn't unheard of at all.
r/salesforce·November 2025·18 points
Useful if you are being asked to justify a second messaging tool. The integration does not require Slack to win internally, it requires the revenue team to live there, and those are different arguments to make to a CIO.
Two things come through across these threads and they pull in opposite directions. People who use both products daily want exactly what this integration already does, and describe it as something they wish existed. People who have set it up describe a Salesforce admin project. Common ownership is read by practitioners as a reason to expect depth rather than ease, and the licensing question comes up unresolved more than any other.
The licensing confusion in the second quote is the one worth acting on: it is the question that stalls this project, and it is answerable in an afternoon from your own contract.
Common ownership is worth something here and it is worth less than people expect. What it buys is depth and a roadmap: bidirectional record work, approvals, and a reasonable assumption that the integration will keep getting attention. What it does not buy is ease. This is still Flow, permission sets and a change window.
The interesting part is approvals rather than alerts. Notifications make information faster. Approvals in Slack make a decision faster, and on a long enterprise cycle that is the difference the finance team can see. If you are building a case for this internally, build it on cycle time rather than on visibility.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Salesforce, Slack and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
It is deeper, and no easier to install. Common ownership buys bidirectional record work, approvals actioned in Slack and a reasonable assumption of continued investment. It does not buy a self-serve setup: this is still Flow, permission sets and a change window.
Find and update Salesforce records, receive alerts driven by Flow on any record event, associate a channel with an opportunity or account so the deal room and the record are the same thing, and action approval requests that write back. Feature availability varies by cloud and edition, so check against your own licences.
Approvals rather than alerts. Notifications make information faster; approvals in Slack make a decision faster, and on a long enterprise cycle that difference shows up in cycle time, which is a number finance can see. Build the internal case on that rather than on visibility.
The same rule as every CRM-to-Slack pair: one strict trigger, one channel, one accountable owner. A channel that fires constantly gets muted, and a muted channel is worse than no alerting because everyone still believes it works.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.