Webhook URL or environment detection in scenario

[TimePaste.com]

I need my scenario to use the webhook URL that triggered it, but the “url” property passed when the webhook node is triggered is empty.

Alternatively, I could enter both dev/prod URLs of the webhook trigger node if the scenario can detect whether it is running as DEV or PROD. Is there an environment variable within the scenario?

[TimePaste.com]

Perhaps the question is unclear. Here is an attempt to clarify.

1. When the webhook triggers the scenario, the expectation is to receive the webhook’s URL in the data (in a property called “url”), but this property is coming through as “http://”. The webhook URL is not listed in the property.
2. Is there a way for the scenario to detect whether it’s running in a development environment or production environment.

[Raian]

Hi! We’ve identified this bug, and it will be fixed. Could you share why this issue is so critical for you? By default, most automations primarily run in production, since dev environments typically exist only for development purposes. Personally, I don’t see this as a major issue—but I could be wrong.

Please let me know your thoughts! Thanks!

[TimePaste.com]

Oauth2 flows require a redirect URI. Being able to dynamically pass this as a parameter rather than hard coding it or using JavaScript hacks allows reliable and consistent use of both the development and production URLs. Without it, one environment or the other is purposeless.