List the events an automation can trigger on

Every event an automation can be built on, and what a condition may ask about under each. Any credential that reaches a newsletter can read it: it describes Commune's event vocabulary rather than anybody's data.

Every topic Commune publishes is a trigger, including the ones that are not about a subscriber. carries_subscriber says which, and it carries three facts at once: a trigger without a subscriber cannot send an email, cannot move a tag, and cannot be asked anything about a person.

Read this before writing a condition. context lists the property names a condition may use, per branch. That matters because of one asymmetry in JSON Schema: an absent property says nothing, so a condition about a property no payload carries matches every run and the branch silently always takes the same arm. Saving such a condition is refused, naming the path, and this is the list that refusal is computed from.