It's a slightly different angle, but we have the very similar automations (based on the examples from the From Actions to Impact; Measuring Self-Service ROI in Port webinar) - each triggered by the running of a different self-service action. Of the four pictured, three are identical except for the title/identifier (wouldn't need them to be) and the specific action run that triggers them. The fourth has the same differences, plus some deviations in the values used in the invocation payload mapping (though these differences could be accounted for with conditional logic in the mapping, based on the triggering action). In at least three of the four cases, being able to multi-select the triggering action would significantly reduce duplication/future maintenance overhead - and like I laid out, a little extra logical complexity within the mapping could conceivably consolidate all four into one automation.