What happens if a user's Slack email doesn't match their Salesforce email?

The Slack user lookup fails and the scenario stops unless you add error handling. Set up a fallback that posts to a general channel with @mentions, or maintain a manual mapping sheet for mismatched emails.

Can this work with Salesforce Lead and Contact tasks, not just Account tasks?

Yes, the WhatId field captures any related record type. Your message template can use {{WhatId}} to link to leads, contacts, opportunities, or cases. The Salesforce API returns the correct object type automatically.

How do I prevent notifications for tasks I create for myself?

Add a filter checking if CreatedById equals OwnerId and exclude those matches. This stops self-assigned tasks from generating notifications while still notifying when managers assign tasks to team members.

Does this trigger for task updates or only new task creation?

Only new tasks with the 'Created' trigger setting. If you want reassignment notifications, add a second scenario with 'Updated' trigger that filters for OwnerId changes. Don't use 'Updated' for everything - it fires on every field edit.

Beginner~12 min setupCRM & CommunicationVerified April 2026

How to Send Salesforce Task Notifications to Slack with Make

Send direct messages to Slack users when they're assigned new Salesforce tasks, including due date and priority details.

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 →

Make

Also on:Zapier N8n

Best for

Sales and support teams needing instant task assignment notifications with detailed context in Slack

Not ideal for

Teams on Salesforce Professional edition or those who batch-assign tasks in bulk operations

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 25-person B2B software sales team uses this to notify account managers immediately when support creates follow-up tasks from customer issues. Before automation, AMs checked Salesforce 2-3 times per day and customer follow-ups sat unnoticed for hours. Now they respond within 30 minutes because the Slack DM includes priority level and links directly to the related account record.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

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.

Admin access to Salesforce with API permissions enabled

Slack workspace admin rights to install Make bot

Make account with at least Basic plan for real-time triggers

Matching email addresses between Salesforce users and Slack profiles

Optional

Custom fields or standard task setup in Salesforce for priority/due dates

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Task Subject	`Subject`	The task title that appears in Slack notification header
Assigned User ID	`OwnerId`	Salesforce user ID of the person assigned the task
User Email	`User.Email`	Email from user lookup to match with Slack profile

4 optional fields▸ show

Due Date	`ActivityDate`	When the task is due, formatted as readable date in Slack message
Priority Level	`Priority`	High/Medium/Low priority value to emphasize urgent tasks
Related Record	`WhatId`	ID of the account, opportunity, or case this task relates to
Task Description	`Description`	Full task details to include in the Slack message body

Step-by-Step Setup

Dashboard > Create scenario > Salesforce

Create New Scenario

Start a fresh scenario in Make to connect Salesforce task creation to Slack notifications. This becomes the foundation for your task notification workflow.

1Click the blue '+ Create a new scenario' button on your Make dashboard
2Click the large gray '+' circle in the center of the canvas
3Type 'Salesforce' in the search box and select it from the app list

✓ What you should see: You should see the Salesforce app icon on your canvas with configuration options displayed on the right panel.

Salesforce module > Watch Records

Configure Salesforce Trigger

Set up the trigger to fire when new tasks are created in Salesforce. This monitors task assignments in real-time through Salesforce's streaming API.

1Select 'Watch Records' from the trigger options
2Choose your Salesforce connection or click 'Add' to create one
3Set Object Type to 'Task'
4Set Trigger to 'Created'

✓ What you should see: The configuration panel shows 'Task' as the object type and 'Created' as the trigger event.

⚠

Common mistake — Don't select 'Updated' trigger - it fires on every task edit and will spam your notifications

Make

click +

search apps

Salesforce

Configure Salesforce Trigger

Salesforce

module added

Module connector > Filter

Filter for Assigned Tasks

Add a filter to only process tasks that have been assigned to specific users. This prevents notifications for unassigned administrative tasks.

