• 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.

"unescape" input parameter for json safe request?

kalintro

Member
Hi there! Does anyone know how to "unescape" a input parameter? For example i want this input: This is a "test" to become: This is a \"test\"
 

kalintro

Member
I get this when sending in a "html template" through a string parameter in my pabbly app: Bad control character in string literal in JSON at position 2 (line 1 column 3). But if i send in the "json safe" and escaped parameter, pabbly "double escapes" the actual request to the api? Is there a way to send in a "json safe" parameter through the workflow client, which doesnt get re-escaped or double escaped as e final result in the integration request?


This is the current result: {"html_template":"<!DOCTYPE html>\\r\n<html lang=\"en\">\\r\n <head>\\r\n <meta charset=\"UTF-8\">\\r\n <title>Invoice</title>\\r\n .....


Desired result: {"html_template":"<!DOCTYPE html>\r\n<html lang=\"en\">\r\n <head>\r\n <meta charset=\"UTF-8\">\r\n <title>Invoice</title>\r\n .....



(When sending in the "raw" html input as shown in the image beneath., I get a json error.. if i send in an "escaped" input, the final result becomes "double escaped as shown above when the API recieves the request")

1736498076893.png


1736498096607.png


From the integration app parameter definition inside the action:
1736498136548.png
 
Last edited:

kalintro

Member
Thanks for the reply, @Preeti Paryani ! I don’t think that will solve the problem because, while the parameter will be valid for triggering the request (JSON valid), the request data will be "double-escaped" in the actual and final payload.

  1. The "escaped parameter" is input from the client/workflow.
  2. The actual payload for the integration app request gets "escaped" again, resulting in a double-escaped parameter.
So, the question is: is there a way, either in the integration or the client workflow, to avoid this double escaping, etc.?
 

Preeti Paryani

Well-known member
Staff member
Hello @kalintro,

We have added a Text Formatter step in your workflow to replace double quotes with single quotes. The updated response has been mapped to the PDF.app step, and it worked successfully. Please refer to the attached image for more details.

1736509386980.png
 
Top