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

How to Send HubSpot Lead Score Alerts to Slack with Make

Automatically notify your Slack channel when a HubSpot contact's lead score crosses your threshold to catch hot leads instantly.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

HubSpot for Slack exists as a native integration, but it doesn't support conditional routing or custom message formatting. This guide uses an automation platform for full control. View native option →

Best for

Sales teams that need immediate alerts when leads hit qualification scores and want visual workflow control.

Not ideal for

High-volume lead generation (500+ scored contacts daily) or teams needing sub-5-minute notification speed.

Sync type

polling

Use case type

notification

Real-World Example

💡

A 12-person B2B software sales team uses this to alert #sales-hot-leads whenever a contact scores above 85 points in HubSpot. Before automation, sales reps manually checked lead score reports twice daily and often missed qualified prospects for 4-6 hours, letting competitors reach them first.

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

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.

HubSpot account with lead scoring enabled and configured
Slack workspace with permission to add integrations
Make account (free tier works for basic volume)
Admin access to both HubSpot and Slack
At least one contact in HubSpot with a lead score above your threshold

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Contact First Namefirstname
Contact Last Namelastname
Email Addressemail
Lead Scorehubspotscore
Contact IDvid
3 optional fields▸ show
Portal IDportalId
Company Namecompany
Lifecycle Stagelifecyclestage

Step-by-Step Setup

1

Scenarios > Create new scenario > Apps

Create New Make Scenario

Start a fresh scenario in Make to connect HubSpot lead score changes to Slack notifications. This sets up the foundation for monitoring score thresholds.

  1. 1Log into Make and click 'Create a new scenario'
  2. 2Click the large + icon in the center
  3. 3Search for 'HubSpot' in the app directory
  4. 4Select 'HubSpot' from the results
What you should see: You should see the HubSpot app icon in your scenario with a list of available modules.
2

HubSpot > Triggers > Watch contacts

Configure Contact Updated Trigger

Set up HubSpot to watch for contact changes, specifically lead score updates. This trigger fires whenever any contact property changes in HubSpot.

  1. 1Click 'Watch contacts' from the HubSpot module list
  2. 2Click 'Add' next to Connection to authenticate HubSpot
  3. 3Follow OAuth flow to grant Make access to your HubSpot account
  4. 4Set 'Limit' to 100 to control processing volume
What you should see: Green 'Connected' status appears and the module shows HubSpot contact fields available.
Common mistake — Don't use 'Watch deals' - lead scores are contact properties, not deal properties
Make
+
click +
search apps
HubSpot
HU
HubSpot
Configure Contact Updated Tr…
HubSpot
HU
module added
3

Scenario flow > Filter > Conditions

Add Lead Score Filter

Create a filter to only process contacts when their lead score crosses your threshold. This prevents notifications for every minor contact update.

  1. 1Click the wrench icon between HubSpot and the next module
  2. 2Select 'Set up a filter'
  3. 3Name it 'Lead Score Threshold'
  4. 4Set condition: 'hs_lead_status' Greater than 80
What you should see: Filter shows as a funnel icon with your threshold condition visible.
Common mistake — Use numeric comparison, not text - lead scores are integers in HubSpot's API
HubSpot
HU
trigger
filter
Condition
matches criteria?
yes — passes through
no — skipped
Slack
SL
notified
4

Apps > Slack > Create a Message

Add Slack Module

Connect Slack to receive the lead score notifications. Choose the message module to send formatted alerts to your sales channel.

  1. 1Click + to add a new module after the filter
  2. 2Search for 'Slack' and select it
  3. 3Choose 'Create a Message' from available actions
  4. 4Click 'Add' next to Connection for Slack authentication
What you should see: Slack module appears with connection options and message configuration fields.
5

Slack > Create Message > Message content

Configure Slack Message Content

Build the notification message with contact details and lead score. Use HubSpot data fields to create actionable alerts for your sales team.

  1. 1Select your target Slack channel from the dropdown
  2. 2In Message field, click 'Map' and add: 'Hot lead alert!'
  3. 3Add HubSpot fields: firstname, lastname, email, hs_lead_status
  4. 4Format as: '{{firstname}} {{lastname}} ({{email}}) scored {{hs_lead_status}} points'
What you should see: Message preview shows dynamic HubSpot contact data mapped into your Slack notification template.
Common mistake — Test channel selection first - production alerts going to #general annoy everyone
Message template
🔔 New Lead: {{1.properties.firstname.value}} {{1.properties.lastname.value}}
Email: {{1.properties.email.value}}
Company: {{1.properties.company.value}}
Status: {{1.properties.hs_lead_status.value}}
6

Scenario controls > Run once

Test With Sample Data

Run a test to verify the scenario works with HubSpot contact data. This validates field mapping and message formatting before going live.

  1. 1Click 'Run once' button at bottom left
  2. 2Wait for HubSpot module to fetch sample contact data
  3. 3Check that filter allows high-scoring contacts through
  4. 4Verify Slack message appears in your test channel
What you should see: Test shows green checkmarks on all modules and a properly formatted message appears in Slack.
Common mistake — If no test data appears, create a test contact in HubSpot with lead score above 80 first
Make
▶ Run once
executed
HubSpot
Slack
Slack
🔔 notification
received
7

Slack > Message content > Edit

Add Contact Link for Quick Access

