Salesforce Slack Integration: Setup, Automation, and AI (2026 Guide)
Key Takeaways
- One org-level connection replaces individual app installs. A Slack admin and a Salesforce admin connect the workspace and org once. Mapped users get the Salesforce app automatically. On March 31, 2026, Slack ended its support for legacy connections.
- Salesforce channels take over Chatter’s role on records. Records such as accounts, opportunities, and cases can each have their own Slack channel, visible right on the Salesforce record page. New orgs created since Summer ‘26 have Chatter turned off by default.
- Flow sends Salesforce alerts right to Slack. When a record meets your criteria, you can set up a Flow to send a DM or post a message in a team channel. No coding needed.
- Slackbot works with Salesforce data. On Business+ and Enterprise plans, Slackbot can find, create, and update Salesforce records, as well as summarize accounts, based on each user’s permissions.
Believe it or not, but the Salesforce Slack integration has turned over a new leaf more in 2026 than it did in the five years after Salesforce acquired Slack. And if your setup hasn’t kept up and has lagged behind these changes, things can get messy fast.
On March 31, 2026, Slack ended support for legacy Salesforce connections. If your setup still relies on the old managed package, you’ll need to reconnect it. Since Summer ’26, every new Salesforce Enterprise and Unlimited Edition org also comes with a Slack workspace already set up, while Chatter is turned off by default.
So admins have a lot to figure out. Is your existing integration still working as it should? Are users missing record updates or notifications? And how do you make sure Salesforce data reaches the right people in Slack withʼout adding more manual work?
In this guide, we’ll show you how to set up the Slack and Salesforce integration, how Slackbot and Agentforce fit in, and how to fix common integration issues. You’ll also learn how Salesforce and Slack improve team collaboration when the two platforms are connected.
How the Salesforce Slack Integration Works in 2026
Before you start, check your Salesforce editions and licenses to make sure your org supports the features you need.
Imagine the Salesforce and Slack integration as two separate layers. So what should you do to make them interact? Everything starts with one connection between your Slack workspace and your Salesforce org. Once it’s in place, every other feature builds on it.
Then add the features your teams need: Salesforce apps in Slack, Salesforce channels, Flow notifications, and Slackbot. Set up the connection once, and you have a base for everything else. But let’s reveal how all these components work together!
The org connection
A Slack admin requests the connection, and a Salesforce admin approves it. Slack links each person’s account to their Salesforce user through their email address or SAML NameID. Users can only view records their Salesforce permissions give them access to. Any changes they make in Slack are saved directly in Salesforce. The data itself stays in Salesforce.
The Salesforce apps in Slack
Salesforce offers Slack apps according to different teams’needs. Sales Cloud for Slack lets sales reps search, view, and update accounts and opportunities – all this without leaving Slack. Service Cloud for Slack helps support agents and involve experts to resolve cases. CRM Analytics for Slack lets teams share dashboards and data alerts in channels.
Salesforce channels and the Slack panel on record pages
A Salesforce channel links a Slack conversation to a record, such as an opportunity or a case. The conversation also appears in the Slack panel on that record’s Salesforce page. So, whether someone works in Slack for Salesforce, they can follow the same discussion instead of digging through Chatter posts, emails, and DMs.
Slackbot and Agentforce in Slack
Since January 2026, Slackbot Salesforce has been available to teams. What can it do? It can answer questions about Salesforce data, summarize accounts, and update records right in a talk. Plus, you can also bring Agentforce agents built in Salesforce into Slack. Employees can then interact with them in DMs and channels, right where they already work.
What’s New and What’s Retiring in the Slack Integration with Salesforce
The Slack Salesforce integration changed in four important ways in 2026. If your team set it up before this year, check these first.
- Legacy connections are no longer supported. On March 31, 2026, Slack ended support for legacy Salesforce connections. These are the ones based on the old Slack-built managed package. That’s why we recommend you to reconnect through the current org-level setup if Salesforce features in Slack stopped working around that date.
- Slack is the default for new orgs. Since the Summer ‘26 release, new Enterprise and Unlimited Edition orgs come with a Slack workspace already set up, and Chatter is turned off by default. Existing orgs aren’t affected: Chatter keeps working, and Salesforce hasn’t announced a Chatter retirement date. Still, the direction is clear. For new customers, Chatter vs Slack is no longer a choice, and Salesforce channels take over Chatter’s role on records.
- Approvals moved into Slack. Also in Summer ‘26, approvers can approve or reject Salesforce approval requests directly in Slack, without opening the record.
- Slack Sales Elevate is being retired. The add-on can’t be purchased on renewals after March 1, 2027. If your sales team relies on it, plan the move with your Salesforce account executive before your next renewal.
- Other Slack changes to keep in mind. Slack is also retiring some features and subscriptions – Slack Sales Elevate and the Slack AI add-on. From March 1, 2027, you won’t be able to buy or renew these offerings. If your team uses them alongside Salesforce, check Slack’s retirement list to see how these changes might affect your setup.
Before You Connect Salesforce to Slack
Before you connect Salesforce to Slack, take a few minutes to check what you need. You’ll save yourself a few setup headaches and avoid delays later.
- Salesforce edition. Enterprise and Unlimited support the full integration, including Salesforce channels. If you use Professional Edition, check which features your plan includes before you start.
- Slack plan. To use Slackbot with Salesforce data, you need a Business+ or Enterprise plan with Slackbot enabled.
- Two admins. You need a Slack admin (Workspace or Org Owner/Admin) and a Salesforce System Administrator. Both need to approve the connection. That’s why make sure they’re available.
- My Domain URL. Find it in Setup → My Domain and keep it handy. Slack uses it to identify your Salesforce org, and Slack’s Lightning components need it too.
- User mapping. Decide whether Slack should match users by email or SAML NameID (called Federation ID in Salesforce). If users have different email addresses in the two systems, such as aliases or contractor addresses, use SAML NameID.
- Object access. List the Salesforce objects your team needs to access in Slack — Accounts, Opportunities, and Cases.
- A sandbox for testing. You should start by connecting a Salesforce sandbox to a test Slack workspace. Check what users can see and do before setting up the integration in production.
How to Connect Salesforce to Slack
Connecting Salesforce to Slack lets your team find records, share updates, and manage notifications. And all this is possible without jumping between tools. To get everything working, you have to start with the org connection. And only then, you can set up record access, notifications, and Salesforce channels.
Follow these basic 7 steps to configure the integration. N.B.: Test it in a sandbox first. This is an essential condition as you have to check that users have the right access and everything works as expected before deploying.
Step 1. Enable Salesforce for Slack integrations
A Salesforce System Administrator does this once per org.
1. In Salesforce, open Setup and enter Slack in the Quick Find box.
2. Open the Slack setup page and accept the Salesforce for Slack Integrations terms.
3. Assign the Connect Salesforce with Slack permission through a permission set to users who will work with Salesforce in Slack.
4. Assign any app-specific permission sets your teams need – Slack Sales User or Slack Service User.
Step 2. Preparing the integration user
The connection uses a Salesforce Platform Integration User to control which objects Slack features can access. This step also needs a System Administrator.
1. Create a permission set and give it a label.
2. Under Object Settings, grant Read access (and View All, if your team needs it) to each object you want in Slack, such as Accounts, Opportunities and Cases.
3. Assign the permission set to the integration user. Test the whole setup in a sandbox before connecting production.
Step 3. Connecting Slack and Salesforce
A Slack admin and a Salesforce admin complete this together in three actions.
1. Request the connection in Slack. A Workspace Owner/Admin, Org Owner/Admin, or user with the Salesforce Admin role opens the workspace menu and goes to Tools & settings → Manage Salesforce Organizations → Connect Salesforce Org. Enter your Salesforce org URL, choose Email or SAML NameID for account mapping, leave Automatic account mapping on, and click Request Connection.
2. Approve it in Salesforce. A System Administrator goes to Setup -> Platform Tools -> Slack -> Manage Slack Connection, selects the matching field under User Configuration, agrees to the terms and clicks Approve.
3. Activate it in Slack. The Slack admin returns to Manage Salesforce Organizations, selects the pending connection and clicks Activate.
Every user whose account is mapped then gets the Salesforce app in Slack automatically.
Step 4. Finding, updating and sharing Salesforce records in Slack
1. Type what you're looking for in the Slack search bar and choose Search in Salesforce.
2. Select a record to open it in Slack.
3. Edit any field you have permission to change and click Save Changes. The update appears in Salesforce right away.
4. To share a set of records, open the Salesforce app, go to the List views tab, pick a list view and click Share (Business+ and Enterprise plans).
What each user can see and edit in Slack follows their Salesforce permissions. Admins choose which fields appear by configuring a Slack record layout for each object.
Step 5. Setting up personal notifications with Flow
Notify people in Slack about the records that matter to them. For example, these could be notifications when a lead is assigned to them, a deal closes, or a customer submits a case. If you’re building out your support processes, see our Service Cloud implementation guide.
In Salesforce, create a record-triggered flow on the object you need.
1. Set the entry conditions, for example “Owner changed”.
2. On an asynchronous path, add an Action, choose Slack and then Send Slack Message.
3. Send the message to the user's DM or to the Messages tab of the Salesforce app, and include a link to the record.
4. Save and activate the flow.
Step 6. Setting up Salesforce channels for records
In fact, Salesforce channels are Slack channels tied to a specific record. That’s why the team can discuss a deal or case right next to its data. But how to set up Salesforce channels for your records?
1. In Salesforce Setup, open Slack Channels for Records.
2. Enable the objects that can have channels — Account, Opportunity or Case.
3. Decide whether new channels are public or private by default.
4. Add the Slack component to the object's Lightning record page. This ensures that the channel conversation also appears in Salesforce.
Users can then create a channel directly from a record. In Slack, the channel shows record details, related talks and an AI summary.
Step 7. Sending notifications for a whole object type to a channel
To keep a team channel updated about every record of one type, for example every new high-priority Case, use a flow. Keep in mind that too many notifications make important messages harder to spot.
1. Create a record-triggered flow on the object.
2. Set narrow entry conditions so only relevant changes trigger it.
3. On an asynchronous path, add Slack -> Send Slack Message with the team channel as the target.
4. Save and activate the flow.
Before you go live
Now you’re ready to roll out Salesforce Slack integration to your team. Many developers jump to connecting both platforms and forget to make sure everything works as it should.
That’s why we recommend that each team do the following:
- Check record access. Can users find and open the Salesforce records they need in Slack? Make sure they only see the records and fields their Salesforce permissions allow.
- Test notifications. You need to trigger a few personal and channel notifications. You should make sure the messages reach the right people and channels.
- Check Salesforce channels. For this, you should open a record in Salesforce. Does its Slack conversation appear on the record page?
- Prioritize testing in a sandbox. Before moving to production, it’s necessary to try everything out. And the reason is pretty simple: it’s easier to catch and fix issues before your whole team starts using the Salesforce and Slack integration.
All good? Your team is ready to use Salesforce in Slack, find the records they need, follow updates, and keep conversations in one place.
How to Make Your Salesforce Slack Integration Work for You
Salesforce Slack integration in 2026 is no longer just an add-on. It’s a regular part of how teams work with Salesforce data. With legacy connections retired, Chatter turned off in new orgs, and more ways to collaborate and use AI in Slack, there are fewer reasons to keep the two platforms apart.
The setup itself is simple enough:
- You need to connect Salesforce and Slack, give users the right access, and add the features your team needs.
- Then, you have to use Flow to send important updates, Salesforce channels to discuss records, and Slackbot and Agentforce to find, update, and summarize data.
- After this, you should start small and test everything in a sandbox
- Finally, you can add more features as your team gets used to the integration.
But connecting the two platforms is only the first step. You also need to decide which data users should access in Slack, which updates deserve a notification, and how to keep permissions in check as your team scales up. This is where you need a Salesforce implementation partner who can help you avoid extra work and get the setup right.
At Noltic, we help companies implement Salesforce, offer expert consulting, and connect Salesforce with the tools they use every day. Whether you’re setting up Salesforce for the first time, improving your current system, or building new integrations, we’ll help you make your systems work together and fit your business needs.
Looking for the right team for the job? Explore our guide to Salesforce integration partners to learn what to look for. Talk to our team to find the right integration for your business.
FAQ
Is the Salesforce Slack integration free?
The core Salesforce Slack integration is available with eligible paid plans. But for some features, you may need extra plans or add-ons. For example, you should pick a Business+ or Enterprise+ plan if you want Slackbot features. In addition, Salesforce Sales Elevate is being retired. That’s why before choosing your setup, it’s better to check the latest plan details.
Is Salesforce replacing Chatter with Slack?
Not completely. Since Summer ’26, Chatter is turned off by default in new Salesforce orgs, but existing orgs aren’t affected. Salesforce hasn’t announced a retirement date for Chatter. Slack offers more ways to discuss records, share updates, and use AI. But of course, you can still use Chatter if it fits your team’s needs.
Is Slack still owned by Salesforce?
Yes, Salesforce acquired Slack in 2021, and both platforms keep working closely together. You can learn how to connect them in our Salesforce Slack integration setup guide.
Can you build a custom Salesforce Slack integration?
Yes. If the standard integration doesn’t cover your needs, you can use the Salesforce API to connect Salesforce and Slack through a custom solution.
How do I connect Salesforce to Slack?
To connect Salesforce to Slack, a Slack admin requests the connection, and a Salesforce System Administrator approves it. First, open Manage Salesforce Organizations in Slack and request the integration. Then, approve it in Salesforce under Setup → Slack → Manage Slack Connection. Finally, return to Slack and activate the connection. See our step-by-step guide on how to connect Salesforce to Slack for the full setup.
Why did my Salesforce Slack integration stop working?
The main reason is that Slack ended support for legacy Salesforce connections on March 31, 2026. If your integration fails to work after that date, you may need to reconnect your Salesforce org. In Slack, go to Tools & settings → Manage Salesforce Organizations and request a new connection. Then ask your Salesforce admin to approve it. Follow our step-by-step setup guide to reconnect the two platforms.
Can I send Slack messages from Salesforce Flow?
Yes. Once Salesforce and Slack are connected, you can use the Send Message to Slack action in Salesforce Flow to send messages to a Slack channel or a user’s direct messages (DMs).
How to migrate from HubSpot to Salesforce
together