Salesforce ↔ Slack integration

Important Salesforce changes arrive in the right Slack channel as they happen, and a button in the message updates the record back in Salesforce

The team talks in Slack, while deals, leads and cases live in Salesforce. So a large deal changes stage and nobody notices until the weekly meeting, and a manager who wants to take a new lead has to leave the conversation, open Salesforce and find the record. The Salesforce ↔ Slack pair brings chosen Salesforce changes into the right channel as they happen, with the key fields and buttons, and turns a click on a button into an update of the same record in Salesforce. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: Salesforce →System page: Slack →

What moves between the systems

Salesforce → SlackA change you choose in Salesforce, for example a deal moving to a late stage or a large deal being won, is published by Salesforce as an event and becomes a Slack message in the agreed channel.
Salesforce → SlackA new lead or case appears in the team channel with the main fields and a link to the record, so whoever has time can pick it up at once.
Slack → SalesforceButtons in the message, such as “Take it” or “Mark as contacted”, update the same Salesforce record: the owner or status changes, and the message shows who pressed it.
Slack → SalesforceA short note written in the message thread can be saved to the Salesforce record as a task or comment, so the conversation does not stay only in Slack.

What we connect

Together we choose which Salesforce changes deserve a message and which channel each goes to; everything else stays quiet.
In Salesforce an administrator sets up access for the pair as an External Client App, which Salesforce now recommends for new connections.
In Slack a workspace administrator installs the pair's app and adds it to the chosen channels; it sees only those channels.
We agree which buttons each message gets and which Salesforce fields they may change, and nothing beyond that list.
We test on a Salesforce test environment and a private Slack channel, then turn it on for the team and adjust what is too noisy in the first week.

Automation scenarios

A new lead nobody took

Before leads wait in a Salesforce queue until someone checks it.

After each lead appears in the sales channel, one manager presses “Take it”, and the record gets an owner at once.

A large deal changed stage

Before the head of sales learns about it from a report days later.

After the deal channel gets a message with the amount and stage the moment it changes.

An urgent support case

Before a high-priority case sits in Salesforce while the team discusses something else in Slack.

After it lands in the support channel, and the person who picks it up is recorded in Salesforce.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

REST API gives programmatic access to Salesforce records, metadata and search without using the Salesforce interface itself.
Source: developer.salesforce.com ↗ checked 2026-09-25
Access is authorised through OAuth 2.0 via a Connected App or External Client App; since Spring '26, creating new Connected Apps is restricted and Salesforce recommends External Client Apps instead (existing Connected Apps keep working).
Source: developer.salesforce.com ↗ checked 2026-09-25
Platform Events are secure, scalable messages published by Salesforce and received by subscribers in real time — Salesforce's built-in equivalent of a webhook.
Source: developer.salesforce.com ↗ checked 2026-09-25
The Events API lets an app react to what happens in Slack: Slack itself calls the app's server when an event occurs, so there is no polling.
Source: docs.slack.dev ↗ checked 2026-09-27
Block Kit lets a message carry interactive elements such as buttons and menus; a message can hold up to 50 blocks.
Source: docs.slack.dev ↗ checked 2026-09-27
An app may post about one message per second per channel, whichever way it sends them; short bursts above that are allowed.
Source: docs.slack.dev ↗ checked 2026-09-27

Limits

The limits come from both systems. Slack allows an app about one message per second in a channel, with short bursts above that, so a mass update in Salesforce becomes one summary message instead of hundreds. One Slack message holds up to 50 blocks, so each message shows the key fields and a link, not the whole record. On the Salesforce side, access for new connections is set up as an External Client App, since creating new Connected Apps is now restricted. Buttons can change only the fields agreed in advance, and every change is recorded in Salesforce under the person who pressed it.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Will the channel turn into noise?

Only the changes we agree on become messages, and mass updates are grouped into one. In the first week we remove whatever the team finds useless.

Can anyone in Slack change our Salesforce data?

No. The pair works only in the channels it was added to, buttons change only the agreed fields, and each change is recorded under the person who made it.

Is this the same as the Slack app in the Salesforce marketplace?

No, this is a pair we set up for your process: your fields, your channels, your buttons. If a ready app already covers what you need, we will tell you after looking.