calling a webtrigger works just fine, but, unfortunately, the original query string of the request can’t be found neither in the path property nor somewhere else in the request object passed to the webtrigger function.
Unfortunately, the web request going to the webtrigger is issued by a third party in response to an OAuth2 request for an authorization_code, as part of a server-to-server authorization flow. There, you get a query string, not a request body.
Is there any chance this could soon be added to webtrigger functionality?
If not, is there another way to implement it in Forge?
Otherwise, we would have to turn away from Forge - not good.