• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

JSON parse error illegal character

fisto

Member
Greetings,

I'm getting an error when sending data to Moxie, but I don't know how to solve it:

JSON parse error: Illegal unquoted character ((CTRL-CHAR, code 9)): has to be escaped using backslash to be included in string value; nested exception is com.fasterxml.jackson.core.JsonParseException: Illegal unquoted character ((CTRL-CHAR, code 9)): has to be escaped using backslash to be included in string value at [Source: (org.springframework.util.StreamUtils$NonClosingInputStream); line: 1, column: 4]

I have used Pabbly Text Formatter and javascript in Code by Pabbly to clean up any white spaces or tabs, and I still get the error.

I even try writing a couple of sentences, and try Save and Send Request and still get the same error.

So it must be something with Pabbly sending tabs inadvertently.

The problem occurs at Step 48
 

ArshilAhmad

Moderator
Staff member
Hi @fisto,

Task History ID - IjU3NmMwNTZjMDYzZTA0MzM1MjY5NTUzZDUxMzI1MTY2NTQzNiI_3D_pc

It seems that you are not passing the Due Date in the correct format, which appears to be causing the issue you are encountering.
1713380399163.png


1713380655714.png
 

ArshilAhmad

Moderator
Staff member
There was an unnecessary comma at the end in the Custom Values field. Removing that comma seems to have fixed your issue.
1715878026683.png
 
Top