Hi @NDory , I know this one is frustrating. The n8n “HubSpot Trigger” only fires when HubSpot actually sends a webhook, so if the subscription or auth is slightly off, you’ll see nothing in n8n even though you change a deal stage.
Two reliable paths. First, make sure the trigger is backed by a webhook subscription for the Deals object and the dealstage property. That means the app used by n8n is installed in the same HubSpot portal where you’re testing, and it has the right CRM scopes. In practice, you want a subscription on “propertyChange” for deals, and then change a deal’s stage and hit Save to emit the event. Details on how HubSpot webhooks work and what must be subscribed aree here
(Accounts Dashboard | HubSpot )
Quick sanity checks: the app is installed on the correct account, dealstage is the property you’re listening to, and you’re not filtering to a pipeline or stage value that your test never hits.
Second, if you just need this working today, avoid the app/webhook complexity and let HubSpot fire a webhook from a native Deal workflow
Create a Deal-based workflow, set re-enrollment on “Deal stage changes,” then add the “Send a webhook” action pointing to your n8n Webhook node URL. This is very stable and easy to debug from workflow history Tiny tip: enable re-enrollment so every stage move retriggers, not only the first.
(How to Trigger Webhooks in HubSpot Contact-Based Workflows )
One question to help narrow it: are you using a Private App token or an OAuth app for the n8n node, and is that exact app installed on the same portal where you’re moving the deal?
If keeping HubSpot and your other system in step is the real blocker, Stacksync keeps both sides aligned in near real time so you don’t chase fixes later.