HI,
I have a WF with a HubSpot trigger, start with a Contact.Property Changed.
I dont´know why is not working.
Doing manual update in hubspot the trigger is not responding.
IF done with a new contact and manual check it works.
Any idea?
Thanks !
Hi @Juan_Pablo_Sanchez, welcome to the community 
Hubspot is very picky when it comes to integrating with n8n’s trigger functionality unfortunately (as seen in this Hubspot mega thread).
Are you by any chance using separate workflows or n8n instances? Hubspot only allows a single webhook URL per developer app. So if you have multiple n8n triggers configured with the same Hubspot app, only one of them would work as expected.
You can view the current configuration in Hubspot’s UI for each developer app and compare the URL shown against the webhook URL shown for your n8n trigger.
Hubspot:
n8n:
Great Answer!, i do i have more HS triggers in other WF´s.
I will check this!
Thanks
JP
,)
1 Like
Hi, just again with this and i have a doubt ;=)
IF i ADD more webhooks to the same App it will not work. is it right)
IF I CREATE a new APP and CREDENCIAL it will work? ( means i will have 2-3-4 HS Apps and each APP just for 1 N8N Workflow?.
My end is to substitute the native WebHook in hubspot ( workflows) that you can only use if you have the PRO licence and subtitute by different N8N Workflows.
Thanks!
JP
Iirc correctly Hubspot only allows one webhook URL per app. So you’d indeed need to create another app if you want to use different webhook URLs.
Alternatively you could consider just setting up one webhook for all events and then use Switch or IF nodes in your main workflow to narrow things down.
If i go with the Switcher option. That means i will have less granulate and more request x month is it right?
thanks again
JP
That means i will have less granulate and more request x month is it right?
This depends on the events you receive from Hubspot. But yes, if you go with “all events” that’s certainly possible.
Not possible to create different webhook URLs since N8N by default doesnt allow us to change the URL.
Hi @Hugo_Aroeira, welcome to the community!
It’s important to know that Hubspot only allows a single webhook URL. So you will not be able to use multiple trigger nodes unless you register and manage different Hubspot applications.
That said, n8n let’s you create different webhook URLs. Simply create a new Hubspot trigger node from scratch (rather than copying an existing one) and it should use a new webhook URL.
2 Likes
Do not spend time on setting up a public application and connecting it to n8n. For me it turned out as waste of time exactly because of the webhooks issue. Not 100% agree that it is pure HubSpot issue, as it seems to work fine in zapier.
Nevertheless, here is a workaround:
- Create one major webhook in n8n, and copy it’s URL. I used Production URL here, so I cannot use Test button, but history of executions helps a lot!
- Create a private app in HubSpot
- Create for it a webhook and use the URL from step 1
- Create subscriptions manually for that webhook.
- Implement a fallback logic to cover all possible scenarios in n8n. Like I did:
So you have only one webhook in HubSpot (their limitation), and only one active workflow in n8n handling it. Then you implement sub-workflows to handle every specific case.
The ‘Respond to Webhook’ nodes help, but in HubSpot Workflow logs I can see only the response code, not the text. Not perfect, but good enough for debugging.
I was told by HubSpot Support that webhooks for custom contact fields are only supported in enterprise accounts or with operations hub using a workflow that sends a web hook.
I’m trying to get custom contact properties out of HubSpot into N8N when those properties are changed in HubSpot. Does anyone know if that’s possible and if so, which N8N node they used to receive that change event from HubSpot.?
This is really helpful, so thank you. I have a related question here. We have a workflow using Hubspot credentials from a private app. I think a different workflow, with a Hubspot trigger running off credentials from a public app should work, but the sense I’m getting is that actually making these bits play together predictably is not always straight forward?!
Confirmed I can get custom fields out of webhook subscriptions in hubspot. The trick is, when selecting the record to add to the subscription - use the field ID - just past it in and it will be good - because it wont show in dropdown.
This is a tricky thing hubspot does. They leave the custom fields off. But it works when you paste it in the dropdown.