I would suggest looking and trying the followings:
1. Confirm the subscription event is correct and active Check that the subscription is set specifically to Deal creation (not property changes) and that the subscription is Enabled.
2. Test HubSpot’s connection directly On the Webhooks tab, use “Send test”. – If the test does not appear on webhook.site → HubSpot is not sending anything (wrong URL, subscription disabled, wrong app). – If the test works but real events don’t, the issue is the event type or portal mismatch.
3. Check the webhook logs In the same Private App page, open Webhook Logs. If HubSpot doesn’t show any attempts when a deal is created, the subscription is not firing at all.
4. Confirm you're in the correct HubSpot portal This is a very common miss: The Private App must be installed in the same portal where you’re creating the deal. Otherwise, HubSpot won’t trigger the event.
5. URL requirements Make sure the URL has no trailing slash and is exactly the one you copied
Let me know if this helps, or if you have any other questions!
✔️Was I able to help answer your question? Help the community bymarking it as a solution.
Hi @AJóźwiak thanks for sharing the screenshots and the follow-up, what you observed is actually consistent with how HubSpot splits “legacy” webhook subscriptions across app types. A couple of things are easy to miss here. The “deal.creation” you showed is a legacy webhook subscription, and the behavior (including whether you can see delivery logs in the UI) depends on whether you’re configuring it under a private app vs a public app and which portal the app is installed in. Public apps can absolutely receive webhook events, but the monitoring experience is not always the same as private apps, especially if you’re looking for the Webhook Logs inside the private app screen.
If you want to make this rock-solid for n8n testing, the best sanity checks are: confirm you’re creating the deal in the exact same portal where the app is installed, confirm the subscription is created under that same app, then validate deliveries via the webhook subscription logs rather than only relying on webhook.site. HubSpot’s guide on creating/editing subscriptions and inspecting logs is here (https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/create-and-edit-webhook-subscripti...
Also, keep an eye on throttling and timing. HubSpot can take a few minutes for subscription changes to apply, and if the endpoint is slow or intermittently blocked, HubSpot will retry and you’ll only see that clearly in the subscription logs. The general webhook docs are here as well: https://developers.hubspot.com/docs/api/webhooks.
If you can share which exact events worked only on the public app vs only on the private app, that detail usually reveals whether it’s an app-scope/config issue or just where you’re looking for logs.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
Hi @AJóźwiak thanks for sharing the screenshots and the follow-up, what you observed is actually consistent with how HubSpot splits “legacy” webhook subscriptions across app types. A couple of things are easy to miss here. The “deal.creation” you showed is a legacy webhook subscription, and the behavior (including whether you can see delivery logs in the UI) depends on whether you’re configuring it under a private app vs a public app and which portal the app is installed in. Public apps can absolutely receive webhook events, but the monitoring experience is not always the same as private apps, especially if you’re looking for the Webhook Logs inside the private app screen.
If you want to make this rock-solid for n8n testing, the best sanity checks are: confirm you’re creating the deal in the exact same portal where the app is installed, confirm the subscription is created under that same app, then validate deliveries via the webhook subscription logs rather than only relying on webhook.site. HubSpot’s guide on creating/editing subscriptions and inspecting logs is here (https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/create-and-edit-webhook-subscripti...
Also, keep an eye on throttling and timing. HubSpot can take a few minutes for subscription changes to apply, and if the endpoint is slow or intermittently blocked, HubSpot will retry and you’ll only see that clearly in the subscription logs. The general webhook docs are here as well: https://developers.hubspot.com/docs/api/webhooks.
If you can share which exact events worked only on the public app vs only on the private app, that detail usually reveals whether it’s an app-scope/config issue or just where you’re looking for logs.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
I would suggest looking and trying the followings:
1. Confirm the subscription event is correct and active Check that the subscription is set specifically to Deal creation (not property changes) and that the subscription is Enabled.
2. Test HubSpot’s connection directly On the Webhooks tab, use “Send test”. – If the test does not appear on webhook.site → HubSpot is not sending anything (wrong URL, subscription disabled, wrong app). – If the test works but real events don’t, the issue is the event type or portal mismatch.
3. Check the webhook logs In the same Private App page, open Webhook Logs. If HubSpot doesn’t show any attempts when a deal is created, the subscription is not firing at all.
4. Confirm you're in the correct HubSpot portal This is a very common miss: The Private App must be installed in the same portal where you’re creating the deal. Otherwise, HubSpot won’t trigger the event.
5. URL requirements Make sure the URL has no trailing slash and is exactly the one you copied
Let me know if this helps, or if you have any other questions!
✔️Was I able to help answer your question? Help the community bymarking it as a solution.
I think that I have already solved the issue. Some types of events work with public apps (logs are not visible) and some work with private apps (logs are visible). It is really strange, however I can say that it works.
Would you be willing to please provide a bit more detail about what you're observing in your responses/logs? We can check the webhook subscriptions logs like seen in our guide on the matter here!
Could you also provide the steps you're taking to test the webhook trigger? This should allow for ourCommunity to provide better assistance for your issue here.