One thing I've noticed with the new UI is that, when I refresh it, it doesn't seem to remember which mode (test vs prod) I'm looking at. It would be nice if it would remember so I wouldn't have to keep going into the settings widget and re-selecting test mode.

Having spent time in the Automations, I got the hang of it, and was suitably impressed. It would be nice if a node existed for the purpose of event mutation. While it is true that one can map any given attribute of data, regardless of the original format, it becomes readily apparent that it is wildly easier and more convenient to simply format non-nested data to the root data property in the original event payload. Were I not an engineer with both the access and capability to adjust the payload in this way, I'd much, much rather have an initial Automation, specific to whatever system I was sending an event from, that first mutated the data to a flattened spec, and then continued with a core automation for further processing.