Events, Workflow
The full Add Action catalog behind every event, grouped by purpose, and what the runtime actually supports.
What the workflow does
An event decides when something happens. Its workflow decides what happens next: an ordered list of actions that runs top to bottom.
Add an action
Choose Add Action on an event's workflow to pick a step. Actions are grouped by purpose:
Every other action in this catalog has a matching handler in the platform's workflow engine. call_ai_agent and call_triage_agent don't: they don't appear anywhere in the runtime checker or engine, only in Studio's own Add Action menu. A workflow step built from either one currently won't do anything when it runs.
alter_ui_element, create_ui_element, info_ui_element, remove_ui_element, empty_ui_element, cache_ui_element and load_ui_element are hard validation errors today. Drive UI changes through fields plus a bound expression or visibility attribute instead of imperative element manipulation.
Order, conditions, and async
Actions run top to bottom. Two things change that:
Right-click an action for its context menu: Delete, Copy and Paste to duplicate or move a step, Parameters to pass values into the called event or program, Condition, Open in new tab to inspect the called target, Async, and Watch to add the step to the project's watchers.
Use the checkbox on an action row to disable it temporarily, useful for testing a workflow one step at a time without deleting anything.