This started out as fiddling with getting newlines encoded for a HTTP POST, but it turns out that's not solving the issue. As soon as other things that json needs escaped wind up in your request, it's borked all over again.
A solution would be: have a checkbox that allows input data to a POST to be json "stringified" (as javascript calls it).
Another angle would be to have the reverse of the json parse action that already exists - a json encode action - then one could just preprocess and then create the POST, and the encoder could be useful elsewhere too. Lots of things talk in json...
Anyhow thanks so much for macrodroid!
A solution would be: have a checkbox that allows input data to a POST to be json "stringified" (as javascript calls it).
Another angle would be to have the reverse of the json parse action that already exists - a json encode action - then one could just preprocess and then create the POST, and the encoder could be useful elsewhere too. Lots of things talk in json...
Anyhow thanks so much for macrodroid!