Can I route the same form to multiple Slack channels?

Yes, but you need separate router paths for each channel destination. Clone the Slack module and connect it to the same filtered path.

Why do some form submissions not trigger the scenario?

Make only catches new submissions after the scenario is activated. Historical form data won't trigger the workflow, and draft forms don't send webhooks.

How do I handle forms with different field names?

Use Make's 'if' function in your message template to check if fields exist before displaying them. This prevents empty or broken message formatting.

Can I add rich formatting like buttons or attachments to Slack messages?

Switch from 'Simple text message' to 'Advanced' in the Slack module to access block kit formatting, buttons, and threaded replies.

What happens if Slack is down when a form is submitted?

Make will retry the Slack message 3 times over 30 minutes. Set error handling to 'Break' to get email notifications about persistent failures.

Beginner~12 min setupCRM & CommunicationVerified April 2026

Form submission alerts — HubSpot to Slack in Make

Send instant Slack notifications to specific channels when someone submits a HubSpot form, with different forms routing to different teams.

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 with multiple forms that need different routing rules and rich Slack formatting.

Not ideal for

Simple single-form setups where basic Zapier integration is sufficient.

Sync type

polling

Use case type

notification

Real-World Example

💡

A 25-person B2B SaaS company routes demo requests from their pricing page to #sales-leads, support tickets to #customer-success, and partnership inquiries to #business-dev. Before automation, form submissions sat in HubSpot for hours until someone manually checked, causing 3-4 hour response delays that hurt conversion rates.

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 account with Marketing Hub access and active forms

Slack workspace admin access to add Make bot and create channels

Make account with at least the Core plan for multiple operations

Active website forms generating submissions to test the workflow

List of forms and their intended Slack channel destinations

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Contact Email	`email`	Submitter's email address from the form, maps directly to Slack message
Form Name	`form_name`	HubSpot form title used for router filtering and channel routing
Form ID	`form_id`	HubSpot's internal form identifier for precise routing rules
Submission Timestamp	`submitted_at`	When the form was submitted, useful for time-based Slack formatting

3 optional fields▸ show

Company Name	`company`	Company field from form, often empty on contact forms
Message Content	`message`	Free text field content from textarea inputs on the form
Page URL	`page_url`	URL where form was submitted, helps with context in Slack messages

Step-by-Step Setup

Scenarios > Create new > HubSpot > Watch Form Submissions

Create new scenario and add HubSpot trigger

Start a new Make scenario and add HubSpot as your trigger module. This will listen for new form submissions across all your HubSpot forms.

1Click 'Create a new scenario' from your Make dashboard
2Click the gray circle with the + icon in the center
3Type 'HubSpot' in the search box and select it
4Choose 'Watch Form Submissions' from the trigger options

✓ What you should see: You should see a HubSpot module with 'Watch Form Submissions' as the selected trigger in your scenario canvas.

Make

click +

search apps

HubSpot

Create new scenario and add …

HubSpot

module added

HubSpot module > Connection > Add

Connect your HubSpot account

Authenticate Make with your HubSpot account to access form data. Make needs Marketing Hub permissions to read form submissions.

1Click 'Add' next to the Connection field
2Enter a connection name like 'HubSpot Main'
3Click 'Save' and you'll be redirected to HubSpot
4Log in to HubSpot and click 'Connect app' to authorize Make

✓ What you should see: You should see a green 'Connected' status and your connection name in the dropdown.

⚠

Common mistake — Make sure you're logged into the correct HubSpot portal — switching portals later breaks the connection.

Make settings

Connection

Choose a connection…Add

click Add

HubSpot

Authorize Make

popup window

✓

Connected

green checkmark

HubSpot module > Settings

Configure form filter settings

Set up which forms to monitor and how far back to check. Leave Form ID empty to watch all forms, or specify one form's ID for focused monitoring.

1Leave 'Form ID' blank to monitor all forms
2Set 'Limit' to 10 for testing purposes
3Leave 'Since' empty to start monitoring from now
4Click 'OK' to save the trigger configuration

