Skip to main content
Workflow runtime channels let an integration choose which deployed workflow service executes a triggered run. The channel is transport-level routing metadata, so it is supplied as an HTTP header rather than as part of the workflow input.

Available Channels

To select the stable channel:
Only the exact values current and stable are accepted.

Trigger a Stable Run

Add the channel header to POST /trigger-template. The JSON request body does not change.

Response

The response body retains the normal trigger contract:
The response header reports the channel applied to the run:
The selected channel is stored with the trigger. You do not need to resend the channel header when polling GET /workflow-results/{triggerId}.

Invalid Channels

An unsupported or empty channel returns 400 Bad Request. The run is not stored or dispatched.
Do not send workflowChannel in the JSON body. Body fields are reserved for workflow input and per-run configuration; use the Overlap-Workflow-Channel header for routing.