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

How to Send Weekly Pipeline Summaries from Salesforce to Slack with Zapier

Automatically post formatted pipeline summaries to Slack every Monday with total values, deals by stage, and closing deals.

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 wanting automated weekly pipeline visibility without building custom reports in Salesforce.

Not ideal for

Teams needing real-time pipeline updates or complex conditional formatting based on deal characteristics.

Sync type

scheduled

Use case type

notification

Real-World Example

💡

A 25-person B2B software company uses this to keep executives updated on pipeline health every Monday morning. Before automation, the sales ops manager spent 30 minutes manually pulling Salesforce reports and copying data into Slack, often forgetting during busy weeks. Now the entire leadership team sees consistent pipeline updates without manual work.

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 admin access with API permissions enabled
Slack workspace with permission to post in target channels
Zapier account with multi-step Zap capability (paid plan)
Active opportunities in Salesforce with Amount and CloseDate fields populated

Optional

Understanding of your sales stages and typical pipeline size

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Opportunity AmountAmount
Stage NameStageName
Close DateCloseDate
Opportunity NameName
2 optional fields▸ show
Account NameAccount.Name
Owner Full NameOwner.Name

Step-by-Step Setup

1

Create Zap > Trigger > Schedule by Zapier

Create new scheduled Zap

Start with Schedule by Zapier as your trigger. This runs the automation on a recurring basis instead of waiting for data changes.

  1. 1Click 'Create Zap' from your Zapier dashboard
  2. 2Search for 'Schedule by Zapier' in the trigger app list
  3. 3Select 'Every Week' as the trigger event
  4. 4Choose 'Monday' and set time to 9:00 AM
What you should see: Your trigger should show 'Schedule by Zapier - Every Week' with Monday 9:00 AM selected.
Common mistake — Confirm your workflow timezone matches your business timezone — n8n uses the instance timezone by default. Also verify the workflow is saved and set to Active, since Schedule Triggers won't fire on inactive workflows.
2

Action > Salesforce > Find Records

Connect Salesforce account

Add Salesforce as your first action step. You'll use this to pull current pipeline data when the schedule fires.

  1. 1Click the + button to add an action step
  2. 2Search for 'Salesforce' and select it
  3. 3Choose 'Find Records' as the action event
  4. 4Click 'Sign in to Salesforce' and complete OAuth
What you should see: Green 'Connected' status should appear next to your Salesforce account name.
Common mistake — Use 'Find Records' not 'Get Record' — you need to pull multiple deals at once for the summary.
Zapier settings
Connection
Choose a connection…Add
click Add
Salesforce
Log in to authorize
Authorize Zapier
popup window
Connected
green checkmark
3

Salesforce Action > Set up action

Configure pipeline data query

Set up the Salesforce query to pull all open opportunities. This gives you the raw data to calculate totals and stage breakdowns.

  1. 1Set 'Object' dropdown to 'Opportunity'
  2. 2In 'Search Fields', select 'StageName'
  3. 3Set 'Search Value' to exclude 'Closed Won,Closed Lost'
  4. 4Set 'Max Records' to 500
What you should see: Test should return multiple opportunity records with fields like Amount, StageName, and CloseDate visible.
Common mistake — Don't filter by owner — you want the full company pipeline, not individual rep data.
4

Action > Formatter by Zapier > Numbers

Add Formatter to calculate totals

Use Zapier's Formatter tool to sum up opportunity amounts. This creates your total pipeline value for the summary message.

  1. 1Add another action step and select 'Formatter by Zapier'
  2. 2Choose 'Numbers' as the transform type
  3. 3Select 'Perform Math Operation' as the event
  4. 4Set 'Operation' to 'Sum' and map the Amount field from Salesforce
What you should see: Test output should show a single number representing your total pipeline value.
Common mistake — Map the 'Amount' field specifically — other numeric fields like 'Probability' will give wrong totals.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
5

Action > Formatter by Zapier > Text

Add second Formatter for stage breakdown

Create a formatted list of deals by stage. This requires concatenating stage names with counts for readable output.

  1. 1Add another Formatter by Zapier action
  2. 2Select 'Text' as the transform type
  3. 3Choose 'Extract Pattern' as the event
  4. 4Map StageName from Salesforce and set pattern to group by stage
What you should see: Output should show stage names like 'Prospecting: 12 deals, Negotiation: 5 deals'.
Common mistake — This step is complex — consider using a simpler list format if the grouping fails in testing.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
6

Action > Filter by Zapier

Filter for closing deals

Add a Filter step to identify deals closing within the next 7 days. This creates your 'closing this week' section.

  1. 1Add 'Filter by Zapier' as the next step
  2. 2Set condition field to 'CloseDate' from Salesforce
  3. 3Choose 'Is between' as the condition
  4. 4Set start date to 'today' and end date to '7 days from now'
What you should see: Filter test should show only opportunities with CloseDate in the next week.
Common mistake — Date filters in Zapier use YYYY-MM-DD format — test with actual dates to verify the range works.
Salesforce
SA
trigger
filter
Deal Stage
matches criteria?
yes — passes through
no — skipped
Slack
SL
notified
7

Action > Slack > Send Channel Message

Connect Slack workspace

