HubSpot trigger node Failed to create subscription, `propertyName` must be set for this event type

Questions
,
1

We added the HubSpot Developer API credential that is going to be used in
HubSpot trigger node for ticket propertyChange event but when we run the workflow we get this error:

HubSpot Trigger: Failed to create subscription, propertyName must be set for this event type.

image
image1047Ă—505 12 KB

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @SearchActions

What kind of scopes have you set for your App? Also, are you using other trigger nodes for the same App?

4

Hi there ! Thanks for the reply.
We are using just one trigger node with the following scopes:

image
image762Ă—477 14.7 KB

We were following the n8n docs on adding Developer API key

5

Hi @SearchActions

Could you try adding the ticket scope and see if that works? :eyes:

6

We added it but we are getting the same error :confused:

image
image1017Ă—416 26.2 KB

7

Hi @SearchActions

Thanks for the feedback. Will raise an internal ticket for this and keep you updated here.

8

Great! Thank you!

10

I just signed up for a trial with n8n and am experiencing this same issue. Confirmed my settings are correct as per docs and have all the scopes needed. Trying to connect results in an error message stating the scopes are insufficient.

Side note: really confusing that there are 3 valid connection types for HubSpot, and only the HubSpot Trigger apparently can be used for things like “Contact Property Updated” and it requires a Developer API setup, rather than a Private App.

11

I also noticed this bug with the Hubspot Trigger node, I have opened a PR to fix it so that when selecting the property change event it will show a dropdown for the ticket property to watch for changes (similar to how the deal property event works)

image
image710Ă—686 30.4 KB

fix(Hubspot Node): Hubspot Trigger add the propertyName param for ticket.propertyChange event by dkarzon · Pull Request #12594 · n8n-io/n8n · GitHub

1 Like
12

I have the exact same issue at this moment, there is no dropdown for “Ticket Property Changed” to set the Property Name. Is there a known workaround?

13

Hi, i am having this same problem with ticket property trigger node

Do you have any estimation when this bug will be corrected?

14

Same problem here.
The thing is that if we follow the n8n documentation, the scopes do not contain the tickets one.
BUT if you add the tickets scope, then the connection to hubspot does not work saying that the scope are insufficient.
So the problem is more about letting us the possibility to add the ticket scope to the hubspot app, and make sure the n8n credential succeed to connect to hubspot with this scope set up.
Then we’ll probably have the dropdown list with properties

15

This still doesn’t work…

16

Same issue in the self hosted hubspot trigger node. The problem is that when you attempt to add the scopes:
tickets
conversations.read

It will not reauthorize the new scopes. It will work with the basic object scopes enabled but none of the conversation or ticket triggers will work. The help docs do not even mention these two triggers or anything about adding scopes for them. I have expiermented with adding tickets and conversations.read as optional and conditionally required scopes, but neither of those work either because when you reauthorize, or delete the credential and re-add it, it will not authorize these scopes. The auth acceptance screen flashes so fast that you can not even read it to check the optional scopes to enable them.

The help docs need to be updated to explain how to get these two triggers to work.
HubSpot node documentation | n8n Docs