Hey @knowlec -
Defaulting back to plain text is an indication that we fail to parse the response into the desired format. In this case, it looks like influx is returning CSV data (much like this example). This appears to be the Annotated CSV format.
This appears to be the only format that influx supports.
Short of adding some sort of middleware that is parsing this payload into a more standard json or xml format, I don’t think there is a good path to be able to ingest this data into Tulip today. I will add a feature request for us to evaluate adding support for this as a response decoding type.
Pete
ninja edit - it does look like the v1 endpoint supports json response type, and that should be compatible with Tulip