Anatomy of a Node
Last updated
Was this helpful?
Last updated
Was this helpful?
A node defines a collection of instructions for the Flow Controller. By connecting multiple nodes together, you can program the behavior of your site.
Let's take a look at a node, and break down it's parts. We'll look at a Middleware node, as it has all parts that can be included with a node, but be aware that not all nodes will have every part.
This entire element is refered to as the Node.
The icon represents the type of node.
Here are the icons, and what type of node they represent.
Lightning Bolt
Listener
Asterisk (Yellow)
Middleware
Field
Value
Antenna
Broadcaster
Asterisk (Red)
About
The Title provides a high level name for the Node.
If the Node is associated with a Module type, it will also be displayed here. For example:
The description provides a brief explanation of what the node does when pressurized.
A Node can have a number of Inputs. These inputs provide data that the Node can use in its function.
In this Equals example, there are two inputs A, and B, it checks if the value passed into both inputs are the same.
Nodes can also be Pressurized through an input, alongside data. For more information, see Connecting Nodes.
A Node can have a number of outputs. These outputs provide data and pressure to the next Node in the Flow.
In this Equals example, if both inputs where equal (say we passed 1 to both A and B), the Equal output would be pressurized. If both inputs where not equal, (say we passed 1 to A, and 3 to B ), the Not Equal would be pressurized.
Data can also be passed alongside pressure through the outputs of a Node. For more information, see Passing Data.
