Intermediate~15 min setupCRM & CommunicationVerified April 2026
Salesforce logo
Slack logo

How to Send New Lead Notifications with Pipedream

Auto-post to #sales-leads when a new lead is created in Salesforce with source, company, title, and phone for instant rep action.

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 who need instant Slack alerts with rich lead context when prospects hit Salesforce.

Not ideal for

Teams who want digest summaries or need two-way sync between Salesforce and Slack.

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 25-person B2B SaaS company uses this to alert their #sales-leads channel within 30 seconds of a new Salesforce lead. Before automation, reps checked Salesforce every hour and missed hot inbound leads for up to 3 hours. Now the first rep to react gets first dibs on the lead.

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 Pipedream

Copy the pre-built Pipedream blueprint and paste it straight into Pipedream. 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 user account with API access enabled and permission to view/create leads
Slack workspace where you can install apps or admin pre-approval for Pipedream integration
Access to the Slack channel where you want lead notifications posted
Pipedream account with webhook quota available on your plan

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Lead NameName
CompanyCompany
6 optional fields▸ show
TitleTitle
PhonePhone
EmailEmail
Lead SourceLeadSource
IndustryIndustry
Lead StatusStatus

Step-by-Step Setup

1

Pipedream Dashboard > New Workflow

Create New Workflow

Go to pipedream.com and click 'New Workflow' in the top right. You'll see the workflow builder with an empty canvas. This is where you'll add your Salesforce trigger and Slack action steps.

  1. 1Click 'New Workflow' button
  2. 2Name your workflow 'Salesforce Lead to Slack Notifications'
  3. 3Click 'Create Workflow'
What you should see: You should see an empty workflow canvas with 'Add a trigger' as the first step.
2

Workflow > Add a trigger > Salesforce

Add Salesforce Trigger

Click 'Add a trigger' and search for Salesforce. Select the 'New Record (Instant)' trigger which uses webhooks for real-time notifications. This trigger fires immediately when a new lead is created in your Salesforce org.

  1. 1Click 'Add a trigger'
  2. 2Search and select 'Salesforce'
  3. 3Choose 'New Record (Instant)' trigger
  4. 4Click 'Continue'
What you should see: You should see the Salesforce trigger configuration screen with authentication options.
Common mistake — Don't pick the polling trigger - it checks every 15 minutes instead of instant notifications.
Pipedream
+
click +
search apps
Salesforce
SA
Salesforce
Add Salesforce Trigger
Salesforce
SA
module added
3

Salesforce Trigger > Connect New Account

Connect Salesforce Account

Click 'Connect New Account' to authenticate with Salesforce. You'll be redirected to Salesforce login where you'll need to grant Pipedream access to your org. Make sure you're logging in as a user with API access and permission to view leads.

  1. 1Click 'Connect New Account'
  2. 2Log into your Salesforce org
  3. 3Click 'Allow' to grant Pipedream permissions
  4. 4Return to Pipedream workflow
What you should see: You should see your Salesforce org name appear in the account dropdown with a green checkmark.
Common mistake — If you see permission errors, your Salesforce admin needs to enable API access for your user profile.
Pipedream settings
Connection
Choose a connection…Add
click Add
Salesforce
Log in to authorize
Authorize Pipedream
popup window
Connected
green checkmark
4

Salesforce Trigger > Configuration

Configure Lead Object

Set the 'Object Type' to 'Lead' since you want to trigger on new leads specifically. Leave 'Created or Updated' set to 'Created' so it only fires for brand new leads, not updates to existing ones.

  1. 1Set 'Object Type' to 'Lead'
  2. 2Set 'Created or Updated' to 'Created'
  3. 3Click 'Save and Continue'
What you should see: The trigger shows 'Listening for new Lead records' and displays sample lead data if available.
5

Salesforce Trigger > Test

Test Salesforce Trigger

Create a test lead in Salesforce to verify the webhook works. Go to your Salesforce org, create a new lead with fake data, then return to Pipedream. The trigger should capture the new lead data within 30 seconds.

  1. 1Go to Salesforce and create a test lead
  2. 2Return to Pipedream workflow
  3. 3Click 'Test' on the trigger step
  4. 4Wait for the test data to appear
What you should see: You should see the test lead data populate with fields like Company, Name, Email, Phone, and LeadSource.
Common mistake — If no data appears after 2 minutes, check that your Salesforce user can create leads and the webhook URL is reachable.
Pipedream
▶ Deploy & test
executed
Salesforce
Slack
Slack
🔔 notification
received
6

Workflow > Add Step > Slack

Add Slack Action Step

Click the + button below your Salesforce trigger to add a new step. Search for Slack and select 'Send Message to Channel' action. This will post formatted lead notifications to your chosen Slack channel.

  1. 1Click the + button to add a step
  2. 2Search and select 'Slack'
  3. 3Choose 'Send Message to Channel'
  4. 4Click 'Continue'
What you should see: You should see the Slack step configuration with fields for channel, message, and authentication.
7

Slack Step > Connect New Account

Connect Slack Workspace

Click 'Connect New Account' to authenticate with your Slack workspace. You'll be redirected to Slack to authorize Pipedream. The Pipedream app needs permission to post messages to channels in your workspace.

  1. 1Click 'Connect New Account'
  2. 2Select your Slack workspace
  3. 3Click 'Allow' to grant permissions
  4. 4Return to Pipedream
