Any specific reason for Hubspot Trigger structure is different from Other Triggers like Chargebee?

I am trying to setup a workflow with hubspot trigger. Is there any specific reason for hubspot trigger being different than the other app triggers like chargebee?

Some Changes I noticed were,

  1. Asking Credentials for a trigger
  2. In HubspotTriggerNode.ts file I can see Webhook as default option and also a setup option. But its not getting displayed anywhere.
  3. Are the Developer App Credentials being asked in step 1 to communicate and setup webhooks in the developer app ?

The reason I am asking is why not we simplify this trigger like Chargebee trigger.

Information on your n8n setup

  • n8n version: - V0.219.1
  • Database you’re using (default: SQLite): - Postgres
  • Running n8n via [Docker, npm,, desktop app]: - Docker Compose Self hosted

Hi @Mahesh_Thiru,

Trigger nodes are designed to automatically add the webhook url to the service you are using so that you don’t need to do it. Chargebee was made before that was an option and part of the setup involves having to manually add the webhook to Chargebee.

You would need to authenticate an API call to add a webhook which is why they trigger nodes tend to require that.

The quick version is the Chargebee node is 4 years old and has had no love since it was created.

1 Like


I understand now. Thank you for the response.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.