Can I customize notifications based on meeting type or deal stage?

Yes, add a router module after the contact lookup to send different message formats. Route based on HubSpot contact properties, deal stage, or the meeting type field from your booking form.

What happens if a sales rep isn't in Slack or changes their email?

The Slack message will fail silently. Add a Slack user lookup module and configure error handling to send failed notifications to a backup channel like #sales-ops when user lookups fail.

How quickly do notifications arrive after someone books a meeting?

Webhooks typically deliver within 30 seconds. HubSpot webhook delays are rare but can reach 2-3 minutes during high traffic periods. Make processes webhooks immediately once received.

Can I include calendar links or meeting join URLs in the notifications?

Yes, if your HubSpot meeting booking includes video links. Map the meeting URL field from HubSpot to your Slack message template. Teams/Zoom links come through automatically when configured in HubSpot.

Beginner~12 min setupCRM & CommunicationVerified April 2026

How to Send HubSpot Meeting Notifications to Slack with Make

Automatically DM your sales reps in Slack when prospects book meetings through HubSpot, including meeting details and pre-call responses.

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 →

Make

Also on:Zapier N8n

Best for

Teams needing customized meeting notifications with conditional routing and rich data formatting

Not ideal for

Simple meeting alerts where basic email notifications would suffice

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 25-person B2B SaaS sales team uses this to notify the assigned rep immediately when prospects book product demos through their HubSpot scheduling page. Before automation, reps checked their calendars manually every hour and often showed up unprepared because they missed the pre-meeting questions prospects filled out. Now each rep gets a Slack DM within 30 seconds with the prospect's company size, current tools, and specific pain points.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/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 Professional or Enterprise account with meeting booking tools enabled

Admin access to HubSpot settings to create webhooks and private apps

Slack workspace admin permissions to authorize Make integration

Sales rep user IDs or email addresses mapped in HubSpot contact owner fields

Make account with at least the Core plan for webhook triggers

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Meeting Start Time	`startTime`	The scheduled meeting start time in UTC — convert to rep's timezone for display
Prospect Name	`contactName`	Full name of the person who booked the meeting from HubSpot contacts
Assigned Sales Rep	`hubspot_owner_id`	HubSpot user ID of the contact owner — needs conversion to Slack user ID

3 optional fields▸ show

Company Name	`company`	Prospect's company name from HubSpot company records
Meeting Type	`meetingType`	The type of meeting booked (demo, discovery, etc.) from HubSpot meeting forms
Pre-meeting Questions	`meetingNotes`	Any questions or notes the prospect provided when booking

Step-by-Step Setup

Dashboard > Create scenario > Apps

Create New Scenario in Make

Set up a new automation scenario that will monitor HubSpot for new meeting bookings. This creates the foundation for your notification workflow.

1Log into Make and click 'Create a new scenario' from the dashboard
2Click the large + icon in the center of the scenario builder
3Search for 'HubSpot' in the app selector
4Select 'HubSpot' from the results list

✓ What you should see: You should see the HubSpot app icon in your scenario with a configuration panel on the right.

HubSpot module > Triggers > Watch Events

Configure HubSpot Meeting Trigger

Set up the trigger to fire when new meetings are scheduled. This monitors your HubSpot meeting booking activity in real-time.

1Click 'Watch Events' from the HubSpot trigger options
2Select 'meeting.booked' from the event type dropdown
3Click 'Create a webhook' to generate the endpoint
4Copy the webhook URL that appears

✓ What you should see: You should see a webhook URL starting with 'hook.integromat.com' and the trigger showing 'meeting.booked' event type.

⚠

Common mistake — Don't choose 'meeting.created' — that fires for all meetings, including ones reps create manually.

Make

click +

search apps

HubSpot

Configure HubSpot Meeting Tr…

HubSpot

module added

HubSpot module > Connection > Add

Connect Your HubSpot Account

Authenticate Make to access your HubSpot data. This allows the scenario to read meeting details and contact information.

1Click 'Add' next to the Connection field
2Select 'HubSpot' connection type
3Click 'Sign in with HubSpot' and complete OAuth flow
4Grant permissions for Meetings and Contacts scopes

