# Cross references to other flow nodes in documentation

**URL:** <https://discourse.nodered.org/t/cross-references-to-other-flow-nodes-in-documentation/101504>\
**Category:** General\
**Created:** [21 July 2026 07:40 UTC](https://discourse.nodered.org/t/cross-references-to-other-flow-nodes-in-documentation/101504 "2026-07-21T07:40:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [21 July 2026 08:36 UTC](https://discourse.nodered.org/t/cross-references-to-other-flow-nodes-in-documentation/101504/3 "2026-07-21T08:36:29Z")

</div>

Thanks for the detailed answer 👍

> [@Steve-Mcl](#):
>
> It would be far better to be a core feature

Definitely.

On the other hand doing something like we did with the [groupflow](https://discourse.nodered.org/t/async-multiple-input-for-nodes/101476) plugin, i.e. having a plugin demonstrate the feature which then can be used in the meantime is probably the golden middle road.

I'm pretty sure that something like the groupflow will - eventually - make it into core. Having a plugin to test the feature and add suggestions before then is really useful.

> [@Steve-Mcl](#):
>
> we do something similar in FlowFuse

Can I ask does FlowFuse parse the url and to determine what functionality is to be called? I.e. could I add something like `[Name](#search/search%20term)` so that I can trigger the `RED.search.open("search term")` functionality?

I know that extending the markdown rendered isn't rocket science, just whether that is possible via a plugin remains a mystery to me.

> [@Steve-Mcl](#):
>
> [see function 2](http://\<ip\>/#node/55820643ea60d8cd)

I think this isn't a good idea for portability 😉 - hardcoding both the IP and node id means that importing the flow somewhere else will probably break the documentation ....

> [@Steve-Mcl](#):
>
> The reason onclick gets removed is due to dom sanitizer.

`onclick` is definitely no solution. I totally forgot to use markdown notation (because I started with onclick), so having `[..](#<function>/<arg>)` convention for markdown links would be the way to go...

Cheers!

---

_[View the full topic](https://discourse.nodered.org/t/cross-references-to-other-flow-nodes-in-documentation/101504)._