I have an OAuth app configured for users in multiple HubSpot portals. I have subscribed to webhook events for:
call:created
call.status_change
However, I am receiving an unusually large number of webhook events. The events are hitting my configured webhook URL almost every second, and within just a couple of days I have received over 350,000 events.
This does not appear to be normal. I was expecting only a small number of events corresponding to actual calls made by users in the HubSpot CRM using the native calling feature.
My concerns are:
The volume is unexpectedly high, and I suspect many events may be redundant or unrelated to real user actions.
I cannot easily identify which events are tied to legitimate user activity versus possible system triggers or background processes.
This large volume of webhook traffic is putting unnecessary load on my system.
Could you please:
Confirm why so many call:created and call.status_change events are being sent.
Suggest ways to differentiate real user-initiated events from other events.
Provide guidance on best practices for mitigating or filtering these events.
Check if there is any misconfiguration or known issue causing excessive event triggers.
I can share example payloads and timestamps if that would help in the investigation.
Hi @kpun7
Thank you for reaching out to the Community!
I’d like to invite some community members who are subject matter experts to join this conversation. @HubDoPete@CForrest5@Bortami - Would you be able to share any insights on this? Your expertise would be greatly appreciated.
Best,
Victor
I found some resources that might help with your excessive webhook events issue. While these discussions focus on deal events rather than call events, the filtering and deduplication strategies could be applicable to your situation:
Some key strategies that might work for your call events:
Event Deduplication: Implement backend logic to filter out redundant events for the same call ID that occur within a short timeframe
Dampener Mechanism: Add logic to dismiss multiple call.status_change events for the same call object that fire within X seconds of a call:created event
Immediate Response Pattern: Return HTTP 200 immediately to prevent HubSpot retries, then process events asynchronously
Given you’re seeing 350k+ events across multiple portals, there might be automated processes or system triggers creating/updating call records beyond normal user activity. The filtering approaches in that thread could help you identify and dismiss the non-essential events while preserving legitimate user-initiated calls.
Worth investigating if your webhook subscription configuration is capturing more than intended, or if background processes in your portals are generating excessive call activity.