✓ What you should see: Your connection should show as 'Connected' with a green checkmark and your HubSpot account name.

⚠

Common mistake — Make sure to grant Contacts scope — you'll need this to fetch the assigned rep's details.

Make settings

Connection

Choose a connection…Add

click Add

HubSpot

Authorize Make

popup window

✓

Connected

green checkmark

HubSpot Settings > Integrations > Private Apps > Webhooks

Set Up Webhook in HubSpot

Configure HubSpot to send meeting data to your Make scenario. This completes the connection between your CRM and automation.

1Open HubSpot Settings > Integrations > Private Apps
2Create a new private app or edit existing one
3Navigate to the Webhooks tab
4Paste your Make webhook URL and select 'meeting.booked' event

✓ What you should see: HubSpot should show the webhook as 'Active' with your Make URL listed under Target URL.

⚠

Common mistake — Test the webhook immediately — HubSpot webhooks sometimes fail silently if the URL format is wrong.

Scenario > Add module > HubSpot > Get a Contact

Add Contact Lookup Module

Fetch additional contact details from HubSpot to get the assigned sales rep information. This ensures your notification goes to the right person.

1Click the + icon after your HubSpot trigger
2Search for and select 'HubSpot' again
3Choose 'Get a Contact' from the actions list
4Map the Contact ID from the trigger data to the Contact ID field

✓ What you should see: You should see a second HubSpot module configured to fetch contact details using the contact ID from the meeting booking.

⚠

Common mistake — Map the actual contact ID, not the contact VID — they're different fields and VID won't return current data.

Scenario > Add module > Slack > Create a Message

Add Slack Module

Connect Slack to send the notification message. This creates the final output of your automation workflow.

1Click the + icon after your contact lookup module
2Search for 'Slack' in the app selector
3Select 'Create a Message' from the Slack actions
4Choose 'Direct Message' as the channel type

✓ What you should see: You should see a Slack module with message composition fields and channel selection options.

Slack module > Connection > Add

Connect Your Slack Workspace

Authenticate Make to send messages to your Slack workspace. This gives the scenario permission to DM your sales reps.

1Click 'Add' next to the Connection field in Slack module
2Select your Slack workspace from the list
3Click 'Allow' to grant Make messaging permissions
4Verify the connection shows your workspace name

✓ What you should see: The connection field should display 'Connected' with your Slack workspace name visible.

⚠

Common mistake — Make sure the Slack user has permission to DM all your sales reps — some workspaces restrict cross-team messaging.

Slack module > Message configuration

Configure Slack Message Content

Design the notification message with meeting details and prospect information. This determines what information your reps receive.

1In the User field, map the assigned rep's Slack user ID from HubSpot
2Set the Message Text to include meeting time, prospect name, and company
3Add any pre-meeting questions from the HubSpot meeting data
4Format the message using Slack markdown for readability

✓ What you should see: Your message template should show mapped fields from HubSpot with proper Slack formatting and all relevant meeting details.

⚠

Common mistake — Test with Slack user IDs, not email addresses — email mapping fails about 20% of the time in enterprise Slack instances.

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}}

Scenario > Run once

Test the Complete Scenario

Run a full test to verify data flows correctly from HubSpot to Slack. This catches any mapping issues before going live.

1Click 'Run once' at the bottom of the scenario
2Book a test meeting in HubSpot to trigger the webhook
3Check that all modules execute successfully with green checkmarks
4Verify the Slack message arrives with correct formatting and data

✓ What you should see: All modules should show green checkmarks and you should receive a properly formatted Slack DM with meeting details.

⚠

Common mistake — Use a real meeting booking for testing — Make's sample data doesn't include all the fields you'll need for production.

Make

▶ Run once

executed

✓

HubSpot

✓

Slack

🔔 notification

received

Module menu > Add error handler

Enable Error Handling

Set up proper error handling to prevent the scenario from breaking when data is missing or API calls fail.

1Right-click each module and select 'Add error handler'
2Set error handlers to 'Break' for critical failures
3Add a 'Resume' directive for non-critical errors like missing optional fields
4Configure retry logic for rate limit errors (429 responses)

✓ What you should see: Each module should show a small error handler icon and your scenario should have fallback paths for common failures.

⚠