What you should see: Your Slack workspace name should appear in the account dropdown with a connected status.
Common mistake — You need admin permissions in Slack to install apps, or ask your Slack admin to pre-approve Pipedream.
8

Slack Step > Configuration

Configure Slack Message

Set the channel to '#sales-leads' or your preferred channel name. In the message field, create a formatted notification using the Salesforce lead data. Reference fields from the trigger step using the data picker on the right side.

  1. 1Set 'Channel' to '#sales-leads'
  2. 2Click in the 'Text' field
  3. 3Use the data picker to select lead fields
  4. 4Format your message with lead details
What you should see: Your message should show dynamic field references like {{steps.trigger.event.Company}} and {{steps.trigger.event.Name}}.
Common mistake — Channel names must start with # for public channels or @ for direct messages - don't forget the prefix.
9

Workflow > Test

Test Complete Workflow

Click 'Test' at the top of the workflow to run the entire sequence. This will use your test Salesforce lead data and send an actual message to your Slack channel. Check your Slack channel to verify the message format and content.

  1. 1Click 'Test' at the workflow level
  2. 2Watch each step execute
  3. 3Check your Slack channel for the message
  4. 4Verify all lead data appears correctly
What you should see: You should see a success message and a formatted lead notification in your Slack channel with company, name, title, and phone.
Common mistake — The test sends a real Slack message - warn your team or use a test channel first.
10

Workflow > Deploy

Deploy Workflow

Click 'Deploy' in the top right to activate your workflow. This enables the Salesforce webhook and makes your automation live. From now on, every new lead in Salesforce will trigger a Slack notification within 30 seconds.

  1. 1Click 'Deploy' button
  2. 2Confirm deployment in the popup
  3. 3Wait for 'Active' status to appear
What you should see: The workflow status shows 'Active' with a green indicator, and you'll see webhook URLs registered in Salesforce.

Add this Node.js code step between Salesforce and Slack to enrich notifications with urgency scoring based on title and company size. Paste this in a new Code step after your Salesforce trigger.

JavaScript — Code Stepexport default defineComponent({
▸ Show code
export default defineComponent({
  async run({ steps, $ }) {
    const lead = steps.trigger.event;

... expand to see full code

export default defineComponent({
  async run({ steps, $ }) {
    const lead = steps.trigger.event;
    
    // Score urgency based on title keywords
    const highValueTitles = ['ceo', 'cto', 'vp', 'director', 'head of', 'chief'];
    const titleScore = highValueTitles.some(title => 
      lead.Title?.toLowerCase().includes(title)) ? 2 : 1;
    
    // Company size indicator (rough estimate from domain)
    let companySizeScore = 1;
    if (lead.Company?.includes('Inc') || lead.Company?.includes('Corp')) {
      companySizeScore = 2;
    }
    
    const urgencyScore = titleScore + companySizeScore;
    
    let urgencyEmoji = '📝';
    let urgencyText = 'Standard';
    
    if (urgencyScore >= 4) {
      urgencyEmoji = '🚨';
      urgencyText = 'HIGH PRIORITY';
    } else if (urgencyScore >= 3) {
      urgencyEmoji = '⚡';
      urgencyText = 'Priority';
    }
    
    return {
      ...lead,
      urgency_emoji: urgencyEmoji,
      urgency_text: urgencyText,
      urgency_score: urgencyScore
    };
  }
});

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

Use Pipedream for this if you need instant lead notifications with custom formatting and don't mind writing a bit of code. Pipedream's webhook processing is genuinely instant - leads appear in Slack within 30 seconds of hitting Salesforce. The Node.js code steps let you build smart lead scoring and conditional formatting that Zapier can't match. Skip Pipedream if your team wants zero-code setup and basic notifications work fine - Zapier handles this in 3 clicks.

Cost

This costs about 1 credit per lead notification. At 200 new leads per month, you'll use 200 credits monthly. Pipedream's free tier includes 10,000 credits, so this workflow is free unless you're processing 10,000+ leads monthly. Zapier charges $20/month for the same volume on their Starter plan, making Pipedream significantly cheaper for most sales teams.

Tradeoffs

Make has better visual conditional logic if you need complex lead routing rules without code. Zapier wins on pure simplicity - their Salesforce to Slack integration takes 5 minutes with zero configuration. N8N gives you more control over the message formatting with their visual data transformation, plus it's self-hosted. Power Automate integrates better if you're already using Dynamics 365. But Pipedream's instant webhook processing beats everyone on speed, and the code flexibility handles edge cases the others miss.

You'll hit Salesforce API limits if you're creating 1000+ leads daily - the webhook can overwhelm your org's API quota. Lead data sometimes arrives incomplete if Salesforce validation rules are still running when the webhook fires. Slack rate limits kick in at 1 message per second, so high-volume periods might delay notifications by a few minutes. The webhook URL changes every time you redeploy the workflow, breaking the Salesforce connection until you test again.

Ideas for what to build next

  • Add Lead AssignmentRoute leads to specific reps based on territory or lead source using conditional logic in Pipedream.
  • Create Digest ModeBuild a scheduled workflow that sends hourly lead summaries instead of individual notifications for high-volume periods.
  • Enable Two-Way UpdatesAdd a reverse workflow so reps can update lead status from Slack using slash commands or reaction emojis.

Related guides

Was this guide helpful?
Salesforce + Slack overviewPipedream profile →