The Nodes
Dernière mise à jour
Dernière mise à jour
The iconnek.io sidebar contains a set of nodes that form the basic building blocks of scenario creation.
Information on the use and purpose of each node can be found on separate pages throughout this section.
Comments help make your automation scenario easier to follow and understand, similar to how comments function in programming code.
Exception
The Exception node allows you to force an error on a node. Exception handling is a method used in many programming languages to manage errors and exceptional situations during runtime.
Function
The Function node allows JavaScript code to be executed against messages passing through it.
A complete guide for using the Function node is available in the section.
Switch
The Switch node routes messages to different branches of a flow by evaluating a set of rules against each message.
The node is configured with a property to test. Value rules are then evaluated against this configured property.
Fan Out
The Fan-out node functions like a "For Each" loop in programming. It's used to model information exchange that involves delivery to one or more destinations.
For each element, the Fan-out node will process all connected nodes that follow it.
Sequencer
The Sequencer node allows you to control the order in which data is processed through the scenario, according to a left-to-right priority.
Connector
The Connector node connects third-party API sources to the Iconnek platform. To enable connection to external software, you must first add them to your inventory in the Data Management / Connectors section.
Usage:
Drag and drop the Connector into the scenario editing area
Double-click on the node to open the configuration window
Rename the node if desired
Choose whether the node will be bypassed in the event of errors
Source Tab Configuration:
Select the connector source
Choose the desired route (available routes correspond to those available through the software API)
Specify the limit of elements per call
Filter
The Filter node allows you to include or exclude data according to predetermined criteria from a list previously created in the Data Management / Filter Lists section.
For example, you could use a Filter to exclude entries with names containing "test" from your data. Be precise when creating your filter list, as the filter will match exact characters.
Conversion
The Conversion node uses conversion tables to transform field names of incoming data into a new nomenclature. These conversion lists are defined in the Data Management / Conversion tables section.
For example, you could convert a field name from "English" to "EN" to facilitate data integration between different software systems.
The Mail node sends email notifications based on events occurring in the automation scenario or with Catch node error handling.
DEFAULT
Catch
The Catch node detects and handles errors that may occur during scenario execution. It is present by default in the editing section of your scenario.
Depending on the type of error, you can configure different notifications (such as email alerts) for each case. The Catch node processes the error that occurred at the first node in the scenario. If the "Stop scenario when an error occurs" option is activated by the node in error, the Catch node will process the error of the next node.