How to Set Up HubSpot Webhook Notifications with Webhookify

Published Feb 21 202610 min read
HubSpot webhook setup with Webhookify

HubSpot is one of the most widely used CRM and marketing automation platforms, trusted by over 200,000 businesses to manage contacts, deals, marketing campaigns, and customer support. Staying on top of CRM activity is critical for sales teams that need to respond quickly to new leads, marketing teams tracking campaign conversions, and support teams managing customer tickets. With Webhookify, you can transform HubSpot CRM events into instant notifications delivered to Telegram, Discord, Slack, Email, or your mobile device. This means your team can react to new deals, contact changes, and form submissions in real time instead of discovering them hours later in the CRM dashboard.

This guide covers how to set up HubSpot webhooks using HubSpot Workflows and connect them to Webhookify for real-time notifications. The process takes about 15 minutes and works with HubSpot's free CRM as well as paid tiers.

Why Monitor HubSpot Webhooks with Webhookify?

  • Instant Lead Notifications: When a new contact is created in HubSpot -- whether from a form submission, an import, or an API integration -- you receive an immediate notification. Sales teams can respond to new leads within minutes instead of waiting for the next time they check the CRM.

  • Deal Pipeline Visibility: Track every stage change in your sales pipeline. When a deal moves from "Qualified" to "Proposal Sent" or from "Negotiation" to "Closed Won," your team gets an instant alert. This is especially valuable for sales managers who need to stay informed without micromanaging.

  • Form Submission Alerts: Know the moment a prospect fills out a demo request, contact form, or content download form on your website. Webhookify delivers an AI-summarized notification with the prospect's name, email, company, and form responses.

  • Multi-Team Coordination: Route different HubSpot events to different channels. Send new deal alerts to the sales Slack channel, form submissions to the marketing Discord, and support ticket updates to the customer success Telegram group -- all from the same Webhookify setup.

  • AI-Powered CRM Summaries: Instead of receiving raw HubSpot property data, Webhookify's AI translates CRM events into plain-English notifications. "New contact: Sarah Chen, VP of Engineering at TechCorp, submitted the Enterprise Demo Request form" is far more actionable than a JSON payload.

Prerequisites

  1. A HubSpot account (free CRM or any paid tier)
  2. Access to HubSpot Workflows (available on Professional and Enterprise plans, or via the free Workflows tool for simple automations)
  3. A Webhookify account (sign up free at webhookify.app)
  4. At least one notification channel configured in Webhookify (Telegram, Discord, Slack, Email, or mobile push)

Step-by-Step Setup Guide

1

Create a Webhookify Endpoint

Log into your Webhookify dashboard at webhookify.app. Click "Create Endpoint" to generate a unique webhook URL:

https://hook.webhookify.app/wh/vwx234yza567

Copy this URL. Name the endpoint descriptively, such as "HubSpot CRM Events" or "HubSpot - New Leads." If you want to track different types of CRM events separately, you can create multiple endpoints -- for example, one for deal events and another for contact events.

2

Configure Your Notification Channel

Navigate to the notification settings in your Webhookify dashboard.

For Telegram: Connect the Webhookify bot and select your chat or group. A "Sales Alerts" or "CRM Updates" group works well for HubSpot notifications.

For Discord: Authorize the bot and choose a channel like #crm-alerts or #new-leads.

For Slack: Complete the OAuth flow and select your workspace and channel. Many sales teams use channels like #new-leads, #deal-updates, or #hubspot.

For Email: Add email addresses for the team members who need real-time CRM updates. This is especially useful for sales reps who want to be notified about their specific leads.

For Mobile Push: Install the Webhookify app on your phone and enable push notifications. This ensures you never miss a hot lead, even when you are away from your desk.

3

Create a HubSpot Workflow with Webhook Action