✓ What you should see: The HubSpot module should show 'Watch Form Submissions' with a small gear icon indicating it's configured.

⚠

Common mistake — Setting a specific Form ID now means you'll need separate scenarios for each form — better to filter later with routers.

HubSpot

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Slack

notified

Scenario > Run once > HubSpot module

Test HubSpot connection

Run a test to verify Make can pull form submission data from HubSpot. This shows you the exact data structure you'll work with.

1Click 'Run once' at the bottom of the screen
2Submit a test form on your website or HubSpot landing page
3Wait 30 seconds, then click the HubSpot module
4You should see sample form data with fields like email, form name, and submission timestamp

✓ What you should see: The HubSpot module displays a white bubble with a number 1, and clicking it shows your test form submission data.

⚠

Common mistake — If no data appears, check that your form is published and not in draft mode in HubSpot.

Make

▶ Run once

executed

✓

HubSpot

✓

Slack

🔔 notification

received

HubSpot module > + > Flow control > Router

Add router for form-based routing

Insert a router module to send different forms to different Slack channels. This lets you route demo requests to sales and support forms to your support team.

1Click the small circle after the HubSpot module
2Select 'Flow control' from the category list
3Choose 'Router' from the available modules
4The router automatically connects to your HubSpot trigger

✓ What you should see: You should see a diamond-shaped router module with two empty paths extending from it.

Router > Path 1 > Filter settings

Configure first routing path

Set up conditions to route specific forms to specific channels. Use the form name or form ID to create routing rules.

1Click the small wrench icon on the first router path
2Set Label to 'Demo Requests'
3Add condition: Form Name contains 'demo' OR 'contact sales'
4Click 'OK' to save the filter

✓ What you should see: The first router path should show 'Demo Requests' as the label and display a small filter icon.

⚠

Common mistake — Use 'contains' not 'equals' for form names — HubSpot form names often have extra characters or spaces.

Router path 1 > + > Slack > Create a Message

Add Slack module to first path

Connect Slack to the first router path to send demo request notifications to your sales channel.

1Click the + at the end of the 'Demo Requests' path
2Search for 'Slack' and select it
3Choose 'Create a Message' from the action list
4The Slack module connects to your filtered path

✓ What you should see: You should see a Slack module connected to the first router path, ready for configuration.

Slack module > Connection and Message settings

Connect and configure Slack

Authenticate with Slack and set up the channel and message format for demo request notifications.

1Click 'Add' next to Connection and authorize Make in Slack
2Select your target channel from the 'Channel' dropdown
3Set Message Type to 'Simple text message'
4In Text field, write: 'New demo request from {{email}} - Company: {{company}}'

✓ What you should see: Slack module shows connected status and displays your channel selection and message template.

⚠

Common mistake — Make sure the Slack bot has permission to post in your target channel — test with #general first if unsure.

Router > Path 2 > Filter settings

Set up second routing path

Configure the second router path for different form types, like support requests or newsletter signups.

1Click the wrench icon on the second router path
2Set Label to 'Support Forms'
3Add condition: Form Name contains 'support' OR 'help'
4Click 'OK' to save this filter

✓ What you should see: Second router path shows 'Support Forms' label with a filter icon indicating the condition is set.

Router path 2 > + > Slack > Create a Message

Add Slack module to second path

Connect another Slack module to handle support form submissions with different channel routing and message formatting.

1Click the + at the end of the 'Support Forms' path
2Add Slack > Create a Message (same as before)
3Select your existing Slack connection
4Choose a different channel like #customer-support
5Set message text: 'Support request from {{email}} - Issue: {{message}}'

✓ What you should see: Second Slack module is configured with a different channel and message format for support requests.

Scenario > Run once

Test the complete workflow

Submit test forms to verify routing works correctly and messages appear in the right Slack channels with proper formatting.

1Click 'Run once' to activate the scenario
2Submit a form with 'demo' in the name on your site
3Check that the message appears in your sales channel
4Submit a support form and verify it goes to the support channel

