NR - Flow "conventions"

General
1

As I become more familiar with NR, the number of flows I have is growing. I'm now at the point where a half-dozen of my flows need to send emails. I've been copying/pasting the email node into the new flows, the doing the configuration.

Today, I found out I need to make some email server config changes - and I'll be opening up all the flows, changing each config on the email nodes.

Surely there's a "GOSUB <flow.email_node>" style of functionality in NR. :slight_smile:

What's the typical convention? How does one, in proper NR style, call a node on another flow?
Or is it frowned upon? If allowed, would I have a dedicted Flow, say "Email" with only the email node in it?

Learning.
Thanks!

2

Hi @pconroy328

Use the link nodes (link in/out)
Link nodes creates invisible wireless between themself, and they can travel across different flows.

Have 1 link on the email flow, and place a link per other flow to it, that needs to send it a message.

If you need to return from the email flow (like a type of ack if you will) then extend the link nodes with the use of link call nodes.

Link call nodes, act like a subflow, but allow you to re-use portions of a flow in various areas - all whilst still having 1 instance of the logic behind it all.

But yes, link nodes is what you are looking for, so your need is fully supported.

3

link call is what you use for subroutine like behaviour