@qateam sorry for multiple posts. I’ve just reviewed this and whilst it is helpful for getting some information about what action was triggered it doesn’t actually tell you which key was pressed. So for example if you are on a New Message screen and you are waiting for a trigger that could be any number of key combinations then ideally you just want to know which combination was pressed so that you can program the workflow accordingly.
I just tried using parallels but this doesn’t seem to work particularly well and also means that you have to use multiple event trigger activities and update all of them whenever something needs changing.
Feel like I am missing something simple here…In simple terms what I am looking for is a more generic listener i.e. some keys were pressed --> check what keys they were --> ok now do action 3 outside of the monitor events sequence based on those keys.