HubSpot webhooks send data from your CRM to an external system the moment a trigger fires. When a trigger fires in HubSpot, it can push that information to an external application in real time rather than waiting for a scheduled export or manual data pull.
This guide explains what HubSpot webhooks are and how to use them effectively, with context for teams in Southeast Asia.
Decide which HubSpot event should fire the webhook: a workflow enrollment trigger or a deal stage change are the most common starting points. Webhooks in HubSpot run through workflows, so you need a workflow as the delivery mechanism.
Go to Automation > Workflows. Create a new workflow and set your enrollment trigger. Most setups use a contact-based or deal-based workflow, depending on what you want to send.
Inside the workflow, click the plus icon to add an action. Search for “Send a webhook.” Enter your endpoint URL and choose POST as the method. HubSpot sends a JSON payload containing the object properties you specify.
You can send all properties on the record or select specific ones. For most use cases, sending a focused set of properties keeps the payload clean and easier for the receiving system to process.
Use a tool like Webhook.site or a dedicated test endpoint in your receiving application to verify the payload structure. HubSpot shows the full JSON it sent in the workflow history.
What is a HubSpot webhook?
A webhook is an HTTP POST request that HubSpot sends to a URL you specify. The receiving URL is usually an endpoint in your own application, an automation tool like n8n or Make, or a middleware service. When the trigger condition is met, HubSpot sends the data immediately.
This differs from the HubSpot API, where you pull data on demand. With a webhook, HubSpot pushes the data to you. The result is near real-time data flow without polling.
When should you use a HubSpot webhook instead of a native integration?
HubSpot has a large integrations library with pre-built connectors for popular tools. In most cases, those connectors are easier to set up than a custom webhook.
Webhooks become the right choice when:
- There is no native integration for the system you need to connect
- You need more control over what data is sent and when
- You are building a custom internal application that needs HubSpot data in real time
- You are using a middleware platform like n8n to route data across several systems simultaneously
Teams in Southeast Asia connecting HubSpot to LINE Notify or region-specific payment platforms that lack a native integration will typically find webhooks are the only practical route.
What does a HubSpot webhook payload look like?
HubSpot sends a JSON array where each item describes one event. A typical contact property change event carries the portal ID and object ID to identify the source record, alongside the property name and its new value. A timestamp is included for ordering events.
When you use the workflow-based webhook action, the payload format is slightly different. It sends the properties of the enrolled record as a flat JSON object, which is usually simpler to work with downstream.
What are the most common HubSpot webhook use cases?
Syncing data to a custom application. If your company has an internal operations system outside the HubSpot marketplace, a webhook can push contact or deal data to it the moment something changes in the CRM.
Triggering notifications in messaging platforms. A webhook can call an endpoint that sends a LINE message or Slack notification when a high-value lead fills in a form or when a deal moves to a specific stage.
Feeding data to a data warehouse. Teams using BigQuery or a similar data platform can receive webhook events and write them into their pipeline without waiting for nightly exports.
Connecting to regional booking or payment systems. For hospitality and retail teams in Southeast Asia, webhooks allow HubSpot to notify a booking system when a deal closes or a contact upgrades to a paying customer.
How do HubSpot workflows trigger webhooks?
All webhook actions in HubSpot run through workflows. This means you have the full power of HubSpot workflow automation to control when the webhook fires. Before the webhook fires, the workflow supports conditional filters and time delays to control which records trigger the call.
This approach gives more precision than a simple trigger-and-send model. You could scope it to high-value deals only. You could also restrict it to contacts from a particular acquisition source.
What limits should you know about?
HubSpot enforces rate limits on webhook requests. The receiving system must respond with a 200 status code within a set timeout or HubSpot marks the request as failed. Repeated failures on a workflow action can cause the workflow to pause for that contact.
It is good practice to build your receiving endpoint to respond immediately with a 200 and then process the data asynchronously. This avoids timeout failures caused by slow downstream processing.
Note also that HubSpot does not include webhook signatures by default in the workflow action. Validate the incoming payload on your end using the portal ID or a shared secret passed as a header.
FAQ: HubSpot webhooks
Do I need a paid HubSpot plan to use webhooks?
The webhook action is part of HubSpot’s workflow engine and requires a paid Marketing Hub or Sales Hub plan. Free CRM users do not have access to workflows.
Can I receive webhook data from an external system into HubSpot?
That is the reverse flow: you would use the HubSpot API to write data into HubSpot. Webhooks only send data out. For inbound data from external systems, look at the HubSpot API or a middleware connector.
How do I retry a failed webhook?
Check the workflow action history for the contact. If the request failed, you can re-enroll the contact in the workflow or trigger a manual re-run. Building your receiving endpoint to be idempotent (safe to process the same payload more than once) is worth doing before go-live.
What format does HubSpot use for the webhook payload?
JSON. The exact structure depends on whether you use the workflow-based action or the native webhook subscription API. Workflow-based payloads send the record properties as a flat object, which is straightforward to parse.
Can HubSpot send webhooks to multiple endpoints at once?
In a single workflow, you can add multiple webhook actions pointing to different endpoints. The native webhook subscription API also supports multiple subscriptions per event type.
This site is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a registered trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us