docs(automation): Event Catalog trigger - #150
Open
karlrank wants to merge 2 commits into
Open
Conversation
karlrank
force-pushed
the
docs/automation-event-catalog-trigger
branch
from
September 9, 2026 17:53
356dd74 to
fb5b35c
Compare
added 2 commits
September 14, 2026 14:24
New page covering configuration (event, pinned version, entity node, ignore switch), event data in conditions/templates/webhooks, version pinning and loop prevention; cross-links from Core Events and the automation overview; changelog entry.
karlrank
force-pushed
the
docs/automation-event-catalog-trigger
branch
from
September 14, 2026 11:25
fb5b35c to
d928cb5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Dev Center documentation for the new Event Catalog automation trigger.
docs/automation/event-catalog-trigger.md: configuration (event, pinned version, entity node, ignore switch), event data in trigger/action conditions,{{event.<path>}}template variables (email + document), webhook/custom-actioneventobject, version pinning, loop prevention (each guard attributed to the loop class it stops, worked example, sequence diagram with_automation_chainboth ways), limitations, and a note that published custom events can start automations (drafts/deprecated cannot).Build passes. Rebased onto main. Review items: the "Core Events" setting label, the hand-written
CHANGELOG.mdentry (CI may generate one from the spec diff), and the sentence mentioning oversized payloads being fetched from storage.Related MRs (Event Catalog → automation trigger)
Already merged: event-catalog-api (
_automation_chainpassthrough) and automation-workers (incl.@epilot/automation-shared2.5.0, published and consumed). Remaining deploy order: svc-webhooks → automation-api → root-config translations → UIs.