I can imagine that.
After some painful discovery, I came up with an approach that is not perfect - but it works.
1) I have a field called “Workflow trigger” and the idea is that you can insert any value in that field and that will trigger automations. At the end of the automation you clear the value from the field, making it possible to store another value in there and trigger other workflows.
2) I use this field to append values to a “multiple choice” field. So for example, I have a list of campaigs and events in one multiple choice property. And then when a person downloads “Report A” i trigger a workflow that appends “Report A” into the field.
The end result behaves very much like tagging, but is obviously more cumbersome to work with and to modify. But when I built it once, it works in practice and its easy to expand as all of my workflow triggers are stored in one workflow.