Websocket with a dynamic Autharization header

[TotallyInformation]

BTW, just seen my reply here:

Setting Websocket Headers dynamically

So I think you will need to do something like watching for the connection error, using a catch node, using that to trigger a flow to regen the token which you capture to a flow context variable. Hmm, but then you would have to restart the websocket and not sure how to do that. Actual environment variables are only read when Node-RED starts. However, Node-RED has extended the idea of env variables and allows you to set them in its tabs, groups and sub-flows. I've not tried this but perhaps hav…

Might give you a work-around.