Webhook Trigger Does Not Display Endpoint URL

📙┃Bug Reports
1

The Webhook trigger step does not display the endpoint URL anywhere in the UI. Without a visible webhook URL, users cannot determine where to send requests to trigger the workflow. This prevents testing and integration with external services that rely on the webhook endpoint.

Steps to Reproduce:

  1. Add a Webhook trigger step to a workflow.

  2. Configure or open the step settings.

  3. Look for the webhook endpoint URL to send requests to.

Expected Result:
The UI should display a clear webhook URL that can be copied and used to send HTTP requests to trigger the workflow.

Actual Result:
No webhook URL is displayed in the step interface, leaving users unable to identify the endpoint for triggering the workflow.

Extra Detail:
Here’s a Jam link for this issue:

2

We will resolve this in next week’s release. :+1:t3: