The id parameter for a flow makes it a bit obscure to understand what the functionality of the flow's functionality is.
Since JSON is not that user-friendly to read when one does HTTP GET /flows extracting the individual id of flow is a hassle when nodered is running on different devices.
And in order to use HTTP GET /flow/:id the value needs to be at the user's disposal a-priori.
Is there some better way to add a bit more semantic information from the running flows on multiple nodered instances.
If the flows can be named in the editor why can't the API be used to query the unique names of the flow as opposed to having the id as a parameter?
