Can I send different forms to different Slack channels?

Yes, create separate Zaps for each form-to-channel combination, or use Filter steps with Form ID conditions. Multiple Zaps is cleaner but uses more tasks.

How quickly do notifications arrive in Slack?

Typically 2-5 minutes after form submission. HubSpot processes submissions first, then Zapier polls every 1-15 minutes depending on your plan tier.

What happens if someone submits the same form multiple times?

Each submission creates a separate Slack notification. HubSpot treats repeated submissions as new events even from the same email address.

Can I include custom form fields in Slack messages?

Standard HubSpot form fields work automatically. Custom properties require HubSpot Professional+ and may need API configuration that Zapier doesn't expose.

Will this work with embedded forms on external sites?

Yes, as long as the forms are actual HubSpot forms. Third-party forms that only sync to HubSpot won't trigger this automation.

Beginner~8 min setupCRM & CommunicationVerified April 2026

How to Send HubSpot Form Submissions to Slack with Zapier

Automatically notify different Slack channels when prospects fill out HubSpot forms — demo requests, contact forms, newsletter signups.

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 →

Zapier

Also on:Make N8n

Best for

Non-technical teams who need instant Slack notifications for HubSpot form submissions without custom coding

Not ideal for

High-volume sites processing 500+ monthly submissions or teams needing complex form routing logic

Sync type

polling

Use case type

notification

Real-World Example

💡

A 12-person B2B SaaS startup uses this to notify #sales-team immediately when prospects fill out their demo request form on the pricing page. Before automation, sales reps checked HubSpot manually every hour and often missed hot leads for 3-4 hours. Now demo requests get claimed within 15 minutes.

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

Before You Start

Make sure you have everything ready.

Admin access to HubSpot with active forms collecting submissions

Slack workspace admin permissions to install Zapier app

At least one form submission in HubSpot within the last 14 days for testing

Active Zapier account (free tier handles 100 tasks/month)

Optional

Form IDs from HubSpot if you want to route different forms to different channels

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
First Name	`firstname`	Contact's first name from form submission, maps to Slack message greeting
Last Name	`lastname`	Contact's last name, combined with first name for full identification in notifications
Email Address	`email`	Primary contact email, used for follow-up and lead qualification
Form Name	`form_name`	Which specific form was submitted, used for routing to correct Slack channels
Submission Date	`submission_date`	Timestamp of form submission, helps track response time SLAs

2 optional fields▸ show

Company Name	`company`	Organization name from form, helps prioritize enterprise vs SMB leads
Phone Number	`phone`	Contact phone if collected, useful for immediate outreach

Step-by-Step Setup

Dashboard > Create Zap

Create New Zap

Start a new Zap to connect HubSpot form submissions to Slack notifications. This sets up the basic trigger-action workflow.

1Click 'Create Zap' button in your Zapier dashboard
2Name your Zap 'HubSpot Forms to Slack' in the title field
3Click 'Trigger' to set up the HubSpot connection

✓ What you should see: You should see the Zap editor with an empty trigger step waiting for app selection.

Trigger > App Selection > HubSpot

Connect HubSpot Account

Link your HubSpot account to Zapier so it can monitor form submissions. You'll need admin access to authorize the connection.

1Search for 'HubSpot' in the app selector
2Select 'HubSpot' from the results
3Click 'Sign in to HubSpot' and authorize Zapier access
4Choose your HubSpot account from the dropdown if you have multiple

✓ What you should see: Green 'Connected' status appears next to HubSpot with your account name displayed.

⚠

Common mistake — Don't use a sandbox HubSpot account — form submissions there won't match your production data

Zapier settings

Connection

Choose a connection…Add

click Add

HubSpot

Authorize Zapier

popup window

✓

Connected

green checkmark

Trigger > HubSpot > Event Selection

Select Form Submission Trigger

Choose the specific HubSpot trigger that fires when someone submits any form on your site. This monitors all forms unless you add filters later.

1Select 'New Form Submission' from the trigger event dropdown
2Click 'Continue' to proceed to trigger configuration
3Leave 'Form' field set to 'Any Form' to catch all submissions

✓ What you should see: Trigger shows 'New Form Submission' with 'Any Form' selected in the configuration panel.

⚠

Common mistake — Don't select 'Updated Contact' — that fires for every contact change, not just form fills

Zapier

click +

search apps

HubSpot

Select Form Submission Trigger

HubSpot

module added

Trigger > Test

Test HubSpot Trigger

Pull in a recent form submission to test the connection and see what data HubSpot sends. You need at least one form fill in the last 2 weeks.

1Click 'Test trigger' button
2Wait 10-15 seconds for Zapier to fetch recent submissions
3Select a sample submission from the list
4Click 'Continue with selected record'

✓ What you should see: Sample data appears showing form fields like email, name, company, and form ID from a real submission.

⚠

Common mistake — If no test data appears, submit a test form on your website first — Zapier only sees submissions from the last 14 days

Zapier

▶ Turn on & test

executed

✓

HubSpot

✓

Slack

🔔 notification

received

Between Steps > + > Filter

Add Filter for Form Routing

Set up conditional logic to send different forms to different Slack channels. This step is optional but recommended for organized notifications.

1Click the '+' icon between trigger and action steps
2Select 'Filter' from the options
3Set condition: 'Form ID' 'Exactly matches' and paste your demo form ID
4Click 'Continue' to save the filter

✓ What you should see: Filter step shows your condition with the specific form ID you want to route to this channel.

