# Is there a better way to use the flow ID when it comes to having larger number of nodered instances?

**URL:** <https://discourse.nodered.org/t/is-there-a-better-way-to-use-the-flow-id-when-it-comes-to-having-larger-number-of-nodered-instances/78203>\
**Category:** General\
**Created:** [5 May 2023 08:22 UTC](https://discourse.nodered.org/t/is-there-a-better-way-to-use-the-flow-id-when-it-comes-to-having-larger-number-of-nodered-instances/78203 "2023-05-05T08:22:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shan](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@Shan](https://discourse.nodered.org/u/Shan)\
**Post date:** [5 May 2023 08:22 UTC](https://discourse.nodered.org/t/is-there-a-better-way-to-use-the-flow-id-when-it-comes-to-having-larger-number-of-nodered-instances/78203/1 "2023-05-05T08:22:24Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [4 July 2023 08:23 UTC](https://discourse.nodered.org/t/is-there-a-better-way-to-use-the-flow-id-when-it-comes-to-having-larger-number-of-nodered-instances/78203/2 "2023-07-04T08:23:24Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.