• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

Data Forwarder bug with booleans

raulbooqi

Member
Your Task History ID
IjU3NmQwNTZjMDYzZjA0MzM1MjZlNTUzMDUxMzQ1MTY1NTQzNyI_3D_pc
We've been using Pebbly Connect for only one day and unfortunately we already found a bug. When using the 'Data Forwarded' to forward a webhook call to another API, I found out that keys that are in the root of the JSON body and are of type 'boolean' will be parsed to a empty string. The weird thing is that an array of objects with booleans inside will work just fine. So for example:


JSON:
{
    "test": true
}

// Will become

{
    "test": ""
}

// And this will work just fine

{
    "test": [
        {
            "test": true
        }
    ]
}

We really need this to be exactly the same. How can we make it work?
 

raulbooqi

Member
{
"subscription": true,
"status": "COMPLETED",
"rebooking": false,
"product": {
"title": "SECRET",
"plot": {
"timeStart": "SECRET",
"timeEnd": "SECRET",
"id": "SECRET",
"date": "SECRET"
},
"id": "SECRET"
},
"paymentMode": "LIVE",
"id": "SECRET",
"entries": [
{
"type": "ITEMS",
"title": "SECRET",
"quantity": "SECRET",
"prices": {
"unit": "SECRET",
"total": "SECRET",
"tax": {
"value": "SECRET",
"percentage": "SECRET"
},
"subtotal": "SECRET",
"net": "SECRET",
"gross": "SECRET",
"discount": "SECRET"
}
}
],
"customer": {
"name": {
"last": "SECRET",
"full": "SECRET",
"first": "SECRET"
},
"id": "SECRET",
"fields": {
"straße": "SECRET",
"stadt": "SECRET",
"postleitzahl": "SECRET",
"ichMöchteMichFürDenNewsletterAnmelden": "SECRET",
"ichAkzeptiereIhreAllgemeinenGeschäftsbedingungenUndDenDatenschutzerklärung": "SECRET"
},
"email": "SECRET"
},
"created": {
"timezoneType": "SECRET",
"timezone": "SECRET",
"date": "SECRET"
},
"barcodes": [
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET",
"SECRET"
],
"audiences": [
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
},
{
"price": "SECRET",
"name": "SECRET",
"itemId": "SECRET",
"id": "SECRET",
"grouped": true,
"barcode": "SECRET"
}
],
"amount": "SECRET"
}
 

Luv

Member
Hey @raulbooqi

Kindly allow us some time to find a resolution for this issue. We have raised this to our technical team, they are currently looking into this.

Your patience will be greatly appreciated.
 
Top