Automation flows can now be triggered by relation changes: trigger operation types accept the new relationsAdded, relationsRemoved, relationsDeleted, relationsSoftDeleted, and relationsRestored values on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id}, and executions report them in trigger_event.operation_type
Automation actions can now wait for a journey submission through new optional config.journey_id and config.wait_for_journey_submission fields, accepted when creating or updating a flow and returned wherever flows and executions are read; a waiting execution additionally reports a workflow_wait_context
Executions started from a workflow now report who triggered it through a new optional workflow_context.trigger_user_id field, accepted on POST /v1/automation/executions and returned wherever executions are read