• 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

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

Socketlabs integration not working

solipsist

Member
Did some digging.

The issue is that some of the fields are not properly encoded, so they cannot be used in the HTML Body field as they are.

The Socketlabs integration needs to properly encode the data in the HTML Body and Text Body fields.
 

solipsist

Member
Secondly, the HTML Body field does not allow new lines. Again, the integration should properly encode the data and strip new lines.
 

solipsist

Member
I've confirmed it's line breaks that cause the "invaliddata" error.

Bug report to your devs: Socketlabs integration does not properly encode the field for message body, leading to a failed request in case one or more new lines are used in the HTML Body field.
 
A

Arshita

Guest
Hey @solipsist

Kindly provide us the workflow name in which you are getting issues.

So we can check on it and guide you further.
 

ArshilAhmad

Moderator
Staff member
I am unable to find the InvalidData - PostBody parameter does not have a valid structure, or contains invalid or missing data error you are referring to, in the workflow you have shared.
 

solipsist

Member
I am unable to find the InvalidData - PostBody parameter does not have a valid structure, or contains invalid or missing data error you are referring to, in the workflow you have shared.
That is from the socket labs api docs. I had to try to figure out what “invaliddata” (the error message pabbly gave me) means. So I looked it up. Please re-read this thread and it will make sense.

As I wrote, here’s the issue for your devs:

The socket labs integration does not escape new lines in the body html field (probably true for the body text field too…)

How do I know? I managed to work around it by deleting all new lines in that field.
 
P

Pabbly13

Guest
Hey @solipsist !

Kindly provide us with the screenshot of the concern, in which you have received the error?

Accordingly we can further investigate on the concern and guide you on it.
 

solipsist

Member
1710584035145.png



1710584041706.png


Please fix this poorly written Socketlabs integration code.
 

solipsist

Member
That does not fix the issue.

Creating line breaks is not a problem. I'm using p tags as you can see.

The problem is that the field is extremely unforgiving to the user. Nowhere does it say you cannot put line breaks. But even so, the way your components are designed, line breaks are almost impossible to spot. If a line break or newline is present, the integration simply fails with the obscure error "invaliddata" (see above).

All of this can be avoided if you simply stripped or escaped line breaks (\r) and newlines (\n), in your code.

Ergo; the integration with Socketlabs is broken.

Please fix your code.
 

ArshilAhmad

Moderator
Staff member
Please allow me some time to discuss this with my technical team. We will get back to you with an update soon.
 
Top