

How to Send Salesforce Case Escalations to Slack with Make
Automatically notify your support manager in Slack whenever a Salesforce case gets escalated, including case details and priority level.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Slack for Salesforce exists as a native integration, but it limited to record notifications without custom logic. This guide uses an automation platform for full control. View native option →
Best for
Support teams that need formatted escalation alerts with case details sent to specific Slack channels.
Not ideal for
Teams wanting instant real-time alerts or those with fewer than 20 case escalations per month.
Sync type
pollingUse case type
notificationReal-World Example
A 25-person B2B software company uses this to alert their support director in #escalations whenever a customer case gets bumped to management level. Before automation, escalated cases sat unnoticed for hours because the director had to manually scan Salesforce dashboards. Now critical customer issues get management attention within 10 minutes of escalation.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Import this workflow directly into Make
Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Case Number | CaseNumber | |
| Account Name | Account.Name | |
| Priority Level | Priority | |
| Case Description | Description | |
3 optional fields▸ show
| Case Owner | Owner.Name |
| Escalation Date | EscalatedDate |
| Case Record URL | Id |
Step-by-Step Setup
Dashboard > Create scenario > Add module
Create New Scenario
Start a fresh Make scenario to connect Salesforce case escalations to Slack. This sets up the automation foundation.
- 1Log into Make and click 'Create a new scenario'
- 2Click the large '+' button in the center
- 3Search for 'Salesforce' in the app list
- 4Select the Salesforce icon
Salesforce Module > Trigger Type > Configuration
Configure Salesforce Trigger
Set up the trigger to fire when cases are escalated. Use the 'Watch Records' trigger to catch field changes in real-time.
- 1Click the Salesforce module to configure it
- 2Select 'Watch Records' from the trigger options
- 3Choose 'Case' as the Object Type
- 4Set Watch Events to 'Updated'
- 5In the Formula field, enter: IsEscalated = true
Salesforce Module > Connection > Add Connection
Connect Salesforce Account
Authenticate your Salesforce connection using your org credentials. Make needs read access to case records.
- 1Click 'Add' next to the Connection field
- 2Enter your Salesforce username and password
- 3Add your security token at the end of your password
- 4Select your Salesforce environment (Production or Sandbox)
- 5Click 'Save' to establish connection
Salesforce Module > Run once > Test Results
Test Salesforce Connection
Verify Make can read your case data and the escalation trigger works properly. This prevents issues later.
- 1Click 'Run once' at the bottom of the Salesforce module
- 2Go to Salesforce and escalate a test case manually
- 3Return to Make and check if the test case appears
- 4Verify all required fields are populated
Scenario Canvas > Add Module > Slack > Create Message
Add Slack Module
Connect Slack to send the escalation alert. Position it after the Salesforce trigger in your workflow.
- 1Click the '+' button to the right of the Salesforce module
- 2Search and select 'Slack' from the apps list
- 3Choose 'Create a Message' as the action
- 4Leave the configuration panel open for the next step
Slack Module > Connection > Add > OAuth Authorization
Connect Slack Workspace
Authenticate with your Slack workspace where escalation alerts should be sent. Make needs message posting permissions.
- 1Click 'Add' next to Connection in the Slack module
- 2Click 'Authorize' to open Slack OAuth window
- 3Select your workspace from the dropdown
- 4Grant Make permission to post messages
- 5Return to Make to confirm connection
Slack Module > Configuration > Channel Selection
Select Target Channel
Choose which Slack channel receives escalation alerts. Pick a channel your support manager monitors actively.
- 1In the Slack module, click the Channel dropdown
- 2Select the channel where alerts should go
- 3If the channel doesn't appear, type the channel name manually
- 4Ensure the channel allows app messages
Email: {{Email}}
Company: {{Company}}
Slack Module > Text Field > Data Mapping
Build Alert Message
Create the message template with case details. Map Salesforce fields to create an informative alert.
- 1Click in the Text field of the Slack module
- 2Type: '🚨 Case Escalated: '
- 3Click the data picker and select CaseNumber
- 4Add new line and type 'Account: '
- 5Map Account.Name from Salesforce data
- 6Add Priority and Description fields on separate lines
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}Slack Module > Text Field > Message Formatting
Format Message Layout
Structure the alert for quick scanning by support managers. Use emojis and formatting for clarity.
- 1Add line breaks between each field
- 2Include priority emoji: High = 🔴, Medium = 🟡, Low = 🟢
- 3Add a Salesforce record URL using Id field
- 4Preview the message format in the text box
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}Scenario Canvas > Run Once > Check Slack Channel
Test Complete Workflow
Run the full scenario end-to-end to verify escalation alerts work correctly. This catches any mapping issues.
- 1Click 'Run once' on the entire scenario
- 2Escalate another test case in Salesforce
- 3Wait 30 seconds for Make to process
- 4Check your Slack channel for the alert
- 5Verify all case details appear correctly
Scenario Canvas > Schedule Settings > Enable
Enable Scenario
Turn on the automation to start monitoring for case escalations. Set the appropriate scheduling interval.
- 1Click the toggle switch in the bottom left to 'ON'
- 2Set scheduling to run every 5 minutes for faster alerts
- 3Click 'OK' to confirm the schedule
- 4Verify the scenario shows as 'Active'
Drop this into a Make custom function.
JavaScript — Custom FunctionAdd this filter after Salesforce to prevent duplicate alerts:▸ Show code
Add this filter after Salesforce to prevent duplicate alerts:
{{formatDate(EscalatedDate; "X")}} > {{timestamp - 1800}}
This only processes cases escalated in the last 30 minutes, preventing old escalations from triggering alerts when you first enable the scenario.... expand to see full code
Add this filter after Salesforce to prevent duplicate alerts:
{{formatDate(EscalatedDate; "X")}} > {{timestamp - 1800}}
This only processes cases escalated in the last 30 minutes, preventing old escalations from triggering alerts when you first enable the scenario.Scaling Beyond 200+ escalations/month+ Records
If your volume exceeds 200+ escalations/month records, apply these adjustments.
Switch to Webhook Trigger
Replace polling with Salesforce webhook to get instant alerts and reduce operation usage by 90%. Configure webhook in Salesforce Setup > Remote Site Settings.
Add Conditional Routing
Route high-priority escalations to a dedicated Slack channel and page the on-call manager. Use Make's router module to split based on Priority field values.
Implement Message Throttling
Add a filter to prevent spam if the same case gets escalated multiple times. Check if a message for this CaseNumber was sent in the last 2 hours.
Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Make for this if you need custom message formatting and your team escalates 50+ cases per month. Make's visual builder makes it easy to add conditional formatting based on priority levels, and you can route different case types to different Slack channels. Skip Make if you just want basic notifications - Salesforce Flow can push to Slack directly without a third-party platform.
This workflow uses 2 operations per escalated case - one Salesforce poll plus one Slack message. At 100 escalations monthly with 5-minute polling intervals, you'll burn through 8,760 operations total (100 messages + 8,660 polling checks). That fits Make's Core plan at $10.59/month. Zapier would cost $19.99/month for the same volume since their starter plan caps at 750 tasks. Make saves you $113 annually.
Zapier handles Salesforce datetime fields better - their formatter automatically converts Salesforce's weird timestamp format to readable dates. N8n gives you more control over error handling with custom retry logic and dead letter queues for failed messages. But Make wins on the visual mapping interface - building conditional message formats is point-and-click instead of writing JSON transforms.
Salesforce's API has a 15-minute delay on escalation field updates due to their workflow processing queue. Your alerts might lag behind the actual escalation by 10-20 minutes during peak hours. Also, if someone manually toggles IsEscalated on and off quickly, Make will send duplicate alerts since it can't detect the toggle sequence. The polling approach means you'll miss escalations that get resolved before the next check runs.
Ideas for what to build next
- →Add Slack Thread Updates — Create a follow-up scenario that posts thread replies when escalated cases get resolved or reassigned to track outcomes.
- →Build Escalation Dashboard — Send case data to Google Sheets to track escalation patterns, response times, and support manager workload over time.
- →Create Manager Response Tracking — Monitor when support managers react to escalation alerts in Slack and measure average response times for performance metrics.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup