Slack Salesforce Integration
We set up Slack and Salesforce to work together: record-linked Salesforce channels, cloud-specific Slack apps, Flow automation and Slackbot, with sensible permissions.
Deals and cases are often discussed in Slack while the record lives in Salesforce. Connecting the two lets people see and act on Salesforce data in the conversation, and keeps the conversation tied to the record. GeekMidst sets up Slack and Salesforce integration remotely from India, mostly through configuration and light automation rather than custom middleware. For custom system-to-system work, see Salesforce integration services.
What Salesforce offers in Slack
Salesforce's integrations page uses these names:
- Salesforce channels: Slack channels linked to Salesforce records.
- Per-cloud apps: Sales Cloud in Slack, Service Cloud in Slack, IT Service in Slack, Tableau Next in Slack and Flow in Slack.
- Agentforce in Slack, for working with agents from Slack.
- Slack CRM, a small-business CRM in Slack.
- Approvals in Slack, listed as "coming soon".
Slack itself adds Slackbot (the AI assistant), Workflow Builder, Slack Connect, Enterprise Search and a Slackbot MCP client and server (GA August 2026). At Dreamforce 2026 Salesforce introduced Slackforce branding, covering Surfaces, Slackbot, Slack CRM and Slack Code. A Salesforce blog said "GA in October" but the newsroom gave no date, so we confirm availability before planning around it.
Prerequisites and licences
Salesforce channels work inside Salesforce on all Slack plans, but the Summary tab and list views in Slack need a Business+ or Enterprise plan. Existing Salesforce customers can connect a free Slack workspace. The Core, Advanced and Max editions include Slack and Slackbot; check what your contract covers. Agentforce in Slack needs Agentforce licences.
What's included
| Area | What we cover |
|---|---|
| Connection | Linking Salesforce orgs and Slack workspaces, and choosing the apps to install |
| Salesforce channels | Which objects get channels, who joins and how channels are named |
| Alerts | Record updates routed to the right channel or person |
| Flow in Slack | Flows that post to Slack or collect input from it |
| Agents | Agentforce in Slack, where your licences include it |
| Permissions | Slack visibility aligned with your Salesforce sharing model |
How we work
- 01
Discovery
We find where work already happens in Slack and which Salesforce records it relates to.
- 02
Design
We pick a small set of channels, alerts and actions and agree data visibility rules.
- 03
Build
We configure the apps, Salesforce channels and flows in a test workspace and sandbox.
- 04
Test
Users try alerts and actions, and we check nobody sees records they shouldn't.
- 05
Launch
We roll out by team, with a short guide on what belongs in Slack and what stays in Salesforce.
- 06
Support
We trim noisy alerts and add actions as teams ask for them.
Who it suits
Sales and service teams already living in Slack, and managers who want updates without opening another tab. If your company uses Microsoft Teams instead, Salesforce also lists Sales Cloud in Microsoft Teams in Winter '27.
Common mistakes
- Sending every record change to Slack until people mute the channel.
- Forgetting that Slack visibility must follow Salesforce sharing.
- Recording decisions in Slack that belong on the record.
- Planning around features announced but not yet available.
Related services
Pair this with Sales Cloud implementation, Service Cloud implementation or Flow automation. For who sees what, see security and governance. Product details are on our Slack overview.
Questions we hear
Do we need a paid Slack plan?
Can Slack users see any Salesforce record?
Is Slackforce available now?
Can approvals happen in Slack?
Sources
Bring Salesforce into Slack
Tell us how your teams use Slack today and we will suggest the first channels and alerts to set up.