HubSpot uses Workflows to trigger webhook calls when CRM events occur. Here is how to set one up:

  1. In your HubSpot portal, navigate to Automation > Workflows.

  2. Click "Create workflow".

  3. Choose the workflow type based on what you want to monitor:

    • Contact-based for new contacts, contact property changes, and form submissions
    • Deal-based for deal creation and pipeline stage changes
    • Company-based for company creation and property updates
    • Ticket-based for support ticket events
  4. Set your enrollment trigger. For example:

    • "Contact is created" to notify on new leads
    • "Deal stage is any of [Closed Won]" to notify on closed deals
    • "Form submission: Contact has filled out [Demo Request] on any page"
  5. Click the "+" button to add an action, then select "Send a webhook" (under the "External communication" category in Operations Hub, or use a custom code action for free plans).

  6. Configure the webhook action:

    • Method: POST
    • Webhook URL: Paste your Webhookify endpoint URL
    • Request body: Include the relevant properties you want in the notification

For the request body, include properties that matter for your notification. For a contact-based workflow, you might include:

{
  "event": "contact.creation",
  "email": "{{contact.email}}",
  "firstname": "{{contact.firstname}}",
  "lastname": "{{contact.lastname}}",
  "company": "{{contact.company}}",
  "jobtitle": "{{contact.jobtitle}}",
  "source": "{{contact.hs_analytics_source}}"
}
  1. Click "Save" and then "Turn on" the workflow.
4

Set Up Additional Workflows for Different Events

Create separate workflows for each type of CRM event you want to monitor. Here are the most common setups:

New Deal Created:

  • Trigger: "Deal is created"
  • Webhook body includes: deal name, amount, pipeline, stage, associated contact
{
  "event": "deal.creation",
  "dealname": "{{deal.dealname}}",
  "amount": "{{deal.amount}}",
  "pipeline": "{{deal.pipeline}}",
  "dealstage": "{{deal.dealstage}}",
  "contact_email": "{{deal.associations.contact.email}}"
}

Deal Stage Changed:

  • Trigger: "Deal stage is any of [Closed Won, Closed Lost]"
  • Webhook body includes: deal name, new stage, amount, close date

Form Submission:

  • Trigger: "Contact has filled out [Your Form] on any page"
  • Webhook body includes: contact details and form responses

Contact Property Changed:

  • Trigger: "Contact lifecycle stage is any of [Marketing Qualified Lead]"
  • Webhook body includes: contact info and the property that changed

Each workflow points to the same Webhookify endpoint URL (or different endpoints if you want separate routing).

5

Test Your HubSpot Webhook Setup

Test each workflow by creating a test CRM record that matches the enrollment criteria:

  1. For contact workflows: Create a new contact in HubSpot (or submit the form on your website) to trigger the workflow.
  2. For deal workflows: Create a new deal or move an existing deal to the trigger stage.
  3. For company workflows: Create a new company or update the relevant property.

After triggering the workflow, check:

  1. HubSpot Workflow History: Go to your workflow and click "History" to see if the action was executed successfully.
  2. Webhookify Dashboard: Check your endpoint's event log for the incoming webhook.
  3. Notification Channel: Verify you received the AI-summarized notification on Telegram, Discord, Slack, or Email.

If the workflow executed but no event appears in Webhookify, check the workflow history for error details. Common issues include incorrect URL formatting or the workflow being in draft mode.

HubSpot Webhook Events You Can Monitor

| Category | Event Trigger | Description | |----------|--------------|-------------| | Contacts | contact.creation | New contact created in CRM | | Contacts | contact.propertyChange | Contact property updated | | Contacts | contact.lifecycleChange | Contact lifecycle stage changed | | Contacts | contact.formSubmission | Contact submitted a form | | Deals | deal.creation | New deal created in pipeline | | Deals | deal.propertyChange | Deal property updated | | Deals | deal.stageChange | Deal moved to new pipeline stage | | Companies | company.creation | New company created | | Companies | company.propertyChange | Company property updated | | Tickets | ticket.creation | New support ticket created | | Tickets | ticket.statusChange | Ticket status updated | | Tickets | ticket.propertyChange | Ticket property changed | | Marketing | email.open | Marketing email opened | | Marketing | email.click | Link in marketing email clicked | | Marketing | list.membership | Contact added to or removed from list | | Conversations | conversation.creation | New conversation started | | Conversations | conversation.message | New message in conversation |

