create many HTTP triggers

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 triggered

The URL route path that will trigger this endpoint (e.g., 'api/myendpoint'). Must NOT start with a /.

If true, the route includes the workspace ID in the path

Short summary describing the purpose of this trigger

Detailed description of what this trigger does

True if script_path points to a flow, false if it points to a script

Path to the resource containing authentication configuration (for api_key, basic_http, custom_script, signature methods)

Deprecated, use request_type instead

If true, serves static files from S3/storage instead of running a script

If true, wraps the request body in a 'body' parameter

job trigger mode

If true, passes the request body as a raw string instead of parsing as JSON

Path to a script or flow to run when the triggered job fails

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.