Salesforce Slack Integration (and Microsoft Teams): Setup and Use Cases

Your options at a glance

There are four ways to bring Salesforce into chat. Most companies need the first one and a bit of the second. The rest are for gaps.

One thing to drop: Slack says its older Slack-built Salesforce app is no longer supported. If you still run it, plan the move to the Salesforce-built integration before it breaks. For how chat fits into your wider Salesforce architecture, see our Salesforce integration guide.

Slack vs Teams: what Salesforce gives you natively

Salesforce owns Slack, and it shows. The Slack integration is deeper, newer and gets AI features first. Teams support is solid for sharing records, thinner for automation.

How to connect Salesforce to Slack, step by step

This is the current Salesforce-built path. You need a Slack workspace owner or admin and a Salesforce System Administrator. Book an hour with both.

1. Check the basicsConfirm your Salesforce edition supports the Slack features you want and that your org is not on Government Cloud, which Slack can’t connect to. Check login IP restrictions in Salesforce: Slack warns they can stop connected features from working.
2. Start in a sandboxConnect a full or partial sandbox first if you plan to build flows. You test alerts against fake deals instead of announcing a test “closed won” to the whole sales floor.
3. Request the connection in SlackIn Slack, open your workspace menu, then Tools & settings, then Manage Salesforce Organizations, and choose to connect an org. Enter the org URL and pick the mapping field: email or SAML NameID.
4. Approve it in SalesforceIn Setup, find Slack under Platform Tools and open Manage Slack Connection. Pick the same mapping field, accept the terms and approve. Then the Slack admin activates the pending connection.
5. Map usersKeep automatic account mapping on if emails (or SAML IDs) match in both systems. Fix mismatches first: shared inboxes, aliases and contractors with personal emails. Slack can export a mapping report so you can see who did not match.
6. Assign permission setsGive users the Slack permissions and permission sets for the features you turn on. For example, Salesforce’s documentation lists the Connect Salesforce with Slack permission and a Slack Service User permission set for Service Cloud for Slack. Names change between releases, so match what your Setup shows.
7. Turn on features one at a timeConfigure Salesforce channels (choose which objects get them), install Service Cloud for Slack if you plan swarming, and add the Salesforce app in Slack. Launch one feature per team, not everything for everyone.
8. Build the first flow and test itCreate a record-triggered flow with a Send Slack Message action, run it in the sandbox, check who can see the message, then deploy to production with a change set or your normal release process.

How to set up the Salesforce Teams integration

1. Confirm the licenseCheck that your org is Enterprise, Performance, Unlimited or Developer edition with an Agentforce Sales or Service license. If the Setup toggle fails with a message about a Teams integration SKU, Salesforce’s help says your account executive needs to provision it (it costs nothing).
2. Turn it on in SalesforceIn Setup, search for Teams, open Teams Integration, turn it on and accept the terms. Assign the Teams integration permission set (shown in Setup as User for Teams Integration at the time of writing) to the users who need it.
3. Add the app in TeamsA Microsoft 365 or Teams admin allows the Salesforce app in the Teams admin center and, ideally, pins it for the pilot group through an app setup policy.
4. Users sign inEach user signs in to their own Salesforce account inside the app. People without a Salesforce user can’t preview or mention records.
5. Add alerts separatelyFor deal or case alerts, build a Power Automate flow with the Salesforce connector, an iPaaS recipe, or a Salesforce flow that calls a Teams workflow over HTTP. Use a dedicated integration user for the Salesforce side.

Six use cases worth building

Pick two to start. Each one below names the trigger, where it posts and what the reader can do. All of them work in Slack with Flow alone; in Teams, swap the Flow Slack action for Power Automate or an iPaaS step.

1. Big deal won

Trigger: record-triggered flow on Opportunity, when Stage changes to Closed Won and Amount is above your threshold. Posts to: a #wins channel. Message: account, owner, amount band, product line and a link to the record. Thread replies keep the congratulations out of the main feed. Use the threshold to keep it rare, or it stops being news.

2. Case swarming

Trigger: an agent starts a swarm from the case in Salesforce or with the /service-swarm-start command in Slack, for example on high-priority cases with no update in a set time. Posts to: a new or existing swarm channel, through Service Cloud for Slack. Experts join, solve it in the thread, and the agent finishes the swarm (Finish Swarming or /service-swarm-close), which marks the swarm closed in Salesforce. According to Slack, Salesforce’s own support team improved case close rates by 26% with swarming in Slack. Define who may start a swarm, or every hard case becomes a fire drill.

