We would like to request an enhancement to the default webhook payload for the "Waiting for User Action" event in Harness.

Currently, when a pipeline triggers a "Waiting for User Action" event (e.g., when an approval step is pending), the default webhook payload does not include the name or identifier of the specific step that is awaiting user input.

Requested Enhancement: Please include the step name and/or step ID as part of the default webhook payload when a "Waiting for User Action" event is fired. This would allow downstream systems and integrations to easily identify which specific approval step requires attention.

Use Case: When pipelines contain multiple approval steps, receiving the step name/ID in the webhook payload would enable teams to route notifications more effectively.