Tulip has never been able to natively parse JSON. It always requires using a Connector function, a Custom Widget, or some extremely precise string parsing if your structure is consistent. I am sure that Pete and Pete from the product team are well aware of this and I would expect JSON parsing to be possible in Automations at some point. It might look something like the new UI when you map MQTT attributes. XML less likely.
Alternatively, if Custom Expressions ever become a thing… there are infinite possibilities. JSON, XML, SOAP, YAML, etc. And the Tulip ecosystem can grow exponentially instead of waiting for feature requests. Just my 2 cents.