This is a request for ability to access the headers portion of the received POST request (and not just "data" payload) when receiving to an Incoming Webhook automation rule. 

Further details on use case:

Interested in accessing anything identifying the “client” here:

• Origin
• Referrer
• User-Agent

But the ability to even map any incoming headers to variables would be a better solution so as to facilitate custom headers from services.

The context, is as explained “this challenge…needs to be passed back to monday with the same address the webhook was sent…”

To clarify: In our case, Monday.com send a request to our webhook with a string value representing a challenge in the JSON payload provided, which we must POST back to them in order to satisfy this method of validating ownership of the endpoint.

While we can get the challenge data from the payload, we cannot get the Origin of the request to make the required return call to the inbound request.