Nodes

Updated on March 21, 2023

Overview

Every Flow is made of nodes, and every node contains its unique logic. All nodes are located on the Node panel. Node settings depend on the node type and are available by clicking on the node.

How to use Node settings to build flow?

List of nodes that are available to add:

Node	Description	Settings
IN	Starting point of the flow. Only one is allowed.	Name — name of the node. The structures for the IN node are defined in the settings of the flow itself as Input structures. Several input structures can be specified, depending on the requirements.
OUT	The ending point of the flow. There can be one or more OUTs.	Name — name of the node. The structure for the OUT node is defined in the settings of the flow itself as an Output structure. Only one output structure can be specified, but it can be of any complexity, pre-created as a custom structure through the structure builder.
Assign	A container that is used to pass values to variables.	Name — name of the node. Parameters: Variable — add a variable that has already been created before. To select the necessary variable, the Variable selector is used. In this, the created local variables, incoming and outgoing data, and node variables are available. Assign — assign a specific value to the added variable. The Expression Editor is used to add and edit values. It can be either a specific value or an expression of any complexity using existing variables, as well as outgoing node data (node variables). There can be any number of variable-assign blocks, depending on the requirements.
IF	Logic branching block. Accepts a condition and returns a boolean value.	Name — name of the node. Parameters: Condition — add a condition that will determine the further progress of the flow. The Expression Editor is used to add and edit conditions. If the condition is met, then further execution will go along the ‘YES’ branch.
Switch	Branch block. Accepts a condition and returns a boolean value. Unlimited number of ways. Execute the first “true”.	Name — name of the node. Parameters: Label — name of the condition. Condition — add a condition that will determine the further progress of the flow. Unlike IF, there can be several branches here, further execution will follow the first branch that meets the specified condition. The Expression Editor is used to add and edit conditions. There can be any number of label-condition blocks, depending on the requirements.
Iterator	Loop block. Iterates over the entire array.	Name — name of the node. Parameters: List — add the list of entities that the Iterator should iterate over. The Expression Editor is used to add and edit a list. By connecting the outgoing arrow of the Iterator to the target node, where certain conditions will be checked, or certain values will be collected into a new structure for subsequent manipulations. There are no restrictions on the use of subsequent nodes or on the group of nodes involved in the iterator logic. An array is expected as input to the iterator. An iterator node must be cyclically connected to another node or group of nodes. In the node following the iterator, it becomes possible to work with the current element of the array.
Function Call	A call block for a built-in or user-created function.	Name — name of the node. Parameters: Function — add the function to be called. The set of required parameters depends on the selected function. To learn about the operation of the function and the set of required parameters and types of variables that the function takes as input, use the Function selector. To get to the Function Selector, click on See all in the drop-down list of the Function field. Outgoing data also depends on the selected function. Depending on the selected function, a new variable may appear, or the same object with a modified value may be returned. To learn more about all available functions see the Expression Editor section.
Connector	Get data from any external systems and services using REST or SOAP connectors. Possible to add cookies and headers, if required.	Name — name of the node. Parameters: Service — connect the REST/SOAP service to a node for execution in a flow. Services are available from the drop-down menu or through the Service selector. To get to the Service Selector, click See All in the drop-down menu of the Service field. The Service Selector displays the services of the REST and SOAP connectors. The set of required request and path parameters depends on the selected service. It is necessary to define certain variables according to the logic and the corresponding type. Outgoing data depends on the method, if it is a REST connector, and on the established output structure in the corresponding connector service. Cookies — If cookies are required to connect to the required remote service, you can set them here. The Expression Editor is used to add and edit cookies. It expects an array of cookies, the easiest way to pass values to it is to send it as input to the flow itself or assign values to the elements of the array using an iterator and the Assign node. To create an array of cookies, you must use the Structure Builder in the Structure Selector when assigning a type to a variable or property. Cookies are not a required parameter in the connector. Headers — If headers are required to connect to the required remote service, you can set them here. The Expression Editor is used to add and edit headers. It expects an array of headers. Use the same approach as cookies. To read more please review the Structure selector. Headers are not a required parameter in the connector.
dbConnector	Get data from external databases. Support PostgreSQL or MS SQL databases. Each node executes a selected query.	Name — name of the node. Parameters: Query — connect DB query to a node for execution in a flow. Queries are available from the drop-down menu or through the Query selector. To get to the Query Selector, click See All in the drop-down menu of the Query field. The Query Selector displays the queries of the DB connectors. The set of required parameters depends on the selected query. It is necessary to define certain variables according to the logic and the corresponding type. Outgoing data depends on the established output structure in the corresponding connector query.
Subflow	An entry point to an additional flow. Returns the result of an additional flow.	Name — name of the node. Parameters: Flow — add a flow that you will use. The set of required inputs depends on the selected flow as an output.
Raise Exception	Raises the specific exception. Flow can contain more than one Raise Exception node.	Name — name of the node. Parameters: Exception — select the required Exception, if necessary, it is possible to create a structure by inheriting the Exception superclass and adding additional properties to it. Message — add the message you want to send. It is possible to use a text message in combination with passed variable values using the concat() function. Any functions of the Expression Editor are also available for use.Can be used without an Exception Handler.
Exception Handler	Process an alternative flow to handle exceptional situations. Added along with the OUT node where the result is passed.	Name — name of the node. Parameters: Exception — select the required Exception. Depending on the selected structure, a certain Raise Exception will be processed. Each Exception Handler matches only one exception used in the Raise Exception node. Unlike Raise Exception, where values are passed to exception parameters, it forms an object containing all exception parameters and their values.
Dictionary	Structured ordered data storage. It is used both in scorecards and independently in flows.	Name — name of the node. Parameters: Dictionary — add a specific dictionary to the node that was created within the project for use in the current flow. The set of required inputs depends on the selected dictionary model as an output.
Decision Table	Model views with complex logic. Establishes a relationship between conditions and actions.	Name — name of the node. Parameters: Decision Table — add a specific decision table to the node that was created within the project for use in the current flow. The set of required inputs depends on the selected decision table model as an output.
ScoreCard	A graphical representation of a mathematical formula that is used to predict the future behavior of a customer or prospect based on what is known about them.	Name — name of the node. Parameters: Scorecard — select a specific scorecard to the node that was created within the project for use in the current flow. The set of required inputs depends on the selected scorecard model as an output.
PMML	A way to describe predictive models generated by data mining and machine learning algorithms.	Name — name of the node. Parameters: PMML — add a specific PMML to the node that was created within the project for use in the current flow. The set of required inputs depends on the selected PMML model as an output.

Flows builder Structures builder