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

How to Send New Salesforce Leads to Slack with Make

Post lead notifications to #sales-leads when new leads are created in Salesforce, including source, company, title, and phone.

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

Sales teams that need formatted lead notifications with source tracking and can work with 15-minute delays.

Not ideal for

Teams requiring instant notifications or complex lead scoring logic in the message format.

Sync type

polling

Use case type

notification

Real-World Example

💡

A 25-person B2B software company uses this to notify their #sales-leads channel whenever a new lead comes from their website, trade shows, or cold outreach. Before automation, SDRs manually checked Salesforce every hour and often missed hot inbound leads for 2-3 hours. Now they see formatted notifications with phone numbers and lead source within 15 minutes, cutting response time in half.

What Will This Cost?

Drag the slider to your expected monthly volume.

1 op per trigger eventEach time this workflow runs counts as one operation toward your monthly limit.
/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 admin access with API permissions enabled
Slack workspace admin rights or ability to install apps
Make account with at least the Core plan for unlimited scenarios
#sales-leads channel created in Slack with proper team members

Optional

Recent lead records in Salesforce for testing the trigger

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
First NameFirstName
Last NameLastName
CompanyCompany
Lead IDId
3 optional fields▸ show
Job TitleTitle
PhonePhone
Lead SourceLeadSource

Step-by-Step Setup

1

Scenarios > + > Salesforce > Watch Records

Create new scenario

Start a fresh Make scenario and add Salesforce as your trigger module. This will monitor for new lead records.

  1. 1Click 'Create a new scenario' from Make dashboard
  2. 2Click the + icon to add your first module
  3. 3Search for 'Salesforce' and select it
  4. 4Choose 'Watch Records' trigger
What you should see: You should see a Salesforce module with 'Watch Records' selected in your scenario canvas.
2

Salesforce Module > Connection > Create

Connect Salesforce account

Link your Salesforce instance to Make using OAuth. This grants Make permission to monitor your leads.

  1. 1Click 'Create a connection' in the Salesforce module
  2. 2Enter your Salesforce login URL (e.g., yourcompany.my.salesforce.com)
  3. 3Click 'Save' then 'Allow' in the Salesforce popup
  4. 4Verify the green 'Connected' status appears
What you should see: The connection dropdown now shows your Salesforce org name with a green checkmark.
Common mistake — Use your actual Salesforce domain, not login.salesforce.com — that causes authentication loops.
Make settings
Connection
Choose a connection…Add
click Add
Salesforce
Log in to authorize
Authorize Make
popup window
Connected
green checkmark
3

Salesforce Module > Settings

Configure lead monitoring

Set the trigger to watch specifically for Lead records. This filters out other Salesforce objects you don't need.

  1. 1Select 'Lead' from the Record Type dropdown
  2. 2Set Trigger Event to 'Created'
  3. 3Leave Output Bundle Limit at 1
  4. 4Set Order By to 'CreatedDate'
What you should see: Your Salesforce module shows Record Type: Lead and Trigger Event: Created.
Common mistake — Don't use 'Created and Updated' — that triggers twice when leads get auto-assigned or scored.
4

Scenario > Run once > Salesforce module output

Test Salesforce connection

Run a test to pull a recent lead record. This validates your connection and shows available data fields.

  1. 1Click 'Run once' at the bottom of the scenario
  2. 2Wait for the test to complete
  3. 3Click on the Salesforce module to view the output
  4. 4Verify you see lead fields like Company, LastName, Phone
What you should see: The test output displays a real lead record with all standard Salesforce lead fields populated.
Common mistake — If no data appears, create a test lead in Salesforce first — the trigger needs recent records to pull.
Make
▶ Run once
executed
Salesforce
Slack
Slack
🔔 notification
received
5

Scenario > + > Slack > Create a Message

Add Slack module

Connect Slack as your action module to send the notification message. This will post to your chosen channel.

  1. 1Click + to add a module after Salesforce
  2. 2Search for 'Slack' and select it
  3. 3Choose 'Create a Message' action
  4. 4Click 'Create a connection' for Slack
What you should see: A Slack module appears connected to your Salesforce trigger with 'Create a Message' selected.
6

Slack Module > Connection > Sign in with Slack

Connect Slack workspace

Authenticate with your Slack workspace and grant Make posting permissions. This allows the bot to send messages.

  1. 1Click 'Sign in with Slack' in the connection popup
  2. 2Select your workspace from the dropdown
  3. 3Click 'Allow' to grant Make permissions
  4. 4Verify the connection shows your workspace name
What you should see: The Slack connection dropdown displays your workspace name with a green connected status.
Common mistake — Make sure you're a Slack admin or have app installation permissions — regular users can't complete OAuth.
7

Slack Module > Send To > Channel

Configure target channel

Select the specific Slack channel where lead notifications should appear. This is typically your sales team's channel.

  1. 1Select 'Channel' from the Send To dropdown
  2. 2Choose '#sales-leads' from the Channel list
  3. 3Leave Enter a User ID blank
  4. 4Set As User to 'false'
What you should see: The channel field shows '#sales-leads' and Send To is set to 'Channel'.
Common mistake — Private channels won't appear in the list unless you invite the Make bot first.
8

Slack Module > Text > Field mapping

Build notification message

Create a formatted message with the lead details your sales team needs. Use Salesforce data fields to populate the content.

  1. 1Click in the Text field to open the mapping panel
  2. 2Type 'New lead: ' then map {{1.FirstName}} {{1.LastName}}
  3. 3Add new lines and map Company: {{1.Company}}
  4. 4Continue with Title: {{1.Title}} and Phone: {{1.Phone}}
