Salesforce + Slack Integration
Connect Slack to Salesforce so deals announce themselves, approvals happen in the channel, and reps update records without opening the CRM — which is usually why records go stale in the first place.
What Does This Integration Do?
CRM hygiene fails for a boring reason: updating a record means leaving the tool where the work is actually happening. Deals get discussed in Slack for days before anything reaches Salesforce, approvals sit in an email nobody opens, and escalations get lost in a thread.
This integration brings the two together properly — pipeline changes and big wins announce themselves in the right channel, approvals are actioned with a button rather than a login, cases escalate into a dedicated swarm channel, and reps update opportunity fields from a Slack modal that writes straight back to Salesforce.
What Syncs, and Which Way
Most Salesforce + Slack projects cover the same ground. What differs is which teams get which alerts — that's the part worth designing carefully.
Deal & Pipeline Alerts
Salesforce → Slack
Stage changes, big wins, and at-risk deals posted to the right channel
Approvals
Both directions
Discount and quote approvals actioned with a button in Slack
Case Escalation
Salesforce → Slack
High-priority cases open a swarm channel with the right people in it
Record Updates
Slack → Salesforce
Reps update opportunity fields from a modal without opening the CRM
Record Lookup
Slack → Salesforce
Search accounts, contacts, and open deals with a slash command
Channel Sync
Both directions
Discussion linked back to the record so context isn't lost in a thread
How We Build It
Slack's app framework and Salesforce's event APIs pair naturally. Whether the official Slack connector covers you depends on how much writing back you need.
| Approach | What it is | Best for | Watch out for |
|---|---|---|---|
| Salesforce for Slack (official app) | Salesforce's own Slack integration | Record lookup, basic alerts, and channel linking out of the box | Limited customisation; write-backs are constrained |
| Slack Bolt app | A custom Slack app with modals, buttons, and slash commands | Approvals, record updates, and bespoke interactions | You own hosting, auth, and app distribution |
| Salesforce Platform Events | Event-driven pub/sub over the Streaming API | Firing alerts the moment a record changes | Event allocations and delivery limits; needs a subscriber |
| Salesforce Flow + Outbound Messages | Declarative automation with outbound callouts | Simple alerting without writing code | Less control over formatting, batching, and retries |
The failure mode nobody plans for: alert fatigue. A channel that fires on every field change gets muted within a week, and then the integration is worse than nothing. We design the alert rules with the teams who'll receive them, not just the person commissioning the project.
How Much Does It Cost?
A Salesforce + Slack integration typically costs between $3,000 and $14,000 to implement, depending on how much writes back to Salesforce.
| Approach | Implementation | Ongoing |
|---|---|---|
| Alerts and notifications only | $3,000 – $5,500 | Support retainer only |
| Alerts plus approvals & record lookup | $5,500 – $9,500 | Support retainer only |
| Full two-way build with custom Slack app | $9,000 – $14,000+ | Hosting plus support retainer |
The number moves most on whether the integration is read-only or writes back, how many distinct alert rules and channels are involved, and whether a custom Slack app is needed rather than the official connector. We quote a fixed price after a scoping call.
How Long Does It Take?
Deciding who gets alerted about what takes longer than building it — which is why we run that workshop before any code is written.
Alerting build
Pipeline and case alerts routed to the right channels, with sensible thresholds.
Two-way build
Approvals, record updates from modals, slash commands, and case swarming.
What Does Our Integration Process Look Like?
Every engagement follows the same five stages — you get a fixed-price scope and a mapping sheet you sign off before we build.
Discover
We map your channels, teams, and which Salesforce events actually deserve an alert.
Map
We document every trigger, recipient, message format, and write-back rule before building.
Build
We implement against a Salesforce sandbox and a Slack test workspace.
Test
We run real scenarios — approval rejections, permission errors, and alert volume.
Support
We monitor after go-live, with alerting, logging, and a named contact.
Frequently Asked Questions
For record lookup and basic notifications, often yes — and we'll tell you when it is. Approvals, custom modals, and writing structured updates back to Salesforce usually need a custom Slack app.
Yes. A modal presents the fields you choose, validates the input, and writes straight back to the record — which is by far the most reliable way to improve CRM hygiene.
By designing thresholds with the receiving teams and routing by channel rather than broadcasting everything. An alert everyone mutes is worse than no alert at all.
Yes. Discount, quote, and other Salesforce approval requests can be surfaced as interactive messages, with the decision written back and the approval chain respected.
Most projects run $3,000 to $14,000 depending on whether it writes back and how many alert rules are involved. See the cost table above.
It should, and we build it that way — actions run in the context of the linked Salesforce user, so nobody sees or edits records they wouldn't have access to in the CRM.
Ready to Connect Slack to Salesforce?
Every deal discussed in Slack but never logged in Salesforce is a forecast built on guesswork. A scoped integration closes that gap permanently — and you'll know the exact cost before we start.