create websocket trigger
Path parameters
Request body
The unique Windmill path for this trigger. Must be of the form u/<user>/<path> or f/<folder>/<path>. This is the trigger object path, not the HTTP route path.
Path to the script or flow to execute when a message is received
True if script_path points to a flow, false if it points to a script
The WebSocket URL to connect to (can be a static URL or computed by a runnable)
job trigger mode
Logic to apply when evaluating the top-level filters. 'and' requires all of them to match, 'or' requires any of them to match. Nested any_of/all_of/none_of groups carry their own logic.
The arguments to pass to the script or flow
If true, the script can return a message to send back through the WebSocket
If true, error results are sent back through the WebSocket
Path to a script to run when the triggered job fails. A bare path, without the script/ or flow/ prefix a schedule error handler takes; it cannot be a flow.
The arguments to pass to the script or flow
The user or group this trigger runs as. Used during deployment to preserve the original trigger owner.
When true and the caller is a member of the 'wm_deployers' group, preserves the original permissioned_as value instead of overwriting it.
Response
websocket trigger created