3. Approval in chat

Trigger: a discount, quote or contract approval request. With the Salesforce-built integration, requests from classic approval processes can be delivered to Slack with Approve and Reject buttons when Slack notifications are on for approvals. Simple approvals finish in Slack; when the request has comments or the approver must pick the next approver, the user is sent to Salesforce. For richer approvals, run a screen flow in Slack that shows the deal context and collects the decision.

4. Daily pipeline digest

Trigger: a schedule-triggered flow every weekday morning. Posts to: a DM to each rep, or a team channel. Message: deals closing this week, deals with no activity in 14 days, and stage changes since yesterday. A digest replaces ten real-time pings. Send personal numbers by DM, not to the channel.

5. Deal room on a strategic opportunity

Trigger: Opportunity created above a size threshold, or moved to a late stage. Action: create a Salesforce channel on the record (or use Flow to create a channel and then invite the account team with a separate Add Users action). Sales, solution engineering, legal and finance work in one place, and the record details sit in the channel tab. Archive it when the deal closes.

6. Hot lead or renewal at risk

Trigger: a lead with a high score assigned to a rep, or a renewal opportunity with a health flag. Posts to: a DM to the owner, with a fallback to the team channel if nobody touches it within an hour. Speed matters most here, so this is the one alert that earns real-time delivery.

What to send where: mapping table

Salesforce stays the system of record for every row. Chat is where people see and act, never where data is stored.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Who sees what: data exposure in channels

This is the pitfall that reaches the security team. Salesforce sharing rules decide who sees a record in Salesforce. They do not decide who reads a message once it is posted.

• Alerts are plain text. A flow message with the amount, discount or customer contact is readable by every channel member, including people with no Salesforce license, guests and anyone who joins the channel later.
• Previews and Salesforce channels check access. According to Slack, your permissions in a Salesforce channel match your permissions on the record, and you can edit only if Salesforce lets you. Channel members still all see the Messages tab.
• Teams previews may show more. Depending on setup, a shared record shows its compact layout in the conversation, even to people without Salesforce access. Check what your compact layouts contain before rollout.
• Retention moves. A copy of the data now lives under Slack or Microsoft 365 retention and eDiscovery rules, not Salesforce’s. Health, financial and personal data usually should not go there at all.
• External people. Slack says you can’t invite external people to Salesforce channels, but a flow can still post into a shared channel with a partner. Block shared channels as alert targets.

The fix: post links and safe summary fields, and let people click through to Salesforce, where sharing rules apply. Keep a short list of fields that may never appear in a message, and review it with whoever owns your data policy.

Notification fatigue: how teams end up muting the channel

The first month usually goes the same way: every stage change posts, the channel scrolls all day, and people mute it. Then the one alert that mattered is missed.

• Set a threshold for every alert. Amount, priority, segment. If an alert fires more than a few times a day in one channel, raise the bar or turn it into a digest.
• Personal goes to DMs, team news to channels. A rep’s stalled deals are not the whole team’s business.
• One alert, one owner. Every message should say who is expected to act. Alerts nobody owns are noise.
• Thread follow-ups. Use the message timestamp from Send Slack Message to post updates as thread replies instead of new messages.
• Review monthly. Count alerts per channel, ask the team which ones they act on, and delete the rest.

Other pitfalls and fixes

When a custom integration makes sense

The native tools cover most alerts and approvals. A custom Slack or Teams app (built on Salesforce APIs, the Slack API or Microsoft Graph) earns its cost when:

• Approvals need data from several systems, such as margin from the ERP and risk from a contract tool, in one interactive card.
• You run Teams and need two-way actions and approvals there that the Salesforce app does not provide.
• Several Salesforce orgs, or Salesforce plus another CRM, must feed the same channels with the same rules.
• Compliance needs field-level redaction, audit logs of every message sent, or region-specific data handling.

A typical project includes a hosted app (bot, interactive cards, slash commands), OAuth for both sides, an integration user in Salesforce, event handling with retries, and monitoring. Budget for upkeep too: Slack, Microsoft and Salesforce all change their APIs and app rules every year.

For realistic budgets, see our API integration cost guide and the broader cost of data integration.

Go-live checklist

Tick what is already true. It shows how ready your chat integration is for the whole team.

FAQ

Where Gilzor fits

Gilzor builds and maintains Salesforce integrations (see Salesforce integration services). Gilzor’s engineers can map which deals, cases and approvals belong in Slack or Teams, build the flows or a custom chat app, and support it after launch. More Salesforce connections are covered in the Salesforce integration guide.