Real-World Use Cases

  • Speed-to-Lead Optimization: A B2B SaaS company routes form submission webhooks to a Slack channel that sales reps monitor. When a prospect fills out the "Request Demo" form, the team sees the notification immediately and the first available rep calls within five minutes. Their response time dropped from two hours to under five minutes, increasing conversion rates by 30%.

  • Deal Closing Celebrations: A sales team sends deal.stageChange events for "Closed Won" deals to a shared Telegram group. When a deal closes, the entire team sees the customer name, deal value, and the rep who closed it. The cash sound notification adds a celebratory feel that boosts team morale.

  • Customer Success Handoff: When a deal moves to "Closed Won," a workflow fires a webhook to Webhookify that notifies the customer success team on Discord. The notification includes the customer name, deal value, and product purchased, ensuring a seamless handoff from sales to onboarding.

  • Marketing Lead Scoring: A marketing team monitors contact.lifecycleChange events. When a contact transitions from "Lead" to "Marketing Qualified Lead," the marketing manager receives a push notification with the contact details, confirming that their lead scoring model is working and that qualified leads are being passed to sales.

Example Notification

Here is what a typical Webhookify notification looks like when a new HubSpot deal is created:

New Webhook Event Received

Source: HubSpot
Event: deal.creation
Endpoint: HubSpot CRM Events

AI Summary:
New deal created in the Sales Pipeline!
Deal: "TechCorp Enterprise License" worth $24,000.
Stage: Qualified. Associated contact: Sarah Chen
(sarah@techcorp.com), VP of Engineering.
Created by: Mike Johnson.

Timestamp: 2026-02-21T11:42:08Z

View full payload in Webhookify Dashboard

Troubleshooting

  1. Workflow not triggering: Ensure the workflow is turned on (not in draft mode). Check the enrollment criteria -- the trigger conditions might be too specific. View the workflow history for any error messages.

  2. Webhook action failing in HubSpot: If the workflow triggers but the webhook action shows an error, check the URL format. HubSpot requires a valid HTTPS URL. Also verify that the Webhookify endpoint is active by visiting your Webhookify dashboard.

  3. Missing properties in notifications: If your notification does not include expected data, check the webhook request body in your HubSpot workflow. Make sure you are using the correct HubSpot property tokens (e.g., {{contact.email}} not {{email}}). Test the workflow with a record that has all the relevant properties populated.

  4. Delayed notifications: HubSpot Workflows can have slight delays, especially during high-activity periods. If notifications consistently arrive more than a minute after the event, check if the workflow has a delay action configured. Also verify that Webhookify's notification channels are functioning properly.

  5. Webhook not available in free HubSpot: The "Send a webhook" action requires Operations Hub Professional or Enterprise. If you are on the free plan, you can use a custom code action or a third-party tool like Zapier or Make to send HTTP requests to your Webhookify URL as an alternative.

Include the HubSpot record URL in your webhook payload by using the property token for the record link. This way, when you receive a notification on Telegram or Slack, you can click directly through to the HubSpot record to take action. For contacts, add "record_url": "https://app.hubspot.com/contacts/YOUR_PORTAL_ID/contact/{{contact.hs_object_id}}" to your webhook body.

Never Miss a Lead or Deal Again

Get instant HubSpot CRM notifications for new contacts, deal updates, form submissions, and more. Webhookify delivers AI-summarized alerts to Telegram, Discord, Slack, or your phone.

Get Started Free

Related Articles

Frequently Asked Questions

How to Set Up HubSpot Webhook Notifications with Webhookify - Webhookify | Webhookify