Current behavior: The outbound webhook payload does not include the pipeline parameters that were passed when the pipeline was triggered.

Requested: Include pipeline parameters in the workflow-completed and job-completed webhook payloads, so consumers can use them for filtering and routing without custom parsing logic.

Use case: Teams that run one workflow in multiple variations via pipeline parameters (e.g. action=build vs action=release) have no way to differentiate those runs in webhook events today. Including the parameters in the payload would allow downstream systems to filter or route events based on parameter values — eliminating the need to build custom gateway-level parsing logic.