DeviceID in HTTP Connector Header

Octave
1

Is it posible to pass the DeviceId or a defined value from the triggering event in the HTTP Connector header as “x-custom”

if not is it possible to pass the value in the URL as a query parameter on a POST to a web hook

My intention is to have 1 web hook that can gather sensor events form a number of devices but I need to manage them individually.

From the documentation it seems that the Header Parameters have to be fixed in the script and so is the URL

2

HTTP connectors currently can only have a dynamic URL and/or dynamic payload. You can use any data from the triggering event in the routingScript (to include as a URL query parameter) or js properties of the connector (to include in the body).

1 Like