Categories & collections

the folder list on the left side of the dashboard is repurposed to represent categories and collections of templates individual templates consisting of a single automation can be placed into a category that can be searched in the templates catalog docid\ xv6afgpikxsycrj xoa9s a collection is a single template that consists of multiple automations that can be installed as a single group to define a template collection, create a folder with a name that starts with "collection " then place the automations comprising the collection into the folder in the templates catalog docid\ xv6afgpikxsycrj xoa9s the catalog entry is defined by a placeholder automation in the collection whose name begins with "collection " this automation only serves the purpose of being the one whose name appears in the catalog and whose catalog description appears here observe that the name above comes from the name of #12157 and that the description above comes from that placeholder's catalog description note that in the dashboard there are 4 templates set to public but the catalog says the template consists of 3 automations this is correct, b/c #12157 is not an automation template but just a catalog placeholder the placeholder is not installed with the collection in order to create the placeholder template, build an automation consisting of a no op trigger and any action whatever is build doesn't matter, since the implementation is never installed or used templates set to private within a collection are also installed like in the above example, these are generally utility or run once automations used to configure the collection the purpose of setting them private is just so they don't appear in the templates catalog docid\ xv6afgpikxsycrj xoa9s and cause confusion