What you should see: The text field shows your message template with Salesforce field mappings highlighted in blue pills.
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}}
9

Slack Module > Text > Additional mappings

Add lead source tracking

Include the lead source in your message so reps know which campaigns are working. This helps with lead qualification.

  1. 1Add a new line in the Text field
  2. 2Type 'Source: ' and map {{1.LeadSource}}
  3. 3Add 'Salesforce URL: ' on the next line
  4. 4Map the lead URL using {{1.Id}} in a Salesforce link format
What you should see: Your message template now includes lead source and a clickable Salesforce link.
Common mistake — LeadSource can be empty for manual leads — add a fallback like 'Manual entry' to avoid blank fields.
10

Scenario > Run once > Check Slack channel

Test complete workflow

Run the full scenario to verify the Slack message appears correctly formatted. This validates your field mappings work.

  1. 1Click 'Run once' to execute both modules
  2. 2Wait for both modules to show green checkmarks
  3. 3Check your #sales-leads channel in Slack
  4. 4Verify the message shows all mapped lead data
What you should see: A formatted lead notification appears in Slack with all the lead details you mapped.
Common mistake — If fields show as blank, check that your test lead in Salesforce actually has data in those fields.
11

Scenario > Schedule toggle > 15 minutes

Enable automatic scheduling

Turn on the scenario to run continuously and set the polling interval. This makes the automation live.

  1. 1Click the 'OFF' toggle in the bottom left to turn it 'ON'
  2. 2Set the schedule to run every 15 minutes
  3. 3Click 'OK' to confirm the schedule
  4. 4Verify the scenario shows as 'Active' with a green dot
What you should see: The scenario status shows 'ON' and 'Active' with your 15-minute schedule displayed.
Common mistake — Don't set it to 1-minute intervals — Salesforce API has rate limits and you'll hit them quickly.
12

Slack Module > Right-click > Error handler

Set up error handling

Configure what happens when the scenario fails due to API issues or network problems. This prevents silent failures.

  1. 1Right-click the Slack module and select 'Add error handler'
  2. 2Choose 'Break' as the error handling action
  3. 3Enable email notifications for errors in scenario settings
  4. 4Save the scenario with Ctrl+S
What you should see: An error handler route appears on the Slack module, and the scenario is saved with error notifications enabled.

Drop this into a Make custom function.

JavaScript — Custom Function{{formatDate(1.CreatedDate; "MM/DD/YY h:mm A"; "America/New_York")}}
▸ Show code
{{formatDate(1.CreatedDate; "MM/DD/YY h:mm A"; "America/New_York")}}

... expand to see full code

{{formatDate(1.CreatedDate; "MM/DD/YY h:mm A"; "America/New_York")}}

Scaling Beyond 500+ leads/month+ Records

If your volume exceeds 500+ leads/month records, apply these adjustments.

1

Increase polling interval

Move from 15-minute to 30-minute polling to reduce Salesforce API calls. High-volume orgs hit daily API limits faster, and the slight delay rarely impacts sales response times.

2

Add lead qualification filters

Filter out junk leads or specific sources before posting to Slack. Use Make's filter module between Salesforce and Slack to check fields like Lead Score or Status to reduce noise.

3

Batch notifications for quiet hours

Use Make's scheduling to pause notifications overnight and batch morning summaries. This prevents alert fatigue when leads come in from global time zones while your sales team sleeps.

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 reliable Salesforce polling without coding and want detailed error logs when things break. Make's Salesforce connector handles session refreshes automatically and gives you granular field mapping that Zapier's simplified interface can't match. Skip Make if you need sub-5-minute lead notifications — their minimum polling interval is 1 minute, while webhooks on platforms like n8n can trigger instantly.

Cost

This workflow uses 2 operations per new lead (1 Salesforce poll + 1 Slack message). At 100 new leads per month, that's 200 operations monthly. Make's Core plan includes 10,000 operations for $9/month, so you're covered until 5,000+ leads monthly. Zapier charges $20/month for their Professional plan to handle the same volume. N8n is free for self-hosted, but you'll spend more than $9/month on server costs.

Tradeoffs

Zapier wins on speed — their Salesforce triggers can fire within 30 seconds via webhooks on paid plans, while Make polls every 15 minutes minimum. N8n gives you true real-time webhooks and custom JavaScript for complex message formatting that Make's visual editor can't handle. But Make beats both on error recovery — when Salesforce is down, Make automatically retries failed operations for 24 hours, while Zapier gives up after 3 attempts.

Salesforce's API quirks will trip you up. Their datetime fields come through in GMT, so leads created at 3pm EST show as 8pm in your Slack notifications. Lead assignment rules fire after the API creation event, so your notification might show 'Unassigned' even though the lead gets assigned 2 minutes later. Make's polling also creates a brief delay — your sales team won't see leads for 15+ minutes after creation, which kills hot inbound follow-up speed.

Ideas for what to build next

  • Add lead assignment notificationsCreate a second scenario that watches for lead owner changes and notifies the assigned rep directly via Slack DM.
  • Build a lead response trackerConnect Slack thread replies to Salesforce tasks, so when reps respond to notifications, it logs follow-up activity automatically.
  • Create qualification scoring alertsSet up a parallel workflow that monitors lead score changes and sends priority alerts when high-value leads need immediate attention.

Related guides

Was this guide helpful?
Salesforce + Slack overviewMake profile →