Salesforce and Slack Integration

What This Integration Does

This integration pushes Salesforce opportunity updates, case escalations, lead assignments, and custom object changes into Slack channels as structured, real-time notifications. Your team sees pipeline movement, support escalations, and lead activity without leaving Slack.

Salesforce’s own Slack integration covers basic use cases, but it falls short when you need custom routing logic, enriched message payloads, or notifications triggered by complex conditions. This custom integration uses Salesforce’s Streaming API and Platform Events to capture changes the moment they happen, then delivers precisely formatted Slack messages based on rules that reflect your actual business processes. For the full picture of what the Salesforce API side involves, see the Salesforce API Integration page.

An opportunity moving to “Closed Won” does not just trigger a generic alert. It posts to the revenue channel with the account name, deal value, close date, opportunity owner, and a breakdown of products sold. Everything is formatted for quick scanning with a direct link back to the Salesforce record.

The Workflow

Salesforce publishes events through its Streaming API using PushTopic or Platform Event channels. The integration subscribes to these channels via a persistent connection, receiving notifications within seconds of any tracked change.

Each event is validated and queued. The processing layer queries Salesforce’s REST API to enrich the notification with related data. For an opportunity event, that means account details; for a case escalation, contact history; for a new lead, campaign attribution. This enrichment step is what separates a useful notification from a bare “record changed” alert.

Routing rules determine which Slack channel receives each notification. These rules can evaluate any Salesforce field: opportunity amount, record type, account tier, lead source, case priority, or custom fields specific to your org. A high-priority case escalation goes to the support leadership channel. A mid-market opportunity stage change goes to the regional sales channel. A new enterprise lead goes to the named account team’s private channel.

Slack messages are built with the Block Kit API, giving each notification a clean layout with headers, key-value fields, and action buttons where appropriate. Messages include enough context to understand the event without opening Salesforce, but always link back for deeper investigation.

Before and After

Before: Account executives check Salesforce dashboards periodically throughout the day. Case escalations are noticed when someone reviews the queue, which might be minutes or hours after the fact. Opportunity stage changes are communicated verbally or in email threads, reaching stakeholders inconsistently. Sales leadership pieces together pipeline movement from weekly reports rather than seeing it unfold.

After: Every meaningful Salesforce event reaches the right people in Slack within seconds. Support escalations trigger immediate visibility for the team lead. Opportunity wins are celebrated in real time. Pipeline movement is visible to leadership as it happens, not in a retrospective report. The Salesforce data that matters most arrives where the team already communicates.

Who Needs This

Organisations running Salesforce as their CRM where Slack is the primary internal communication tool. This integration delivers the most value when multiple teams (sales, support, customer success, and leadership) all need visibility into Salesforce activity but have different information requirements.

Enterprise sales teams with complex opportunity structures benefit from notifications that include product line details, multi-currency values, and approval stage tracking. Support teams using Salesforce Cases gain immediate escalation visibility. Customer success teams can monitor health score changes and renewal dates as they update in Salesforce.

If your Salesforce org uses custom objects or has heavily customised record types, the native Slack integration likely cannot surface those changes. A custom build handles whatever your data model looks like. If HubSpot is your CRM rather than Salesforce, the HubSpot and Slack Integration follows the same architecture.

How We Build This

We begin by auditing your Salesforce org to understand the data model: standard objects, custom objects, record types, and the fields that carry decision-relevant information. Then we work with your team to define which events justify a notification and who should receive each one.

The integration uses Salesforce’s Streaming API for real-time change capture, with a CometD client maintaining a persistent subscription. For complex event conditions that the Streaming API cannot filter, we use Salesforce Platform Events published by Process Builder or Flow automations within your org.

The Slack delivery layer uses the Web API with Block Kit formatting. We build message templates for each event type and test them with your team to ensure the information hierarchy matches how people actually read Slack notifications.

Deployment includes monitoring for connection health, event processing latency, and delivery confirmation. The Streaming API connection is automatically re-established if interrupted, and missed events are recovered using Salesforce’s replay mechanism.

Build time is typically three to four weeks, accounting for the additional complexity of Salesforce’s event infrastructure compared to simpler webhook-based systems.

Ready to Connect Salesforce and Slack?

If your team is context-switching between Salesforce and Slack dozens of times per day, this integration brings the CRM data to the conversation. Talk to us about what a tailored setup looks like. If you are unsure whether a custom API connection is right for your situation, the Can You Connect to Our CRM? page covers the questions we hear most often.