rusenask
commented
5 years ago Hi, glad to hear it's useful for you!
Regarding nodes and separate connections - yes, each node will create a websocket but it's okay, they are very lightweight and even having several open will never approach the amount of data passed when you open a typical web page :)
In my workflows I have several webhookrelay nodes always active. I also use "switch" node to separate incoming webhooks based on their webhookrelay bucket names:
Then, based on topic/bucket name you divert flow into a nodes that decode different JSON structures.
You can also detect which input received it by inspecting payload.meta.input_name field:
Does this sound helpful to you? I imagine that for a second flow you can either inspect the bucket or input names, that should be enough :) Also, you can also check request headers, usually they are different when dispatched by multiple separate applications.
hepcat72
First, thanks for webhookrelay. I really like it. I'm using it for personal/home automation.
I have a question and a possible feature request.
First, if I include a webhookrelay node connected to the same public endpoint in 2 different node-red flows, are 2 separate websockets maintained or is one socket per endpoint maintained? I'm just curious if there's more overhead in terms of sockets if I put a webhookrelay node using the same endpoint in different flows.
I set up my first flow which I call automatically from an app on my phone based on location. It has an immutable JSON structure. I can change a value or 2, but not the variable names. I'm planning on creating another flow that gets its webhook POSTs from a different source. If I set up a second flow which uses the same webhookrelay endpoint but is called from a different source (e.g. IFTTT) and has a different JSON file structure, is it possible to inject a variable into the JSON based on where the webhook is coming from?