Common mistake — Don't set all errors to 'Ignore' — you'll miss critical issues like authentication failures or malformed webhook data.

Scenario > Activation toggle

Activate the Scenario

Turn on your automation to start monitoring HubSpot meeting bookings. This makes your scenario live and ready for production use.

1Click the 'OFF' toggle in the bottom left to turn it 'ON'
2Set the scenario to run every 15 minutes for webhook processing
3Verify the scenario status shows 'Running' with a green indicator
4Monitor the execution log for the first few runs

✓ What you should see: The scenario toggle should show 'ON' in green and the status should indicate active monitoring of your HubSpot webhook.

⚠

Common mistake — Start with 15-minute intervals — shorter intervals burn through operations faster and won't meaningfully improve notification speed for webhooks.

Drop this into a Make custom function.

JavaScript — Custom Function{{formatDate(parseDate(startTime; "YYYY-MM-DDTHH:mm:ss"); "MMM DD at h:mm A"; "America/New_York")}}

▸ Show code

{{formatDate(parseDate(startTime; "YYYY-MM-DDTHH:mm:ss"); "MMM DD at h:mm A"; "America/New_York")}}

... expand to see full code

{{formatDate(parseDate(startTime; "YYYY-MM-DDTHH:mm:ss"); "MMM DD at h:mm A"; "America/New_York")}}

Scaling Beyond 100+ meetings/day+ Records

If your volume exceeds 100+ meetings/day records, apply these adjustments.

Batch notifications to channels

Switch from individual DMs to channel notifications with @mentions when volume exceeds 200 meetings daily. This reduces Slack API calls and prevents rate limiting while maintaining visibility.

Add webhook queuing

Use Make's data store to queue incoming webhooks during peak booking times. Process queued notifications in batches every 2-3 minutes to smooth out API load and prevent timeouts.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test webhook delivery with actual meeting bookings, not sample data

Applies when: Always

Verify Slack user ID mapping for all active sales reps

Applies when: Always

Set up error handling to retry failed Slack deliveries after 5-minute delay

Applies when: Always

Configure data store to prevent duplicate notifications for the same meeting

Applies when: High volume

Add timezone conversion for meeting times based on rep location

Applies when: Always

Test scenario behavior when HubSpot contact owner field is empty

Applies when: Always

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 complex meeting data transformations or route notifications based on deal stage, contact properties, or rep availability. Make's visual builder handles conditional routing better than Zapier — you can send different message formats for demo requests vs discovery calls. Skip Make if you just want basic meeting alerts with no customization — Zapier's HubSpot trigger is simpler for straightforward notifications.

Cost

This workflow uses 3 operations per meeting booking: webhook receive, contact lookup, and Slack message. At 200 bookings per month, that's 600 operations monthly. The Core plan at $9/month includes 10,000 operations, so you're well covered. Zapier would cost $20/month for the same volume since their HubSpot webhook trigger requires the Professional plan. Make saves you $132 yearly here.

Tradeoffs

Zapier wins on setup speed — their HubSpot integration auto-configures webhooks while Make requires manual webhook setup in HubSpot settings. N8n offers better Slack formatting options with native markdown support and thread management. But Make's error handling is superior for production use — you can retry failed Slack deliveries and route webhook errors to backup notifications. Most teams hit Slack delivery issues eventually, and Make's error recovery keeps notifications flowing.

You'll hit three gotchas after a few weeks. HubSpot webhook signatures expire if your scenario is off for more than 30 days — you'll need to regenerate the webhook URL. Slack user lookups fail when reps leave or change email addresses, breaking DM delivery silently. Meeting timezone data comes through in UTC but most reps expect local time — add Make's timezone conversion functions to display times correctly in notifications.

Ideas for what to build next

→
Add meeting reminder notifications — Create a follow-up scenario that sends Slack reminders 30 minutes before each meeting starts, including prep notes and prospect context.
→
Track notification delivery metrics — Build a Google Sheet logger that records when notifications are sent, delivered, and opened to measure rep engagement with meeting alerts.
→
Create no-show follow-up automation — Set up a workflow that detects when prospects don't join scheduled meetings and automatically sends rebooking links via email and updates deal stage in HubSpot.