@hawky4s Thanks for the details. Looks like it was the Content-Type header that was causing the problem.
On a related note, I see if your parseresults.js code you reference connector. Is there a list of internal names for referencing different objects in Camunda?
On related note, this is what the final code example looked like; used inline Javascript for the Payload:
var lat = execution.getVariable("Latitude");
var long = execution.getVariable("Longitude");
'{"q":"SELECT name, number FROM montreal_boroughs WHERE ST_Intersects(montreal_boroughs.the_geom,CDB_LatLng(' + lat + ',' + long + '))"}';
Response was inline Javascript that parsed as: S(response).prop("rows").elements().get(0).prop("number").numberValue();
(in this example did not need to provide any error handling)
If you have better implementation suggestions, happy to receive.