# Tulip Tags new features feedback

**URL:** <https://community.tulip.co/t/tulip-tags-new-features-feedback/6220>\
**Category:** Product Suggestions\
**Created:** [August 31, 2022, 2:49am UTC](https://community.tulip.co/t/tulip-tags-new-features-feedback/6220 "2022-08-31T02:49:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![youri.regnaud](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/youri.regnaud/32/2917_2.png) [@youri.regnaud](https://community.tulip.co/u/youri.regnaud)\
**Post date:** [August 31, 2022, 2:49am UTC](https://community.tulip.co/t/tulip-tags-new-features-feedback/6220/1 "2022-08-31T02:49:46Z")

</div>

Tulip machine tags features [How to Send Data to Machines from Edge Devices using Node-RED and Tulip Tags | Tulip Knowledge Base - Support for Building Operations Apps](https://support.tulip.co/en/articles/6473639-how-to-send-data-to-machines-from-edge-devices-using-node-red-and-tulip-tags) is a great feature on the “edge-driven” journey. Some feedback about the first version.

- The use of a single tag list is quite restrictive. Indeed, if several devices are connected to a gateway, the tag list corresponds to the concatenation of the tags of several devices. Having a tag list by equipment seems to me simpler because in the end users want to connect an equipment not a gateway
- When you have a machine with hundreds of tags the creation of the tag list is a bit painful. Be able to create the tag list via a node property that can be driven by the message (msg.payload…) can be great.
- I’m looking forward to the OS51 version to send data in multiple tags.