As an administrator, when setting up a Hubspot OAuth, there is an option to configure Webhooks from Hubspot to Apideck.

Problem:

Since there are multiple systems (Hubspot, Apideck, your system) involved, it might be that there are no webhook events arriving in Unify, resulting in no Webhook events being pushed to your system.

Solution:

In this troubleshooting guide, we want to provide an overview of the different configurations you can verify and debug.

Make sure you have created and configured your own Hubspot OAuth credentials in Apideck.
​
You can follow our steps from our How to create an OAuth app in HubSpot guide.

Verify in Apideck, that you are using the Hubspot client ID & Secret of your own Hubspot OAuth App.

Review and configure the webhook subscription in Hubspot, as described in our guide How to configure Hubspot webhooks?

After you log in to the developer portal of Hubspot, navigate your OAuth app and click on the "Webhooks" menu item.

In the "Event subscriptions" section, you will see all the events you are forwarding to Apideck. The count column indicates how many events have been pushed.

When you click on a specific event, you can view the webhook logs from Hubspot.

You can inspect a log item by clicking it, which will show you all the details of the event and the result status.

When there a no changes made in Hubspot, there will be no events pushed to Apideck.
In that case, the count column in the Hubspot webhooks subscription page will show 0.

After making changes in Hubspot, related to your subscription type, you should see events being triggered. You can validate this by reviewing the logs as described in the "Verify Hubspot webhook logs" step.