# \[LINK OUT & LINK CALL\] Trace Link origin

**URL:** <https://discourse.nodered.org/t/link-out-link-call-trace-link-origin/86066>\
**Category:** Feature Requests\
**Created:** [1 March 2024 19:32 UTC](https://discourse.nodered.org/t/link-out-link-call-trace-link-origin/86066 "2024-03-01T19:32:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SynoUser-NL](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/synouser-nl/32/85195_2.png) [@SynoUser-NL](https://discourse.nodered.org/u/SynoUser-NL)\
**Post date:** [1 March 2024 19:32 UTC](https://discourse.nodered.org/t/link-out-link-call-trace-link-origin/86066/1 "2024-03-01T19:32:18Z")

</div>

When using many LINK nodes, it is more and more difficult to know which Link-OUT or Link-CALL sent a message to a Link-IN node. Especially if a Link-IN can be called from multiple OUT's or CALL's.  
To be able to trace where a message to a Link-IN came from, I suggest adding an option to the Link-OUT and Link-CALL nodes to send the name of the link (and this must then not be empty) as a fixed message property.

Something like:  
[boolean] Option: Add Origin to Message  
which would then generate a property: \_linkOrigin {name of link node}

Link-IN nodes would not need to do anything with the property, but this would make debugging a lot easier!

I'm not sure where the right place to ask is, but I would also like to know the status of an earlier FR:

> [@\[LINK OUT & LINK CALL\] Usability Requests](https://discourse.nodered.org/t/link-out-link-call-usability-requests/83361):
>
> I'd like to request a change to both the LINK OUT & LINK CALL nodes: (Add the possibility to) Display the available links in alphabetical order. Currently, available LINK IN's are displayed in the order they are created. Having them available alphabetically would make searching for a specific LINK much easier. Especially if you follow some type of name convention for LINKs. Add the option to display only the currently checked conneections. Rather than having to scroll through the list o…

Thanks! DenW

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [1 March 2024 20:12 UTC](https://discourse.nodered.org/t/link-out-link-call-trace-link-origin/86066/2 "2024-03-01T20:12:40Z")

</div>

Messages originating from a link call have special properties in the msg object you can interrogate (use a debug set to show full message)

For link out nodes triggering a link in, there is nothing stopping you adding something to the msg (like msg.source) - that's what I do 🤷‍♂️

Edit:

Ps, I don't disagree with the benefits for debugging purposes. I just wanted to state this is possible today.

---

<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:** [30 April 2024 20:13 UTC](https://discourse.nodered.org/t/link-out-link-call-trace-link-origin/86066/3 "2024-04-30T20:13:02Z")

</div>

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