SlackSalesforceAgentforce

Slack and Salesforce: making Slack the interface of your CRM

Clément Richard · Founder, Amplee • • 9 min read
In short

Connecting Slack to Salesforce lets teams work on CRM data from the conversation: channels tied to records, updates governed by Salesforce permissions, Slack actions in Flow, Slackbot and Agentforce agents. Licenses on both sides, record previews, notification noise and adoption still need scoping before any rollout.

A key opportunity changes status. The news travels through a Slack thread between the account executive, the manager and presales, but the Salesforce record is only updated two days later. At the next pipeline review, that context is missing from the CRM. The gap between where people talk and where data is recorded is the subject of this article.

Slack and Salesforce are now linked by several native building blocks: a connection between the Slack workspace and the Salesforce org, channels tied to records, Slack actions in Flow, Slackbot and Agentforce agents. Below we describe what these blocks actually do, based on the official Slack and Salesforce documentation read in November 2026, and what remains to be decided before rolling them out.

11native Slack actions in Flow Builder
3Agentforce agent templates built for Slack
20additional Salesforce orgs connectable to one Slack (Pro, Business+, Enterprise)

01What changes when Slack is connected to the CRM

Much sales and service information is born in conversations: a customer announcing a delay, an expert pulled into a hard case. Without a link to Salesforce, it stays in threads.

  • Double entry. Update an opportunity field where the deal is being discussed.
  • Lost context. Attach conversations to the relevant record so newcomers find the history.
  • Alerts buried in email. Push the Salesforce event that calls for action into the right channel at the right time.

Slack does not replace Salesforce: data, permissions and business rules stay in the CRM. Slack becomes a working interface on that data, with its own access rules that must be aligned with Salesforce.

02Slack in a few building blocks

  • Channels and direct messages. Channels bring people, information and tools together around a shared goal, publicly or privately.
  • Slack Connect. A channel can include up to 250 external organizations; to collaborate in channels, each organization must be on a paid plan.
  • Huddles. Audio or video calls from any channel or DM: two participants on the free plan, up to 50 on paid plans, 25 on video at once.
  • Canvases and lists. Canvases hold formatted content such as account plans or meeting notes; lists track tasks with fields, views and filters. Both are available on paid plans.
  • Workflow Builder. Available on paid plans, it automates tasks from a trigger (link, webhook, schedule, list update, keyword message, channel join, emoji reaction) followed by Slack, connector or custom steps.

03The foundation: connecting Salesforce and Slack

Everything starts with a connection between the Slack workspace and the Salesforce org, which Slack describes as the prerequisite for Slackbot, Salesforce channels and Agentforce. It takes three steps: a request in Slack, approval by a Salesforce system administrator in Setup, then activation in Slack. Member accounts are mapped automatically by email or SAML NameID, or manually, one by one or by CSV. Once active, mapped members get a Salesforce app in Slack with list views and notifications, among other things.

Points to anticipate: Government Cloud orgs cannot be connected, Salesforce IP restrictions may prevent some features from working, and a Salesforce Platform Integration User manages access to object types.

Salesforce apps for Slack

A Salesforce support article published on June 2, 2026 lists the apps available from the Slack Marketplace:

  • Salesforce for Slack, the platform app: notifications, approvals and screen flows in Slack, built by the admin in Flow.
  • Sales for Slack (formerly Sales Cloud for Slack): access, update and share records, manage the pipeline, get notifications on key accounts and opportunities.
  • Service for Slack (formerly Service Cloud for Slack): access records, manage cases and collaborate in a swarm channel where several experts work on one case.
  • Specialized apps: CRM Analytics, Account Engagement (formerly Pardot), PRM for partners, Financial Services Cloud, Trailhead.

The same article states that the legacy Salesforce app developed by Slack is not recommended for new implementations and will be phased out. Names change quickly (the article also mentions "Agentforce Sales" and "Agentforce Service"), so we always check the current name before installing anything. For an overview of the product portfolio, see Salesforce clouds explained, and our Service Cloud page for the support side.

04Salesforce channels: one conversation per record

Salesforce channels are a type of Slack channel tied to a record such as an account or an opportunity. They are available on all Slack plans once admins have configured them and chosen the allowed record types. Each channel has tabs:

  • Messages: the team conversation about the record.
  • Record details: a snapshot of Salesforce data, editable in Slack if you can edit the record in Salesforce. Rich text and geolocation fields cannot be edited from Slack.
  • Summary: an AI-generated summary of conversations across the record's channels, with sources (Business+ and Enterprise+).
  • Related conversations and related records: channels linked through record relationships, and a list of related records chosen by the admin.

The channel can also be opened from the record in Salesforce, with messages kept in sync; richer actions such as huddles, clips and workflows remain Slack-only. External people (Slack Connect) cannot be invited to Salesforce channels. For a strategic account, this is a natural extension of your Sales Cloud: account team, manager and presales share one thread and one record.

05Slackbot and Agentforce: AI inside the conversation

Slackbot, a personal agent connected to Salesforce

