Beginner~12 min setupCRM & CommunicationVerified April 2026
Salesforce logo
Slack logo

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

polling

Use case type

notification

Real-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.

/mo
505005K50K

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

Skip the setup

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.

Salesforce org with Case object access and escalation workflows enabled
Slack workspace admin access to install the Make app
Make account with available operations quota for polling
Support manager channel or user identified in Slack
Test cases in Salesforce to validate the escalation trigger

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Case NumberCaseNumber
Account NameAccount.Name
Priority LevelPriority
Case DescriptionDescription
3 optional fields▸ show
Case OwnerOwner.Name
Escalation DateEscalatedDate
Case Record URLId

Step-by-Step Setup

1

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.

  1. 1Log into Make and click 'Create a new scenario'
  2. 2Click the large '+' button in the center
  3. 3Search for 'Salesforce' in the app list
  4. 4Select the Salesforce icon
What you should see: You should see a Salesforce module placeholder in the center of your scenario canvas.
2

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.

  1. 1Click the Salesforce module to configure it
  2. 2Select 'Watch Records' from the trigger options
  3. 3Choose 'Case' as the Object Type
  4. 4Set Watch Events to 'Updated'
  5. 5In the Formula field, enter: IsEscalated = true
What you should see: The configuration panel should show Case object selected with the escalation formula in place.
Common mistake — Don't use 'New Records' - you need 'Updated' to catch escalation changes on existing cases.
Make
+
click +
search apps
Salesforce
SA
Salesforce
Configure Salesforce Trigger
Salesforce
SA
module added
3

Salesforce Module > Connection > Add Connection

Connect Salesforce Account

Authenticate your Salesforce connection using your org credentials. Make needs read access to case records.

  1. 1Click 'Add' next to the Connection field
  2. 2Enter your Salesforce username and password
  3. 3Add your security token at the end of your password
  4. 4Select your Salesforce environment (Production or Sandbox)
  5. 5Click 'Save' to establish connection
What you should see: You should see a green 'Connected' status next to your Salesforce connection name.
Common mistake — Your security token changes when you reset your password - grab the latest one from Salesforce Setup > Personal Information.
Make settings
Connection
Choose a connection…Add
click Add
Salesforce
Log in to authorize
Authorize Make
popup window
Connected
green checkmark
4

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.

  1. 1Click 'Run once' at the bottom of the Salesforce module
  2. 2Go to Salesforce and escalate a test case manually
  3. 3Return to Make and check if the test case appears
  4. 4Verify all required fields are populated
What you should see: The test panel should display your escalated case with CaseNumber, Account.Name, Priority, and Description fields visible.
Common mistake — If no data appears, check your user permissions in Salesforce - you need 'View All' on Case objects.
Make
▶ Run once
executed
Salesforce
Slack
Slack
🔔 notification
received
5

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.

  1. 1Click the '+' button to the right of the Salesforce module
  2. 2Search and select 'Slack' from the apps list
  3. 3Choose 'Create a Message' as the action
  4. 4Leave the configuration panel open for the next step
What you should see: A Slack module should now appear connected to your Salesforce trigger with configuration options visible.
6

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.

  1. 1Click 'Add' next to Connection in the Slack module
  2. 2Click 'Authorize' to open Slack OAuth window
  3. 3Select your workspace from the dropdown
  4. 4Grant Make permission to post messages
  5. 5Return to Make to confirm connection
What you should see: Your workspace name should appear in the Connection dropdown with a green connected indicator.
Common mistake — Only Slack admins can install apps - if you get a permission error, ask your Slack admin to approve Make first.
7

Slack Module > Configuration > Channel Selection

Select Target Channel

Choose which Slack channel receives escalation alerts. Pick a channel your support manager monitors actively.

  1. 1In the Slack module, click the Channel dropdown
  2. 2Select the channel where alerts should go
  3. 3If the channel doesn't appear, type the channel name manually
  4. 4Ensure the channel allows app messages
What you should see: Your selected channel name should display in the Channel field, either from the dropdown or manually entered.
Common mistake — Private channels won't appear in the dropdown - you must invite the Make app to private channels first in Slack.
message template
🔔 New Record: {{FirstName}} {{LastName}}
Email: {{Email}}
Company: {{Company}}
#sales
🔔 New Record: Jane Smith
Company: Acme Corp
8

Slack Module > Text Field > Data Mapping

Build Alert Message

Create the message template with case details. Map Salesforce fields to create an informative alert.

  1. 1Click in the Text field of the Slack module
  2. 2Type: '🚨 Case Escalated: '
  3. 3Click the data picker and select CaseNumber
  4. 4Add new line and type 'Account: '
  5. 5Map Account.Name from Salesforce data
  6. 6Add Priority and Description fields on separate lines
What you should see: Your message template should show mapped Salesforce fields with clear labels for case number, account, priority, and description.
Common mistake — Use Account.Name not AccountId - the ID field shows Salesforce internal codes that aren't useful in Slack.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
9

Slack Module > Text Field > Message Formatting

Format Message Layout

Structure the alert for quick scanning by support managers. Use emojis and formatting for clarity.

  1. 1Add line breaks between each field
  2. 2Include priority emoji: High = 🔴, Medium = 🟡, Low = 🟢
  3. 3Add a Salesforce record URL using Id field
  4. 4Preview the message format in the text box
What you should see: The message should be well-formatted with clear field labels, appropriate emojis, and a direct link to the Salesforce case.
Common mistake — Map fields using the variable picker — don't type field names manually. Hand-typed variable names often have invisible spacing errors that produce blank output.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
10

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.

  1. 1Click 'Run once' on the entire scenario
  2. 2Escalate another test case in Salesforce
  3. 3Wait 30 seconds for Make to process
  4. 4Check your Slack channel for the alert
  5. 5Verify all case details appear correctly
What you should see: A formatted escalation alert should appear in your Slack channel with case number, account name, priority level, and description.
Common mistake — Make's Salesforce polling runs every 15 minutes by default - alerts won't be instant unless you upgrade to a faster interval.
11

Scenario Canvas > Schedule Settings > Enable

Enable Scenario

Turn on the automation to start monitoring for case escalations. Set the appropriate scheduling interval.

  1. 1Click the toggle switch in the bottom left to 'ON'
  2. 2Set scheduling to run every 5 minutes for faster alerts
  3. 3Click 'OK' to confirm the schedule
  4. 4Verify the scenario shows as 'Active'
What you should see: The scenario status should display 'Active' with your chosen polling interval visible in the schedule settings.
Common mistake — Faster polling intervals consume more operations - 5-minute intervals use 288 operations per day versus 96 for 15-minute intervals.

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.

1

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.

2

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.

3

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

VerdictWhy Make for this workflow

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.

Cost

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.

Tradeoffs

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 UpdatesCreate a follow-up scenario that posts thread replies when escalated cases get resolved or reassigned to track outcomes.
  • Build Escalation DashboardSend case data to Google Sheets to track escalation patterns, response times, and support manager workload over time.
  • Create Manager Response TrackingMonitor when support managers react to escalation alerts in Slack and measure average response times for performance metrics.

Related guides

Was this guide helpful?
Salesforce + Slack overviewMake profile →