1Click the small wrench icon between modules to add a filter
2Name the filter 'Has Assignee'
3Set condition: OwnerId 'Is not equal to' (empty)
4Click OK to save the filter

✓ What you should see: A small filter icon appears on the connection line between your modules.

⚠

Common mistake — Test this filter with actual Salesforce data - some orgs use different fields for task ownership

Salesforce

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Slack

notified

Add module > Salesforce > Get a Record

Add Salesforce User Lookup

Look up the assigned user's details from Salesforce to get their email address. This email will match against Slack user profiles.

1Click the '+' button after your filter
2Select Salesforce from the apps list
3Choose 'Get a Record' action
4Set Object Type to 'User'
5Map Record ID to the OwnerId from the previous step

✓ What you should see: The module shows 'Get a Record - User' with OwnerId mapped to the Record ID field.

Add module > Slack > Get a User

Add Slack User Lookup

Find the corresponding Slack user by matching their email address. This connects the Salesforce user to their Slack account for direct messaging.

1Click '+' to add another module
2Search for and select 'Slack'
3Choose 'Get a User' action
4Connect your Slack workspace
5Map the User field to the Email from the Salesforce user lookup

✓ What you should see: Slack module configured with the Salesforce user's email mapped to find their Slack profile.

⚠

Common mistake — This fails if Salesforce emails don't match Slack emails - you'll need manual mapping for those users

Add module > Tools > Text aggregator

Format Task Details

Create a formatted message that includes all relevant task information. This makes the Slack notification actionable and informative.

1Add a 'Text aggregator' or 'Set variable' module
2Create a text template with task details
3Include Subject, Due Date, Priority, and Related Record fields
4Add Salesforce task URL for quick access

✓ What you should see: A formatted text block showing task details in a readable format for Slack.

⚠

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.

Add module > Slack > Send a Direct Message

Send Direct Message

Configure the Slack direct message with the formatted task details. This delivers the notification directly to the assigned user's DM.

1Add a Slack 'Send a Direct Message' module
2Map User ID from the Slack user lookup
3Paste your formatted message template in the Text field
4Set the message as 'mrkdwn' format for better formatting

✓ What you should see: Slack DM module configured with user ID and formatted message template.

⚠

Common mistake — Test with your own user first - some Slack workspaces restrict DMs from bots

Message template

🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}

message template

🔔 New Record: {{FirstName}} {{LastName}}
Email: {{Email}}
Company: {{Company}}

#sales

🔔 New Record: Jane Smith

Email: [email protected]

Company: Acme Corp

Module context menu > Add error handler

Add Error Handling

Configure what happens when users can't be found in Slack or other errors occur. This prevents the entire scenario from breaking on edge cases.

1Right-click the Slack user lookup module
2Select 'Add error handler'
3Choose 'Resume' directive
4Add a fallback notification to a general channel

✓ What you should see: Error handling route appears with dotted lines, showing the fallback path.

Scenario controls > Run once

Test the Workflow

Run a test to verify the complete flow works with real Salesforce data. This validates all connections and field mappings before going live.

1Click 'Run once' at the bottom of the screen
2Create a test task in Salesforce assigned to yourself
3Watch the scenario execution in real-time
4Check your Slack DMs for the notification

✓ What you should see: Scenario runs successfully and you receive a formatted DM in Slack with task details.

⚠

Common mistake — Don't test with production data initially - create a dedicated test task to avoid confusing your team

Make

▶ Run once

executed

✓

Salesforce

✓

Slack

🔔 notification

received

Scenario controls > Scheduling

Schedule and Activate

Turn on the scenario to run continuously and monitor for new task assignments. Set appropriate scheduling based on your notification urgency needs.

1Click the toggle switch to 'ON'
2Set scheduling to 'Immediately' for real-time notifications
3Click 'OK' to activate the scenario
4Monitor the execution history for the first few hours

✓ What you should see: Scenario shows as 'Active' with a green status indicator and begins processing new tasks automatically.

⚠

