Hello Tulip Team and esteemed community members 
,
Working with HTTP connectors and interpreting the structure of various APIs has been both rewarding and, at times, a bit of a puzzle 
. We often bump into intricate nested objects, arrays, and arrays of objects in API results. This complexity can make data processing in connector functions quite the challenge.
Recently, I’ve delved into JSONata, a proficient query and transformation tool for JSON 
. Its prowess in effortlessly flattening complex JSON structures is commendable. By integrating JSONata’s transformative abilities into Tulip, we could potentially unlock a more streamlined approach to handle these JSON outputs 
.
Imagine a feature where we could seamlessly slot a JSONata transformation between the connector response and the JSON query. And, to sweeten the deal, what if we could auto-generate the function’s output structure based on the transformed JSON? That would be quite the enhancement 
.
Such an integration could substantially boost the efficiency and flexibility of our connector functions. I genuinely believe it would be a golden addition to Tulip’s repertoire 
.
Thank you for considering (or not) this suggestion, and I’m excited for the future advancements in the platform 
.