The local calendar has so much potential. But creating an automation triggered simply by a calendar event’s summary attribute is too cumbersome. This is because the only attribute triggers currently implemented are Event start and Event end (with offsets).
Instead, as discussed here, Calendar triggers should include more attributes (e.g. summary, location, categories, and really any field currently or in the future available in a Calendar event).
As currently implemented, I have to template* out these attributes to then sort through them in a Choose action triggered by Event start or Event end. This seems like 3 unnecessary levels which could be reduced down to 1-2 if I could specify a discrete summary string in the trigger and assign it a Trigger ID for use in an action like I do with most of my other branched automations. Plus, it just seems inefficient to have an automation run farther down the logic path every time an event starts or ends on a calendar even if the automation should not have been triggered to begin with.
*Templating should not be required at all for a UI based automation config flow intended to simply trigger off specific events on a calendar. To the average user, jumping in and triggering off a specific event seems uncomplicated, but templating is a more advanced capability that should not be expected of them (or anyone really given the recent efforts to simplify the UI). They (we) should be able to simply put a value in a text field.