Include a direct link to the HubSpot contact record so sales reps can act immediately. This saves time switching between tools during follow-up.

  1. 1Edit the Slack message content
  2. 2Add a new line after the score information
  3. 3Insert: 'View contact: https://app.hubspot.com/contacts/{{portalId}}/contact/{{vid}}'
  4. 4Save the message configuration
What you should see: Slack message now includes a clickable link that opens the specific contact record in HubSpot.
Common mistake — Use 'vid' not 'id' for the contact identifier - HubSpot URLs expect the visitor ID format
8

Module menu > Error handling > Break

Configure Error Handling

Set up error handling to catch API failures and rate limits. This prevents the scenario from breaking when HubSpot or Slack has issues.

  1. 1Right-click the Slack module
  2. 2Select 'Add error handler'
  3. 3Choose 'Break' as the error handler type
  4. 4Enable 'Store incomplete executions' in scenario settings
What you should see: Error handler route appears below Slack module with break symbol.
Common mistake — Don't use 'Ignore' error handling - you'll miss failed notifications and never know why
9

HubSpot module > Scheduling > Interval

Set Polling Schedule

Configure how often Make checks HubSpot for lead score changes. Balance between real-time alerts and API usage limits.

  1. 1Click the clock icon on the HubSpot trigger module
  2. 2Select 'Every 15 minutes' for the polling interval
  3. 3Enable 'Process all results' to catch multiple updates
  4. 4Save the scheduling configuration
What you should see: HubSpot module shows a 15-minute timer icon indicating active polling schedule.
Common mistake — Polling every 5 minutes burns through operations fast - 15 minutes is the sweet spot for lead alerts
10

Scenario controls > Activation toggle

Activate Production Scenario

Turn on the scenario to start monitoring lead scores in real-time. This begins the automated alert system for your sales team.

  1. 1Click the 'OFF' toggle switch at bottom left
  2. 2Confirm activation in the popup dialog
  3. 3Scenario status changes to 'ON' with green indicator
  4. 4Monitor the execution log for first few runs
What you should see: Scenario shows 'ON' status and begins polling HubSpot every 15 minutes for contact updates.
Common mistake — Watch execution logs for first hour - initial runs often reveal data mapping issues not caught in testing

Drop this into a Make custom function.

JavaScript — Custom Function{{if(hubspotscore > 90; "🔥 URGENT"; if(hubspotscore > 80; "⚡ High Priority"; "📊 Qualified"))}} Lead Alert
▸ Show code
{{if(hubspotscore > 90; "🔥 URGENT"; if(hubspotscore > 80; "⚡ High Priority"; "📊 Qualified"))}} Lead Alert

... expand to see full code

{{if(hubspotscore > 90; "🔥 URGENT"; if(hubspotscore > 80; "⚡ High Priority"; "📊 Qualified"))}} Lead Alert

Scaling Beyond 200+ scored contacts/month+ Records

If your volume exceeds 200+ scored contacts/month records, apply these adjustments.

1

Implement Score Change Detection

Add a Make data store to track previous lead scores per contact. Only trigger alerts when score actually increases above threshold, not just when any contact property updates. This cuts false positives by 70%.

2

Batch Process Lower-Priority Scores

Create separate scenarios for different score tiers. Process scores 80-89 every 30 minutes, but check 90+ scores every 5 minutes. Use HubSpot list membership triggers instead of polling all contacts.

3

Add Rate Limiting Buffer

Insert a sleep module between HubSpot and Slack to prevent API rate limiting during high-volume periods. Set 2-second delays when processing more than 10 contacts per execution.

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 visual workflow mapping and complex lead score logic. Make handles HubSpot's nested contact properties better than Zapier, and the visual builder makes it easy to add filters for different score thresholds. Skip Make and use Zapier if you just want basic score alerts - setup takes 3 minutes versus Make's 15-minute configuration process.

Cost

This workflow uses 2 operations per qualifying contact (1 for HubSpot trigger, 1 for Slack message). At 50 hot leads per month, that's 100 operations monthly. Make's free tier covers 1,000 operations, so you won't pay anything. The Core plan at $9/month handles 10,000 operations. Zapier charges $20/month for the same volume on their Starter plan, making Make $11/month cheaper.

Tradeoffs

Zapier wins on trigger speed - their HubSpot integration fires within 2 minutes versus Make's 15-minute polling minimum. N8n offers better customization for complex lead scoring formulas and conditional logic trees. But Make's visual interface makes troubleshooting easier when lead scores don't behave as expected, and their HubSpot integration handles custom properties more reliably than N8n's community-maintained connector.

HubSpot's lead score calculations can lag behind contact updates by several minutes, so immediate triggers sometimes fire before scores update. The portalId field gets tricky in multi-hub accounts - Make pulls from your default hub unless specified otherwise. Contact merge operations in HubSpot create duplicate notifications since Make sees the merge as a new contact update.

Ideas for what to build next

  • Add Deal Stage Progression AlertsExtend the workflow to notify when high-scoring contacts move through your sales pipeline stages, not just initial qualification.
  • Create Lead Score Trend AnalysisBuild a Google Sheets logger to track lead score changes over time and identify which marketing activities drive the highest-scoring leads.
  • Implement Multi-Channel NotificationsAdd email and SMS alerts for your highest-value prospects (95+ scores) to ensure no critical leads slip through during off-hours.

Related guides

Was this guide helpful?
HubSpot + Slack overviewMake profile →