# Feature request - use link nodes in subflows

**URL:** <https://discourse.nodered.org/t/feature-request-use-link-nodes-in-subflows/20054>\
**Category:** Feature Requests\
**Created:** [8 January 2020 13:28 UTC](https://discourse.nodered.org/t/feature-request-use-link-nodes-in-subflows/20054 "2020-01-08T13:28:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![molesworth](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/molesworth/32/11748_2.png) [@molesworth](https://discourse.nodered.org/u/molesworth)\
**Post date:** [8 January 2020 13:28 UTC](https://discourse.nodered.org/t/feature-request-use-link-nodes-in-subflows/20054/1 "2020-01-08T13:28:46Z")

</div>

... or at least link-in nodes.

As part of my system design I distribute several useful "events" via link nodes, such as system startup, regular timestamps, email received etc. In many cases, particularly with the startup event, these are fed into subflows, and while tidying up my flows I realised it would be neater if the incoming links were inside the subflow, to reduce clutter and save checking the incoming message.

I've not looked into the code, but I realise there are likely good reasons why link nodes aren't allowed in subflows, such as the inability to specify different connections on a per-instance basis. However, if it was limited to a "static" or "const" connection, then it might make it simpler to implement.

It's probably not a high priority, but I'd be interested to hear any thoughts on the possibility of implementing this.

---

<div class="post-metadata">

**Author:** ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)\
**Post date:** [27 March 2022 15:33 UTC](https://discourse.nodered.org/t/feature-request-use-link-nodes-in-subflows/20054/2 "2022-03-27T15:33:59Z")

</div>

I have found this:

> **[node-red-contrib-sub-link](https://flows.nodered.org/node/node-red-contrib-sub-link)**
>
> Link messages between Subflows

Works for me perfectly.