⚠

Common mistake — Get form IDs from HubSpot's Forms dashboard — don't guess or use form names as they change

HubSpot

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Slack

notified

Action > App Selection > Slack

Add Slack Action

Connect your Slack workspace and choose the action that posts messages to channels. You'll need admin permissions to install the Zapier app.

1Click 'Action' in the second step
2Search for and select 'Slack'
3Choose 'Send Channel Message' as the action event
4Click 'Sign in to Slack' and authorize workspace access

✓ What you should see: Slack shows as connected with your workspace name and 'Send Channel Message' selected.

Action > Slack Configuration

Configure Slack Message

Set up the channel destination and message format. Use dynamic fields from HubSpot to populate contact details in your notifications.

1Select target channel from the 'Channel' dropdown (e.g., #sales-alerts)
2In 'Message Text' field, type: 'New demo request from {{First Name}} {{Last Name}}'
3Add contact details: 'Email: {{Email}} | Company: {{Company}}'
4Set 'Bot Name' to 'HubSpot Forms' for easy identification

✓ What you should see: Message preview shows your template with sample data from the HubSpot test record.

⚠

Common mistake — Double-check channel permissions — private channels won't appear in the dropdown unless you're a member

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

Action > Test

Test Complete Workflow

Run the full automation end-to-end to verify HubSpot data flows correctly to your Slack channel. This creates a real message in Slack.

1Click 'Test action' button at the bottom
2Wait 5-10 seconds for the test to complete
3Check your Slack channel for the test message
4Verify all dynamic fields populated correctly

✓ What you should see: Success message appears in Zapier and a formatted notification posts to your designated Slack channel.

⚠

Common mistake — Test messages are real — warn your team or use a test channel to avoid confusion

Zap Editor > Publish

Publish and Monitor

Turn on the Zap to start processing live form submissions. Monitor the task usage and error logs for the first few days.

1Click 'Publish' button in the top right
2Toggle the Zap to 'On' status
3Click 'Task History' to monitor executions
4Set up error notifications in Zap settings if needed

✓ What you should see: Zap shows 'On' status with a green indicator and starts processing new form submissions automatically.

⚠

Common mistake — Check task history after 24 hours — form submission spikes can burn through your monthly task limit quickly

Drop this into a Zapier Code step.

Copy this template{{First Name}} {{Last Name}} ({{Email}}) submitted {{Form Name}}

▸ Show code

{{First Name}} {{Last Name}} ({{Email}}) submitted {{Form Name}}
Company: {{Company | 'Not provided'}}
Submitted: {{Submission Date | date: 'MMM d, h:mm a'}}

... expand to see full code

{{First Name}} {{Last Name}} ({{Email}}) submitted {{Form Name}}
Company: {{Company | 'Not provided'}}
Submitted: {{Submission Date | date: 'MMM d, h:mm a'}}

View in HubSpot: https://app.hubspot.com/contacts/{{Portal ID}}/contact/{{Contact ID}}

Scaling Beyond 500+ submissions/month+ Records

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

Switch to Make or N8n

At 500+ tasks monthly, you'll hit Zapier's $49 Professional plan. Make costs $16 for the same volume and includes advanced routing features for different form types.

Use Digest to batch notifications

Enable Zapier's Digest feature to combine multiple form submissions into one Slack message per hour. This reduces noise and cuts task usage by 80-90%.

Going live

Production Checklist

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

Test with a real form submission, not just Zapier's sample data

Applies when: Always

Add fallback values for optional fields like {{Company | 'Not provided'}}

Applies when: Always

Set up error notifications to email if the Zap breaks

Applies when: Always

Verify Slack bot permissions include posting to target channels

Applies when: Always

Add date filter to prevent processing old submissions when first enabled

Applies when: High volume

Monitor task usage for first week to avoid overage charges

Applies when: High volume

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 doesn't code and you need notifications running in under 10 minutes. The trigger fires within 2-3 minutes of form submission, and setup requires zero technical knowledge. Pick Make instead if you're processing 1000+ form fills per month — their free tier handles higher volumes without the per-task cost.

Cost

This workflow uses 1 task per form submission. At 200 submissions monthly, that's 200 tasks total, fitting Zapier's $19.99 Starter plan (750 tasks). Make would cost $9 for the same volume, and N8n runs free if you self-host. Zapier costs roughly double but includes hosting and maintenance.

Tradeoffs

Make handles form routing better with visual branching paths instead of separate Zaps for each channel. N8n offers better HubSpot API access, letting you pull custom form properties that Zapier's integration misses. But Zapier's pre-built HubSpot trigger works immediately without API configuration or webhook setup that the others require.

HubSpot's API sometimes delays new submissions by 5-10 minutes during heavy traffic periods, so urgent demo requests might arrive late. Form submissions with empty required fields can break your Slack message formatting — always add fallback values like {{Company | 'Not provided'}}. If you have multiple forms with identical names, Zapier's form selector gets confusing fast since it doesn't show form IDs in the dropdown.

Ideas for what to build next

→
Add lead scoring notifications — Create a second Zap that notifies different channels based on HubSpot lead scores or contact properties to prioritize hot leads.
→
Set up form abandonment alerts — Monitor HubSpot page views on form pages without submissions to catch prospects who started but didn't complete forms.
→
Create follow-up task automation — Automatically create HubSpot tasks assigned to sales reps when high-value forms get submitted, ensuring nothing falls through cracks.