Common mistake — Start with 5-minute intervals if you have concerns about API limits, then move to real-time once stable

Drop this into a Make custom function.

JavaScript — Custom Function{{formatDate(ActivityDate; "MMM DD, YYYY")}} priority: {{upper(Priority)}} - <https://{{your-instance}}.salesforce.com/{{Id}}|View Task>

▸ Show code

{{formatDate(ActivityDate; "MMM DD, YYYY")}} priority: {{upper(Priority)}} - <https://{{your-instance}}.salesforce.com/{{Id}}|View Task>

... expand to see full code

{{formatDate(ActivityDate; "MMM DD, YYYY")}} priority: {{upper(Priority)}} - <https://{{your-instance}}.salesforce.com/{{Id}}|View Task>

Scaling Beyond 200+ tasks/day+ Records

If your volume exceeds 200+ tasks/day records, apply these adjustments.

Batch Notifications

Group multiple task assignments per user into digest messages sent every 15-30 minutes instead of individual DMs. This reduces operations and prevents Slack notification fatigue.

Cache User Lookups

Store Salesforce-to-Slack user mappings in a Google Sheet or Make data store to avoid repeated API calls. Update the cache weekly rather than looking up users on every task.

Filter Task Types

Add filters to exclude routine tasks like 'Call customer' and only notify for high-priority or customer-facing tasks. This cuts notification volume by 60-70% in most sales orgs.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test error handling with non-existent Slack users

Applies when: Always

Verify Salesforce streaming API connection stays active during maintenance windows

Applies when: Always

Set up operation usage monitoring to avoid mid-month cutoffs

Applies when: Always

Create fallback channel for failed user lookups

Applies when: Always

Filter out system-created and bulk-imported tasks

Applies when: High volume

Add rate limiting if processing 50+ tasks per hour

Applies when: High volume

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 your team needs instant task notifications and you're already on Salesforce Enterprise or higher. Make's real-time streaming triggers fire within 30 seconds of task creation, unlike polling-based systems that check every 5-15 minutes. The visual scenario builder also makes it easy to add conditional logic for different task types or priorities. Skip Make if you're on Salesforce Professional edition - you'll need polling triggers that defeat the purpose of instant notifications. Go with Zapier's polling approach instead.

Cost

This workflow burns 4 operations per task assignment - Salesforce trigger, user lookup, Slack user search, and DM send. At 100 tasks per month, that's 400 operations total. Make's Core plan at $9/month includes 10,000 operations, so you're covered until 2,500+ monthly tasks. Zapier's equivalent runs $20/month for 750 tasks, and their unlimited plan is $49/month. N8N self-hosted is free but requires server maintenance. Make wins on cost until you hit enterprise volume.

Tradeoffs

Zapier handles Salesforce Professional edition better with reliable polling triggers that Make struggles with. N8N offers more advanced text formatting and regex capabilities for complex message templates. But Make's error handling is superior - when a Slack user isn't found, you can route to fallback channels or retry logic without breaking the entire flow. Zapier just fails and stops, while N8N requires custom error handling code.

Salesforce's streaming API occasionally drops connections during maintenance windows, causing 1-2 hour gaps in notifications. You won't know until someone complains about missing a task. The user lookup fails if people use different emails in Salesforce vs Slack - common in companies with multiple email domains or acquired teams. Make's operation counting includes failed attempts, so testing scenarios burns through your monthly limit quickly if you're not careful with your quota.

Ideas for what to build next

→
Add Task Completion Tracking — Create a follow-up scenario that posts to team channels when high-priority tasks are marked complete, keeping everyone updated on customer issue resolution.
→
Escalate Overdue Tasks — Build a scheduled scenario that checks for overdue tasks daily and sends reminder DMs with manager CC, ensuring nothing falls through the cracks.
→
Create Task Analytics Dashboard — Log all task assignments to Google Sheets or Airtable to track response times and workload distribution across your team.