Add Slack as your final action to post the formatted summary. Choose the channel where your team expects weekly updates.

  1. 1Add Slack as a new action step
  2. 2Select 'Send Channel Message' as the event
  3. 3Click 'Sign in to Slack' and authorize workspace access
  4. 4Select '#sales' from the channel dropdown
What you should see: Slack connection should show 'Connected' with your workspace name displayed.
Common mistake — Make sure you have permission to post in the target channel — test with a personal channel first if unsure.
8

Slack Action > Message Text

Format the pipeline message

Build your message template using data from previous steps. Include emojis and formatting to make the summary scannable.

  1. 1In the 'Message Text' field, type: '📊 Weekly Pipeline Summary'
  2. 2Add line break and insert total pipeline value from Formatter step
  3. 3Add stage breakdown from second Formatter
  4. 4Include closing deals list with mapped deal names and amounts
What you should see: Message preview should show formatted text with actual data populated from your Salesforce test.
Common mistake — Use Slack's markdown formatting (* for bold, for code blocks) — plain text looks unprofessional in channels.
Message template
🔔 New Lead: {{1.FirstName}} {{1.LastName}}
Email: {{1.Email}}
Company: {{1.Company}}
Status: {{1.LeadStatus}}
9

Test & Review > Test & Continue

Test the complete workflow

Run a full test to verify data flows correctly and the Slack message appears properly formatted. Check all calculations match expected values.

  1. 1Click 'Test & Continue' on the final Slack step
  2. 2Verify the test message appears in your Slack channel
  3. 3Check that pipeline totals match your Salesforce dashboard
  4. 4Confirm deal counts by stage are accurate
What you should see: A properly formatted pipeline summary should appear in Slack with real data from your Salesforce org.
Common mistake — Test messages go to the real channel — warn your team or use a test channel to avoid confusion.
Zapier
▶ Turn on & test
executed
Salesforce
Slack
Slack
🔔 notification
received
10

Zap Dashboard > Status Toggle

Activate the Zap

Turn on your automation to run every Monday morning. Monitor the first few runs to catch any data issues early.

  1. 1Click 'Publish' to activate the Zap
  2. 2Verify the status shows 'On' in your Zap dashboard
  3. 3Set up email notifications for Zap failures
  4. 4Add the Zap to a folder for easy organization
What you should see: Zap status should show 'On' with next scheduled run time displayed as 'Monday 9:00 AM'.
Common mistake — Check your task usage after the first few runs — multiple Formatter steps consume more tasks than expected.

Drop this into a Zapier Code step.

JavaScript — Code Step{{formatCurrency(sum(Amount), 'USD')}} — Use this in your Slack message template to format pipeline totals with proper currency symbols and commas for readability.
▸ Show code
{{formatCurrency(sum(Amount), 'USD')}} — Use this in your Slack message template to format pipeline totals with proper currency symbols and commas for readability.

... expand to see full code

{{formatCurrency(sum(Amount), 'USD')}} — Use this in your Slack message template to format pipeline totals with proper currency symbols and commas for readability.

Scaling Beyond 200+ opportunities in pipeline+ Records

If your volume exceeds 200+ opportunities in pipeline records, apply these adjustments.

1

Increase Max Records limit

Salesforce queries default to 100 records. Bump to 500 or add pagination with Iterator if your pipeline exceeds query limits.

2

Filter by probability

Exclude deals under 20% probability to focus on realistic pipeline. Reduces API calls and makes summaries more actionable for leadership reviews.

3

Split by region or team

Create separate Zaps for different sales teams posting to their own channels. Prevents information overload and improves relevance for each audience.

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 team wants a simple weekly summary without custom coding. The Schedule trigger handles recurring reports better than most platforms, and the Formatter tools let you calculate totals without writing formulas. Skip Zapier if you need complex stage groupings or conditional logic — Make handles data manipulation much better for sophisticated pipeline analysis.

Cost

This workflow burns through 6-8 tasks per run. At weekly frequency, that's 32 tasks monthly — easily fitting Zapier's Starter plan at $20/month. Make would cost $9/month for the same volume since their operations are cheaper. N8n self-hosted runs free but requires server maintenance that costs more than the $11/month savings.

Tradeoffs

Make beats Zapier on data transformation — their Set Variable modules handle stage groupings and date math more elegantly than chaining Formatter steps. N8n offers better Salesforce querying with complex filters that don't require multiple API calls. But Zapier's Schedule trigger is rock-solid reliable, while Make's scheduled scenarios occasionally skip runs during platform maintenance.

Salesforce's API returns null amounts for some opportunity records, breaking your sum calculations. The query pulls closed deals if your stage names don't match exactly — 'Closed-Won' vs 'Closed Won' trips up most teams. Slack formatting breaks when deal names contain special characters, so sanitize text fields in your message template.

Ideas for what to build next

  • Add deal aging analysisCreate a follow-up automation that flags deals sitting in the same stage for 30+ days and posts warnings to a separate Slack channel.
  • Build quarterly pipeline trendsExpand the automation to compare current week's pipeline against previous quarters, showing growth trends alongside absolute numbers.
  • Create rep-specific summariesSet up individual pipeline summaries that DM each sales rep their personal numbers every Monday, using the same data but filtered by owner.

Related guides

Was this guide helpful?
Salesforce + Slack overviewZapier profile →