Automation assignment actions can now spread work across a group of candidates: config.assignment_type accepts the new sequential and even_distribution values, together with new optional config.candidate_group, config.fallback, config.fallback_assignees, and config.reset_interval fields — accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows and executions are read
Assignment actions additionally accept a new optional config.workload_filter for narrowing which existing workload is counted when picking an assignee
New EventCatalogTrigger trigger type (event_catalog) added for starting flows from Event Catalog events — configured with event_name, a pinned event_version, the entity_node_id and entity_schema of the entity the execution runs on, and an optional ignore_automation_triggered flag (default true); accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever triggers are read
Executions started by an Event Catalog event carry a new trigger_event variant of type event_catalog with event_id, event_name, event_version, published_version, entity_node_id, and a payload_ref to the stored event payload — returned by the execution list, read, search, and POST /v1/automation/public/executions:resume endpoints
Action conditions accept a new source.originType value event for reading the condition operand from the trigger's event payload (attribute is then a dot path into the payload)
New optional trigger_event_name query parameter added to GET /v1/automation/flows for listing flows that have an event_catalog trigger for a given event