Integrating Salesforce and Slack is the most common Slack configuration work for Salesforce teams. The standard pattern: install the Salesforce app in Slack, install the Slack app in Salesforce, configure channel-to-record linkages, build Flow-based notifications, and roll out gradually by team. Plan adoption carefully because Slack notification fatigue is real and undisciplined integration produces more noise than value.
- Confirm Slack workspace and Salesforce licensing
Confirm the org has the right Slack edition (free Slack supports basic integration; Business+ and Enterprise Grid add advanced features). Confirm Salesforce has the Slack integration features enabled in the appropriate edition.
- Install the Salesforce app in Slack
From the Slack App Directory, search Salesforce, install. Authenticate to the Salesforce org via OAuth. Configure which Salesforce objects and channels integrate. Set permissions for which users can use the integration.
- Install the Slack package in Salesforce
Setup > Slack > Install. Connect to the Slack workspace via OAuth. Enable the features the use case needs: Flow Slack actions, Sales Engagement integration, Service Cloud Slack channel.
- Configure channel-to-record linkages
For deal rooms or case rooms, link Slack channels to specific Salesforce records. The link surfaces the record in the channel sidebar and the channel under the record. Use Channel Connect for external collaboration with customers.
- Build Flow-based Slack notifications
For record-triggered notifications (high-value Opportunity created, critical Case escalated), build Flows that post to Slack channels. Tune the notification logic to avoid noise; over-notifying produces fatigue and reduced attention.
- Configure Agentforce in Slack if applicable
Enable Agentforce agents to surface in Slack channels. Configure which agents appear, which slash commands invoke them, and how their responses render in conversation.
- Train users and roll out by team
Slack integration adoption depends on user familiarity. Train each team on the slash commands, the notification meaning, and the deal-room or case-room patterns. Roll out by team to manage adoption pace.
- Curate the Slack app set and monitor adoption
App proliferation produces notification fatigue. Curate the approved Slack app list, monitor channel activity for noise, and prune unused integrations periodically.
Free, Pro, Business+, Enterprise Grid. Higher editions add governance, compliance, and Enterprise-Grid centralized administration.
Salesforce-side (Flow notifications, Sales Engagement) and Slack-side (slash commands, CRM cards). Most deployments use both.
Deal Rooms, Case Rooms, custom channel-record bindings. Foundation of contextual collaboration around Salesforce records.
- Notification fatigue is the leading Slack integration failure mode. Over-notifying produces user blindness; under-notifying produces missed important events. Tune the notification logic carefully.
- Slack and Salesforce have separate user identities. SSO between the two is foundational; without it, users hit separate logins and adoption drops sharply.
- Slack data lives in Slack''s infrastructure, not Salesforce''s. Retention, eDiscovery, and compliance scope cover Slack separately. Enterprise Grid supports centralized governance.
- App permissions matter. Each Slack app installed has its own scope; reviewing permissions before installation prevents over-permissioned integrations.
- Slack Connect (shared channels with customers) operates under each organization''s policies. Plan retention, archival, and compliance posture for external collaboration deliberately.