I am reaching out to request your assistance in investigating an issue we are experiencing with events sent from HubSpot to n8n. We have noticed that events intended to trigger specific workflows (for example, the New Deal event) are behaving inconsistently — sometimes they fire correctly, and other times they do not trigger at all.
Additionally, no related activity appears in the HubSpot logs, which makes it difficult to verify whether the webhook was sent or to diagnose the root cause of the problem.
Could you please review this issue and check whether there are any problems on the HubSpot side that might be affecting the delivery or consistency of these events?
Thank you in advance for your support. I look forward to your response.
Hey @AJóźwiak - thanks so much for posting in the Community!
To ensure we get you the best support possible, can you provide a bit more context around the inconsistent behavior you noted above. Specifically, are there any differences in the events where the workflows were triggered correctly versus those where they did not? Any screenshots of these logs (without private information) can also be really helpful to identifying what may be causing this.
Shane, Senior Community Moderator
I am creating a Deal in HubSpot (always in same way). Sometimes this webhook triggers the workflow in N8N and sometimes not (About 7-8 tries of out 10 are successful).
Unfortunately the logs related to successfull and/or unsuccessful events don’t appear in the console, so I’m not able to share them.
Best Regards,
Adam
Hey @AJóźwiak - thank you for this context!
I’d like to tag in some Community experts to see if they have insight that may help us out here! @HubSpot_Corey, @ChristinaKay, and @CateDuarte - any thoughts for @AJóźwiak?
Shane, Senior Community Moderator
Thanks for reaching out to the Community. I use HubSpot webhooks a lot and they’ve been very reliable in my experience.
One thing that can be confusing at first: HubSpot webhooks are batched. They’re designed to send multiple events in a single webhook request if those events happen close together in time. So if you create 10 deals around the same moment, you might not receive 10 separate webhook calls. Instead, HubSpot may send:
1 webhook containing all 10 events, or
several webhooks split into smaller batches, or
10 individual webhooks
The exact batching behavior isn’t publicly documented, but HubSpot does state the following in their official docs Webhooks API - HubSpot docs:
“As shown above, you should expect to receive an array of objects in a single request. The batch size can vary, but will be under 100 notifications. HubSpot will send multiple notifications when a lot of events have occurred within a short period of time. For example, if you’ve subscribed to new contacts and a customer imports a large number of contacts, HubSpot will send you the notifications for these imported contacts in batches and not one per request.”
Because of this, your n8n webhook endpoint must be able to handle an array of events in a single payload. If the workflow expects only one event per request, it may fail or only process the first item and ignore the rest.
I’d recommend checking whether your n8n setup is correctly looping through and processing every event in the batch. That’s often the root cause in cases like this.
Did my post resolve your question? If so, please consider marking it as the accepted solution to help others in the community.
Kind regards
Dennis
The problem exists even if I’m triggering a single event, but probably I’ve found the solution. I’m using webhooks on a free version of HubSpot, where Private Apps don’t exist. Instead of private apps there is an integration called 'Legacy apps", which seems to be less reliable and not supported.
Can it be the reason of my problem and after upgrading HubSpot to higher tier the problem should disappear?
For example after upgrading to Operations Hub Starter I should be able to use Private Apps?
Thank you in advance for the reply and wish you nice rest of the day!
Hi @AJóźwiak,
Legacy apps are the same as what were previously called Private apps. The feature was renamed from “Private apps” to “Legacy apps” within the settings relatively recently. Aside from this terminology change, there is no difference in functionality or performance, and these apps remain available on both free and paid plans.
Did my post resolve your question? If so, please consider marking it as the accepted solution to help others in the community.
Kind regards
Dennis
