Hi Tiago,

I think something else is going on because that issue is about binary files and you are trying to sent a JSON body.

Can you show us how you configured the parameters and how you configured the body of the endpoint?

What might be wrong that is if you have the body configured for instance with a single variable, for instance {my_json}, and you are already provoding the JSON in the correct format, in that case, the my_json input parameter should be configured with “Pre-Processing”: None.

If set to Auto, or JSON - it is treated as a parameter for a JSON field and will be escaped - making it an invalid JSON body when it was already provided as a correct JSON value, due to being escaped again.

We will update the documentation about the different Pre-processing options.

Can you let us know if that was the case?

If it is not the case, can you try with providing a hardcoded json value in the SF - to see if that works?

Hi ​@tiago,

Can you respond to the question Dick asked? Thanks in advance!

Hi All,

Thank you all for your repsonses. 

To be honest, I'm not really sure why it works now, while it didn't at first. I've been jogling around with the many combinations of vairables:

using {json_body},
""json_body]”
{">my_key_1]”: "{my_value_1}”,

"/my_key]”: {my_value_1}}

pre-processing none, or json 

with or without mentioning the content_type

without a doubt in some of the cases didn't pass the variable correctly and did not see that . 

So that's quite an amount of combinations, and I guess it worked, and I now use that as an example :-)

As I said in a previous comment: 
having a better view of what you are sending and where to, would help so much. 

take a look at how n8n works:
You can start a test run, and than use that to set the variables all in one screen. You have instand feedback if you do something wrong, whcih prevents having to test with every change you make. 

 

what I do here in one screen, I need to navigate to around 10-20 screens in Thinkwise, and it's easy to get lost. 

maybe a nice inspiration for the future

Hi Tiago,

Great you could find a solution.

We added more documentation to the docs, about the different pre-processing options and how to use them. Also, at the bottom some use cases that should help with using the web connections feature.

Web connections | Thinkwise Documentation

We also hope to work on the debug experience, that would probably make it easier to notice why the request is not working.