Nodes
Each node displays key information such as the node name, the ID, the node type, whether it is a Frontend (FE) or Backend (BE) node, and provides controls to resize the node. Each of these elements is described in the following sections.
Node components
Node name
The Node Name is the label displayed on top of the node. It can be changed by opening the node and clicking the edit pencil icon in the top-right corner, allowing you to better describe the node's purpose within the flow and improve readability.
Node type
Indicates the node type (e.g., Frontend Form, Backend Script, Condition, etc.). The node type determines what function the node performs within the flow.
Node ID
The Node ID is a unique identifier for the node within the flow. It represents the ID used to store the node in the database. The node ID is auto-generated and cannot be changed.
Node execution (FE/BE)
Indicates whether the node is a Frontend (FE) or Backend (BE) node, depending on where the node logic is executed:
-
Frontend (FE): Executes in the user's browser, typically for displaying UI or collecting user input
-
Backend (BE): Executes on the server, typically for processing logic or API calls
Resize node
Using the Resize icon, the node can be minimized or expanded to improve readability and workspace organization. This is particularly useful when working with complex flows containing many nodes.
Input and output
Each node has its inputs on the left side and its outputs on the right side, which define how the flow enters and exits the node.
Inputs
-
Located on the left side of the node
-
Receive the execution flow from previous nodes
-
Accept data from the flow context
-
Typically one input per node
Outputs
-
Located on the right side of the node
-
Direct the flow to the next nodes
-
Can have multiple outputs (Success, Failure, etc.)
-
Each output represents a possible execution path
Node configuration
Each node can be configured by clicking on it. The configuration panel includes:
-
General Settings: Name, description, and basic parameters
-
Input Configuration: How the node receives and processes data
-
Output Configuration: How the node produces results and routes to next nodes
-
Variable Management: Variables the node reads from or writes to the flow context
Node states
Nodes can be in different states:
-
Not Connected: Node is on the canvas but not connected to the flow
-
Connected: Node is properly connected with inputs and outputs
-
Active: Node is part of an active flow
-
Error: Node has configuration errors (shown with visual indicators)
Best practices
-
Use descriptive names: Change the default node name to describe its specific purpose
-
Organize visually: Use the resize function to keep important nodes visible
-
Connect all outputs: Ensure every output connector leads somewhere
-
Test configurations: Verify node settings before activating the flow
