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

How to Send Salesforce Lead Notifications to Slack with Zapier

Automatically post new Salesforce leads to a Slack channel with source, company, title and phone details for instant rep follow-up.

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 under 1000 leads/month who need instant Slack alerts without coding custom integrations.

Not ideal for

High-volume teams processing 2000+ leads monthly where webhook costs become prohibitive.

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person B2B SaaS sales team uses this to notify #hot-leads whenever a new Enterprise prospect fills out their demo request form and enters Salesforce. Before automation, reps checked Salesforce manually every hour and often missed high-value leads for 2-3 hours. Now they respond within 10 minutes, improving demo booking rates by 40%.

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

Before You Start

Make sure you have everything ready.

Salesforce administrator access with API permissions to read Lead records
Slack workspace admin rights to install apps and post to target sales channels
At least one existing Lead record in Salesforce for testing the trigger
Active Zapier account with available task credits
Your Salesforce org's custom domain URL for building record links

Field Mapping

Map these fields between your apps.

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

Step-by-Step Setup

1

Dashboard > Create Zap > Salesforce

Create new Zap and connect Salesforce

Start building your automation by creating a new Zap and connecting your Salesforce account. This establishes the trigger that will fire whenever a new lead enters your CRM.

  1. 1Click 'Create Zap' from your Zapier dashboard
  2. 2Search for 'Salesforce' in the app picker
  3. 3Select 'New Record' as your trigger event
  4. 4Click 'Continue' to proceed to connection setup
What you should see: You should see the Salesforce trigger configured with 'New Record' selected as the event type.
2

Trigger > Account Connection

Authenticate Salesforce connection

Connect your Salesforce org to Zapier using OAuth authentication. This gives Zapier read access to detect new leads as they're created.

  1. 1Click 'Sign in to Salesforce' button
  2. 2Enter your Salesforce username and password
  3. 3Click 'Allow' when prompted for permissions
  4. 4Verify the connection shows your org name
What you should see: A green checkmark appears next to your Salesforce account with your org name displayed.
Common mistake — Use your production Salesforce login, not a sandbox - sandbox leads won't reflect real prospect activity.
3

Trigger > Set up trigger > Object

Configure Lead object trigger

Specify that you want to monitor the Lead object specifically, not all Salesforce records. This focuses the trigger on new prospects entering your sales funnel.

  1. 1Select 'Lead' from the Object dropdown menu
  2. 2Leave 'Created Date' field mapping as default
  3. 3Click 'Continue' to move to test phase
  4. 4Wait for Zapier to load available Lead fields
What you should see: The trigger setup shows 'Lead' selected with a list of available Lead fields like Company, Email, Phone, and Lead Source.
Common mistake — Don't select 'Contact' by mistake - that triggers on existing customers, not new prospects.
Zapier
+
click +
search apps
Salesforce
SA
Salesforce
Configure Lead object trigger
Salesforce
SA
module added
4

Trigger > Test

Test Salesforce trigger

Zapier pulls a recent lead from your Salesforce to use as test data. This sample will show you exactly which fields are available for your Slack message.

  1. 1Click 'Test trigger' button
  2. 2Review the sample lead data that appears
  3. 3Verify key fields like Company, Title, Phone, and LeadSource have values
  4. 4Click 'Continue with selected record'
What you should see: A sample lead record displays showing fields like FirstName: 'John', Company: 'Acme Corp', Title: 'VP Sales', Phone: '555-123-4567'.
Common mistake — If no test data appears, create a dummy lead in Salesforce first - Zapier needs at least one recent record to proceed.
Zapier
▶ Turn on & test
executed
Salesforce
Slack
Slack
🔔 notification
received
5

Action > Choose App > Slack

Add Slack action step

Configure Slack as your action app to receive the lead notifications. This is where you'll format and send the message to your sales team.

  1. 1Click the '+' button to add an action step
  2. 2Search for and select 'Slack' from the app list
  3. 3Choose 'Send Channel Message' as the action event
  4. 4Click 'Continue' to connection setup
What you should see: The action step shows Slack selected with 'Send Channel Message' configured as the event type.
6

Action > Account Connection

Connect Slack workspace

Authenticate your Slack workspace so Zapier can post messages to your channels. Make sure you're connecting the workspace where your sales team operates.

  1. 1Click 'Sign in to Slack' button
  2. 2Select your company workspace from the dropdown
  3. 3Click 'Allow' to grant Zapier posting permissions
  4. 4Confirm the workspace name appears correctly
What you should see: Your Slack workspace appears connected with a green checkmark and your workspace name displayed.
Common mistake — Connect to your main company workspace, not a personal one - you need access to sales channels.
Zapier settings
Connection
Choose a connection…Add
click Add
Salesforce
Log in to authorize
Authorize Zapier
popup window
Connected
green checkmark
7

Action > Set up action > Channel

Select target channel

Choose the specific Slack channel where lead notifications will be posted. This should be a channel your sales reps monitor actively for quick response.

  1. 1Click the 'Channel' dropdown menu
  2. 2Select '#sales-leads' or your preferred sales channel
  3. 3Verify the channel name appears correctly
  4. 4Leave 'Bot Name' as default or customize
What you should see: The channel dropdown shows your selected channel, like '#sales-leads', with the channel ID populated automatically.
Common mistake — Pick a dedicated sales channel, not #general - you don't want lead notifications buried in random chatter.
message template
🔔 New Record: {{FirstName}} {{LastName}}
Email: {{Email}}
Company: {{Company}}
#sales
🔔 New Record: Jane Smith
Company: Acme Corp
8

Action > Set up action > Message Text

Format lead notification message

