Pro Forms: Text/Numeric field data to Webhook

Bug Reports
1

When I try to connect a Text or Numeric field to send data to a webhook, if that field contains only a string of numers i.e 9370922530723087, the data captured by the webhook is missing the double quotes “” around the numeric value.

for example my webhook receives the data in this format:

"body": 
{
"code": 9370922530723087,
},

The webhook that receives the data is in n8n and without the double quotes wrapping the number, n8n fails to receive the correct number.

To see what I mean, you can try sending the following numbers to a webhook via a Text or Numeric field:

9370922530723087 → n8n saves it as 9370922530723088
9370922530723055 → n8n saves it as 9370922530723056
9370922530723065 → n8n saves it as 9370922530723064

The problem gets solved if the data in n8n is received wrapped in double quotes like this:

"body": 
{
"code": "9370922530723087",
},

I recorded a short video showing how n8n fails to save correctly the data if the number is not wrapped in double quotes: ▶️ - n8n[DEV] - Google Chrome - 18 September 2025 | Loom
In the video I say that the problem is with n8n, but then later I understood that the number is not wrapped with double quotes and this causes incorrect information to be saved. As soon as I wrapped the number with double quotes, then I could save it correctly.

I tried wrapping the value that I send to the webhook with double quotes like this:

image
image357×195 6.86 KB

as well as with every other possible combination I could think of but nothing seemed to be working.

Please let me know if this is a Pro Form bug and if you can please fix it.

2

Hi @Daniele, any chance you can please look into this?

Also I have problem with codes that start with zero (0). n8n does not accept in the json this format:

image
image665×184 17.4 KB

However if it is wrapped in double quotes, then it’s fine:
image

3

@Daniel Is the pro form responsible of sending the webhook data wrapped in double quotes or not?

If I input only numeric characters in the number field or the text field, then the data in that field is sent plain without being wrapped in double quotes.

I need to understand why this is happening and whether I need to contact n8n about this.

4

I don’t know what was the error here, but I solved it be sending the field numeric value by injecting a short string so to force n8n to receive the value as a string rather than a number. When it’s received as a string, then the value is wrapped in double quotes " " and the number is preserved correctly. I then strip the added string out from the number in n8n using a Set Field.