✓ What you should see: You should see form submissions trigger the correct router paths and post formatted messages to the appropriate Slack channels.

⚠

Common mistake — If messages don't appear, check the scenario execution log for errors — often it's a channel permission issue.

Scenario > ON/OFF toggle > Scheduling settings

Activate scenario for production

Turn on the scenario to run automatically and set appropriate scheduling for your form submission volume.

1Click the 'ON/OFF' toggle in the bottom left to activate
2The scenario will check for new submissions every 15 minutes by default
3Click 'Scheduling settings' if you need faster polling
4Save your scenario with a clear name like 'HubSpot Forms to Slack Routing'

✓ What you should see: Scenario shows 'Active' status with a green indicator, and new form submissions automatically trigger Slack notifications.

⚠

Common mistake — Don't set polling below 5 minutes unless you're on a higher-tier Make plan — you'll burn through operations fast.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(length(company) > 0; "Company: " + company + "\n"; "")}}{{if(length(message) > 0; "Message: " + message; "No message provided")}}

▸ Show code

{{if(length(company) > 0; "Company: " + company + "\n"; "")}}{{if(length(message) > 0; "Message: " + message; "No message provided")}}

... expand to see full code

{{if(length(company) > 0; "Company: " + company + "\n"; "")}}{{if(length(message) > 0; "Message: " + message; "No message provided")}}

Scaling Beyond 500+ form submissions/month+ Records

If your volume exceeds 500+ form submissions/month records, apply these adjustments.

Batch notifications

Use Make's aggregator module to bundle multiple submissions into single Slack messages every 30 minutes instead of individual notifications. This cuts operation usage by 70%.

Implement deduplication

Add a data store module to track processed form submission IDs and filter out duplicates. HubSpot sometimes sends duplicate webhooks during API hiccups.

Going live

Production Checklist

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

Set error handling to 'Break' on both Slack modules to catch posting failures

Applies when: Always

Add a fallback router path with no filters to catch unmatched forms

Applies when: Always

Test message formatting with empty fields (company, message) to avoid broken templates

Applies when: Always

Verify Make Slack bot has posting permissions in all target channels

Applies when: Always

Set polling interval to 5 minutes maximum to avoid operation overages

Applies when: High volume

Add data store logging to track processed form IDs and prevent duplicates

Applies when: Enterprise

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 routing logic and have multiple form types going to different channels. Make's router system handles conditional logic better than Zapier's path filters, and you get visual branching that's easier to debug. The data transformation tools let you format rich Slack messages with attachments and threading. Skip Make if you only have 1-2 forms — Zapier's single-path setup is simpler for basic notifications.

Cost

This workflow uses 2-3 operations per form submission (trigger + router + Slack message). At 200 submissions per month, that's 600 operations monthly. Make's Core plan gives you 10,000 operations for $9/month, so you're well covered. Zapier charges $20/month for their Starter plan to handle the same volume with multi-step Zaps. N8N is free but requires hosting setup.

Tradeoffs

Zapier beats Make on polling frequency — their forms trigger fires within 1-2 minutes while Make's default is 15 minutes. N8N offers better Slack formatting options with their message builder and native threading support. But Make wins on routing complexity — you can build unlimited conditional paths without upgrading plans, while Zapier limits paths on lower tiers.

HubSpot's form API doesn't include utm parameters or page context in the webhook data, so you'll lose attribution tracking unless you capture it in hidden form fields. The API rate limit is 100 requests per 10 seconds — not an issue for normal volumes but watch out if you're processing bulk imports that trigger the form webhook. Make's HubSpot module sometimes double-processes submissions if the polling interval overlaps with high submission periods.

Ideas for what to build next

→
Add lead scoring notifications — Extend the workflow to include HubSpot contact scores in Slack messages and highlight high-value leads with different formatting.
→
Create follow-up task automation — Add HubSpot task creation after sending Slack notifications so sales reps have automatic follow-up reminders in their CRM.
→
Build submission analytics dashboard — Log all form submissions to Google Sheets or Airtable to track conversion sources and response times by channel.