Build the message template that will post to Slack with key lead details. Include the specific fields reps need to qualify and contact the lead quickly.

  1. 1Click in the 'Message Text' field
  2. 2Type: '🚨 New Lead Alert!' and press Enter twice
  3. 3Add mapped fields: 'Name: {{FirstName}} {{LastName}}'
  4. 4Continue with: 'Company: {{Company}}', 'Title: {{Title}}', 'Phone: {{Phone}}', 'Source: {{LeadSource}}'
What you should see: The message preview shows your template with placeholder values from the test lead, formatted as a clear lead summary.
Common mistake — Don't include sensitive fields like Lead Score or internal notes - keep it to contact info and qualification basics.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
9

Action > Set up action > Message Text

Add Salesforce record link

Include a direct link to the Salesforce lead record so reps can access full details with one click. This eliminates the need to search for the lead manually.

  1. 1Add a new line after the lead details
  2. 2Type: 'View in Salesforce: ' (with space after colon)
  3. 3Map the {{Id}} field from Salesforce data
  4. 4Prepend your Salesforce org URL like: 'https://yourorg.salesforce.com/{{Id}}'
What you should see: The message template now includes a clickable Salesforce URL that will take reps directly to the lead record.
Common mistake — Use your actual Salesforce domain (like 'companyname.salesforce.com'), not the generic lightning.force.com URL.
10

Action > Test

Test complete workflow

Run a full test to verify the integration works end-to-end. This confirms the message format looks correct and posts to the right channel.

  1. 1Click 'Test action' at the bottom of the setup
  2. 2Check your Slack channel for the test message
  3. 3Verify all lead fields populated correctly
  4. 4Click the Salesforce link to confirm it works
What you should see: A formatted lead notification appears in your Slack channel with all mapped fields showing real data from the test lead.
Common mistake — The test posts to your actual Slack channel - warn your team that test messages are coming.
11

Zap Editor > Turn On

Enable Zap and set name

Turn on your automation and give it a clear name for future management. Once enabled, new Salesforce leads will automatically trigger Slack notifications.

  1. 1Click 'Turn on Zap' in the top right corner
  2. 2Name it 'Salesforce New Lead → Slack Notifications'
  3. 3Click 'Save' to confirm the name change
  4. 4Verify the Zap shows as 'On' in your dashboard
What you should see: Your Zap appears in the dashboard with 'On' status and the descriptive name you set.
Common mistake — Once turned on, every new lead will post to Slack - make sure your team knows the automation is live.

Drop this into a Zapier Code step.

Copy this template{{FirstName}} {{LastName}} from {{Company}}
▸ Show code
{{FirstName}} {{LastName}} from {{Company}}
📱 {{Phone}} | 🏢 {{Title}}
🎯 Source: {{LeadSource}}

... expand to see full code

{{FirstName}} {{LastName}} from {{Company}}
📱 {{Phone}} | 🏢 {{Title}}
🎯 Source: {{LeadSource}}
🔗 https://yourcompany.salesforce.com/{{Id}}

Scaling Beyond 500+ leads/day+ Records

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

1

Add lead source filters

Exclude bulk imports and low-priority sources like trade show badge scans. Filter for only 'Website' and 'Referral' sources to avoid notification spam during list uploads.

2

Use digest scheduling

Switch from individual notifications to hourly digest messages that summarize multiple leads. This prevents channel flooding while maintaining sales team awareness.

3

Consider webhook alternatives

At 1000+ leads daily, Zapier tasks become expensive. Direct Salesforce Process Builder to Slack webhooks cost nothing but require developer setup and ongoing maintenance.

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 Zapier for this workflow

Use Zapier for this if your sales team needs instant lead alerts but doesn't have developers to build custom integrations. The setup takes 15 minutes and works reliably for most B2B teams under 1000 leads per month. The guided interface makes it easy to modify message formats when your team's needs change. Skip Zapier only if you're processing 2000+ leads monthly - at that volume, a direct Salesforce-to-Slack webhook saves significant money on task usage.

Cost

This workflow uses 1 task per new lead. At 200 leads per month, that's 200 tasks monthly, fitting comfortably in Zapier's Starter plan at $19.99/month. Make would cost $9/month for the same volume but caps at 1000 operations. N8n is free for unlimited leads but requires hosting setup. For most sales teams, Zapier's reliability and support justify the extra $11 monthly.

Tradeoffs

Make handles conditional logic better - you can easily add rules like 'only notify for Enterprise leads' or 'route different sources to different channels' without multiple Zaps. N8n offers superior data transformation, letting you enrich leads with company data from Clearbit or similar APIs in the same workflow. But Zapier wins on maintenance - it just works without touching server configs or debugging webhook endpoints that break during Salesforce updates.

Salesforce's API sometimes delays new record visibility by 2-3 minutes, so your first lead notification might seem slow. The platform also has strict rate limits - if you import bulk leads, Zapier will spread notifications over 15-20 minutes to avoid hitting API caps. Watch out for lead assignment rules that trigger multiple record updates - each update fires the Zap again, creating duplicate Slack messages unless you add time-based filters.

Ideas for what to build next

  • Add lead scoring notificationsCreate a second Zap that posts to Slack when existing leads reach high score thresholds, helping reps prioritize follow-up activities.
  • Set up opportunity stage alertsBuild notifications for when leads convert to opportunities and move through sales stages, keeping the team informed of pipeline progression.
  • Create lead response trackingConnect Slack reactions or replies back to Salesforce as activities, showing which reps are actively working new leads from the notifications.

Related guides

Was this guide helpful?
Salesforce + Slack overviewZapier profile →