# Coerce Data Types in Webhook Payloads

**URL:** <https://community.hubspot.com/t/coerce-data-types-in-webhook-payloads/143759>\
**Category:** HubSpot Ideas\
**Tags:** api\
**Created:** [December 5, 2025, 10:40pm UTC](https://community.hubspot.com/t/coerce-data-types-in-webhook-payloads/143759 "2025-12-05T22:40:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![HumbleTinker](https://avatars.discourse-cdn.com/v4/letter/h/e47c2d/32.png) [@HumbleTinker](https://community.hubspot.com/u/HumbleTinker)\
**Post date:** [December 5, 2025, 10:40pm UTC](https://community.hubspot.com/t/coerce-data-types-in-webhook-payloads/143759/1 "2025-12-05T22:40:41Z")

</div>

When building a custom Webhook from PandaDoc, I ran into an issue where the linked HubSpot Record ID of a Deal sent to HubSpot in the Webhook was passed as a STRING (contained in quotes in the payload body.)

When recieving the webhook in HubSpot, selecting the data type NUMBER **does not actually coerce the data to be a NUMBER** , nor does it flag an issue with mismatched data. It just proceeds and quietly fails.

**This results in a failure state in the Webhook build** when trying to create custom Webhooks from PandaDoc - regardless of whether you’re using the Workflow Webhook trigger UI, or the Custom Event UI to recieve the webhook.

I have also raised this issue with PandaDoc to find out if that datapoint can simply be changed to NUMBER in the case of Webhooks going to HubSpot.