# UDP/TCP input nodes **URL:** \ **Category:** Feature Request\ **Created:** [December 13, 2018, 5:45pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311 "2018-12-13T17:45:32Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\ **Post date:** [December 13, 2018, 5:45pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/1 "2018-12-13T17:45:32Z")
Requesting UDP and TCP input nodes for the workflows, similar to node-red. This would allow more direct support of non-mqtt based hardware telematics devices. ---
**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\ **Post date:** [December 13, 2018, 6:36pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/2 "2018-12-13T18:36:45Z")
Edge Workflows do provide a [UDP Trigger](https://docs.losant.com/workflows/triggers/udp/). TCP is not yet available for the edge, but it’s something we’ll likely be offering in the future. Offering these in Application (cloud) Workflows is an interesting challenge that we’ve been investigating for quite a while. Node-RED and our Edge Agent run on your own gateway, so exposing TCP and UDP ports is straightforward. Because UDP and TCP require a dedicated IP and port for each and every application and user, providing that in a scaleable and highly available way in the cloud is the challenge. ---
**Author:** ![Tim\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Tim\_Hoffman](https://forums.losant.com/u/Tim_Hoffman)\ **Post date:** [December 13, 2018, 11:54pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/3 "2018-12-13T23:54:16Z")
Hi Brendon Speaking of edge node triggers 😉 Any signs of the redis subscribe capability on edge ? T ---
**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\ **Post date:** [December 16, 2018, 7:32pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/4 "2018-12-16T19:32:25Z")
Well, Another way around that might be too have the Losant Edge Agent on to our own instance of EC2 or other cloud server. I know this is possible with node-red, but I am not sure for the Losant edge. Do you think that is possible @Brandon_Cannaday? ---
**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\ **Post date:** [December 19, 2018, 12:26am UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/5 "2018-12-19T00:26:28Z")
It is absolutely possible and something we’ve done internally. The Edge Agent doesn’t really care if it’s running on a Linux gateway or a Linux VM in the cloud. ---
**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\ **Post date:** [August 29, 2019, 9:16pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/6 "2019-08-29T21:16:10Z")
Wondering if there was any further consideration to doing a TCP node for the Edge? ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [August 30, 2019, 2:37pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/8 "2019-08-30T14:37:26Z")
Hi @paul_wareham, I know there has been some discussion about the functionality, but I do not know it’s current state or if it was selected for development. I will give a +1 to this feature request, and communicate your interest! I will keep you updated on it’s status as well 😄 Thanks, Julia ---
**Author:** ![emcdee](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/emcdee/32/4313_2.png) [@emcdee](https://forums.losant.com/u/emcdee)\ **Post date:** [June 5, 2023, 8:24pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/10 "2023-06-05T20:24:50Z")
Bump, kindly. Thanks ---
**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\ **Post date:** [June 5, 2023, 11:11pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/11 "2023-06-05T23:11:27Z")
Hey @emcdee, I’d like to know more about your TCP protocol. UDP works because messages are divided into datagrams, which is easy to map to individual workflow triggers. A TCP stream is not so easy to automatically delineate. For example, the Node-RED TCP options are designed to support messages separated by newlines or carriage returns, which could be something we can support. ---
**Author:** ![emcdee](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/emcdee/32/4313_2.png) [@emcdee](https://forums.losant.com/u/emcdee)\ **Post date:** [June 6, 2023, 10:45am UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/12 "2023-06-06T10:45:38Z")
That would be great - cr/lf separated messages like in a terminal emulator. ---
**Author:** ![emcdee](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/emcdee/32/4313_2.png) [@emcdee](https://forums.losant.com/u/emcdee)\ **Post date:** [June 6, 2023, 5:55pm UTC](https://forums.losant.com/t/udp-tcp-input-nodes/1311/13 "2023-06-06T17:55:23Z")
Such that you could send simply send/receive ascii via an MQTT node or something on edge workflow.