-
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:
- Pabbly Connect
- Pabbly Subscription Billing
- Pabbly Email Marketing
- Pabbly Form Builder
- Pabbly Email Verification
- Pabbly Hook
- Pabbly Chatflow
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.
-
"unescape" input parameter for json safe request?
- Thread starter kalintro
- Start date
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")
From the integration app parameter definition inside the action:
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")
From the integration app parameter definition inside the action:
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.
- The "escaped parameter" is input from the client/workflow.
- The actual payload for the integration app request gets "escaped" again, resulting in a double-escaped parameter.
kalintro
Member
@Preeti Paryani ! Aha, you are absolutely right! Thank you very much for your help! 
Similar threads
