Inbound webhooks - array issues

[TimPonting]

Your Task History ID

IjU3NjUwNTY4MDYzMDA0Mzc1MjZiNTUzNzUxMzI1MTYxNTQzMDBmMzIi_pc

Hi there

My inbound webhooks seem to be misbehaving today - for example giving different results from the same input between this morning NZ time and this afternoon.

Arrays being passed in sometimes are just exposed as the word "Array" with no actual data. But this issue is sometimes only visible when you refresh your inbound webhooks and look at them - they may still run OK in the live environment and be parsed properly as an array. At other times, the opposite is true - some arrays don't work in the live environment (passing an array onwards as the word "Array" not the array data) but the field data looks fine when you refresh your inbound webhooks and look at it in non-live environment.

Any clues?

E.g. screenshot shows the "Entry" array in the non-live environment. But if you look at the related Task history id supplied the Entry array was properly passed in and didn't fail. However, an array which IS visible as an array in the non-live environment was passed on to Airtable as the word "Array" (see the field "PaymentTest" in the Task History - the array data appeared in an Airtable text field as the word "Array".)

 

[TimPonting]

In case anyone is watching this one - I can now see some data properly in the non-live environment editing the automation, but some arrays are being picked up correctly, others simply as [Array]

 

[TimPonting]

OK, so digging deeper into the Task History, the Arrays are now currently arriving correctly in the live and editing environments, but internally the Array is being converted to the word "Array". One screenshot shows the arriving array (I also stripped the outside array square brackets to see if the same thing happened) and the other screenshot shows the JSON sent to Airtable directly from this input is the text "Array".
In this case the TaskID is IjU3NjUwNTY4MDYzMDA0MzA1MjZmNTUzMzUxMzA1MTYxNTQzNjBmMzUi_pc

 

[ArshilAhmad]

Hi @TimPonting,

Webhook by Pabbly is based on descriptive webhooks. We don't have any control over the manner in which the source application sends data to Pabbly Connect. We simply provide the webhook URL and display the data as it is.

You can connect your source application with webhook.site, and you will see that the same data arrives there as well.

We suggest you get in touch with the source application's support team to understand why you are encountering this issue.