Slack presents Slackbot as a personal work agent, available on all plans with access and limits varying by plan. It can summarize, draft, search and run deep research that includes Salesforce data. Its answers only include what the user can access, including Salesforce permissions for Salesforce data.

By default, Slackbot can create or update records. Admins can restrict it to specific orgs, allow or exclude objects, and limit edits to assigned layouts; members are always asked to review and approve any change. Slack also documents standard Salesforce MCP servers (Data 360, record reads, mutations and deletes, Tableau Next) and custom MCP servers your developers can build on Apex actions, flows or Agentforce agents.

Agentforce in Slack

Agentforce in Slack is available on all Slack plans with a Salesforce Agentforce license. Agents are built in Salesforce with Agentforce Builder, then installed in Slack by an owner or admin. Only the Agentforce Employee agent type can be used for Slack, and three templates are offered: customer insights, employee help and onboarding. Members find agents in the Agents tab or mention them in a channel; answers respect the user's Slack and Salesforce permissions. Slack users without a Salesforce account need a Salesforce license, and service agents can only be used once access has been explicitly assigned.

These agents raise the wider question of where the CRM interface lives, which we cover in Headless and agentic. See our Agentforce page for how we design and test agents.

06Automation: from Salesforce to Slack, and back

  • Flow, on the Salesforce side. Flow Builder offers a Slack action category: create a channel, create or look up a Salesforce channel for a record, add users, archive a channel, send a message to a channel or to a user's Salesforce app, pin a message, create and share a canvas, look up a user's Slack ID. These actions run in the context of the user running the flow.
  • Workflow Builder, on the Slack side. On Business+ and Enterprise Grid, a workflow can start from a Salesforce event. Slack's example: create a Salesforce channel and add the opportunity owner and sales director when the opportunity amount drops by 10%.

A rule that depends on Salesforce data and sharing belongs in Flow; a team routine specific to Slack fits Workflow Builder better.

07Security, permissions and data retention

  • Inherited permissions. In Salesforce channels, people can only view and edit in Slack what they can view and edit in Salesforce.
  • Record previews. In channels and DMs, a preview reflects the record when it was shared, based on the sharer's permissions (or the integration user's for admin-created notifications). In canvases, it is computed when opened, with the viewer's permissions. Admins can limit preview details, and previews do not appear in channels with external people.
  • Guests. They can take part in the Messages tab but cannot access Salesforce data.
  • Retention. Slack-hosted data follows Slack retention settings (kept as long as the workspace exists by default on paid plans, configurable by owners, including for Salesforce channels); Salesforce data shown in Slack follows Salesforce policies.
  • Identity and compliance. SAML single sign-on is available on Business+ and Enterprise, and on Free and Pro when a Salesforce org is connected. Slack states that Salesforce channels use its compliance infrastructure where possible, including Slack EKM, data residency and data loss prevention.

The point we watch most closely: a preview shared by someone with broad access is visible to every member of the conversation. Preview settings belong in the scoping, alongside the Salesforce sharing model.

08What remains to scope, and our approach

NeedWhat Slack bringsWhat Salesforce bringsScoping point
Work an account or deal as a teamSalesforce channel, Messages tab, AI summary (Business+ and Enterprise+)Record of reference, relationships, permissionsAllowed objects, default privacy, channel naming
Update the CRM without switching toolsRecord details tab, Slackbot with user approvalEdit rights, layouts, validation rulesObjects open to Slackbot, limit to assigned layouts
Get alerted at the right timeChannels, Salesforce app messagesFlow and its Slack actionsNotification volume, target channels, running user's rights
Bring experts onto a caseSwarm channel, huddlesCase, knowledge baseLicenses and swarming setup
Delegate tasks to an agentAgents tab, channel mentionsAgentforce Builder, Employee agent typeAgentforce and Salesforce licenses, access to service agents
Work with external partnersSlack ConnectPRM for Slack (PRM license)No external people in Salesforce channels
  • Licenses on both sides. Several features depend on the Slack plan and on Salesforce licenses (Agentforce, data access). We map them before committing to a use case.
  • Noise. A useful alert triggers an action. We start with a few high-stakes events rather than notifying everything.
  • Permissions. Sharing model, channel privacy, previews and integration user are decided together.
  • Adoption. Channels and agents only matter if teams make decisions there, so rituals are redesigned with them.

Our three-step approach

  • Assess. We start from your decisions and rituals, then audit your Slack plan, Salesforce licenses, sharing model and installed apps.
  • Build. Connection and account mapping, Salesforce channels on a narrow scope, a few alert flows, Slackbot settings and, when the use case justifies it, a first agent, each tested with users holding different permissions.
  • Adopt. Coaching teams through their first rituals in Slack, documenting the rules chosen, adjusting from field feedback.

Our Fast Start "Slack & Agentic bot" offer, described on our Offers page, covers this first scope. If you first want to know where your org stands, we start with a Health Check.

Fast Start Slack & Agentic bot

Connect Slack to your Salesforce, with the right permissions from day one

We start from how your teams actually work: which decisions happen in Slack, which Salesforce data should surface there, and who can see and edit it. One first conversation is enough to know where to begin.