Available nodes in the Platform's FlowEngine
- 1 Introduction
- 2 Component List
- 2.1 Input
- 2.2 Social
- 2.3 Advanced
- 2.4 Spreadsheet
- 2.5 Analysis
- 2.6 Output
- 2.7 Storage
- 2.8 Raspberry Pi
- 2.9 Utilities
- 2.10 Weather
- 2.11 Onesait Platform Dataflows
- 2.12 Function
- 2.13 INPUT
- 2.14 OUTPUT
- 2.15 FUNCTION
- 2.16 STORAGE
- 2.17 ANALYSIS
- 2.18 ADVANCED
- 2.19 RASPBERRY PI
- 2.20 WEATHER
- 2.21 UTILITIES
- 2.22 SPREADSHEET
- 2.23 ONESAIT PLATFORM DATAFLOWS
- 2.24 Onesait Platform Dataflows
Introduction
The Flow Engine module is the flow engine that allows to perform data intake, and is build through the programming tool Node-RED, with which you can connect both hardware devices, APIs and online services. One of the advantages on the use of the flow created through Node-RED, is that the information is storage in JSON format, which can be is easily imported or exported.
To create flows using Node-RED, it uses individual units called nodes, and the connection between these nodes is simple and intuitive. In the tool viewer, you can find a description of the node, its inputs and outputs. Next, we show a list of the nodes that have been incorporated into the platform's Flow Engine module along with the library to which each corresponds to, a short description of it, and the official relative documentation.
Component List
INPUT
Node Name | Library | Description | Technical documentation |
 | Activates the flow manually or at regular intervals. | ||
 | Catches errors thrown by nodes in the same tab. | ||
 | Reports about messages from other nodes in the same tab. | ||
 | Creates virtual links between flows. | ||
 | Connects to a MQTT broker, and subscribes to the messages of a specific topic. | ||
 | Create a HTTP endpoint for creating web services. | ||
 | WebSocket entry node. | ||
 | Node-RED-bluemix-nodes | Provides TCP inputs. It can be connected to a remote port or accept incoming connections. |
|
 | Input node that generates a message that contains an encrypted buffer, string or string. | ||
 |
Onesait Platform's own node | Create a HTTP endpoint for creating web services. |
|
 | Performs an insertion of data in the target ontology. | ||
 | Onesait Platform's own node |
Input node for notifications. | |
 | Node-RED-contrib-ttn | Receive events from devices connected to The Things Network. | |
 | Receive information from devices connected to The Things Network. | ||
 | Connects to a Stomp server to receive messages. | ||
 | Subscribes to a specific PubNub channel and receive its content. | ||
Node Name | Library | Description | Technical documentation |
 | Monitors messages in an editor. Sends messages within the editor for debugging purposes. | ||
 | Creates virtual links between flows. | ||
 | Connects to a MQTT broker, and subscribes the messages of a specific topic. | ||
 | Sends responses back to requests received from an HTTP input node. | ||
 | WebSocket exit node. | ||
 |
Node-RED-bluemix-nodes | Provides TCP output options. |
|
 | Sends the corresponding message to the host and the assigned UDP port. | ||
 | Onesait Platform's own node | Send responses back to requests received from an HTTP input node. | |
 | Node-RED-contrib-ttn | Sends information to a device connected to The Things Network. | |
 |
Node-RED-node-stomp | Connects to a Stomp server to send messages. |
|
 | Node-RED-contrib-pubnub | Posts messages on the specified PubNub channel. | |
FUNCTION
Node Name | Library | Description | Technical documentation |
 |
Node-RED's own node | JavaScript method that works against the messages received by the node. | |
 | Sets properties based on the template that is added. | ||
 |
Node-RED's own node | Delays message entry at set intervals. | |
 | Creates a timeout within the flow so a first message is sent, and optionally, depending on the chosen value, a second message will also be sent. | ||
 | Node-RED's own node | Allows to insert a comment. |
|
 | Node-RED's own node | Sends a HTTP request, and return a response. |
|
 | Node-RED'-bluemix-nodes | Connects to a remote TCP port, and answers messages from an input client. | |
 |
Node-RED's own node | Routes messages based on their property values or sequential position. | |
 | Adds, changes, deletes or moves properties of a message. You can specify multiple rules that apply, in the defined order. | ||
 | Scales linearly the received value. | ||
 | Splits a message into a sequence of messages. | ||
 | Joins a sequence of messages into a single message. The way to join them can be automatic, manual or reduced sequence. | ||
 | Sorts a sequence of messages, or the properties of one. | ||
 | Creates message sequences based on different rules, such as: number of messages, time intervals and concatenated sequences. | ||
 |
Node-RED's own node | Converts between the CSV format and the JavaScript object that represents it. The process can be done in either direction. | |
 | Extracts elements from an HTML document using a CSS selector. | ||
 | Converts between the JSON format and the JavaScript object that represents it. The process can be done in either direction. | ||
 | Converts between the XML format and the JavaScript object that represents it. The process can be done in either direction. | ||
 | Converts between the YAML format and the JavaScript object that represents it. The process can be done in either direction. | ||
 | Onesait Platform's own node | Invokes an operation of a REST API from Platform. | |
 |
Onesait Platform's own node | Convert any message into an action for a Digital Twin. |
|
 | Represents a Digital Twin from Platform. | ||
 | Onesait Platform's own node | Node with integration in Firebase for the development of web and mobile applications. | |
 | Onesait Platform's own node | Insert values in an ontology. | |
 | Onesait Platform's own node | Node that is responsible for sending mails. | |
 |
Onesait Platform's own node | Makes a query on dynamic bases. |
|
 | Makes a query on static bases. | ||
 |
Node-RED-contrib-crypto-js | Encrypts the message using a given algorithm. |
|
 | Decrypts the message using a given algorithm. | ||
 | Creates a message authentication code with a hash key. | ||
 | Generates an encrypted message using a given algorithm. | ||
 | Encodes information using a set of specific characters. | ||
 | Decodes information using a set of specific characters. Generates an array of words. | ||
 | Node-RED-node-rbe | Provides reports if an exception happens. It will not send information unless the data has changed. It works with both numbers and strings. | |
 | Node-RED-ontrib-file-function | This node loads the script to be executed from a current document on the disk. It is the same functionality as the "function" node. | |
 | Node-RED-contrib-soap | It allows the user to send a SOAP request. It will be necessary to create a new configuration. It is very important to enter the method name correctly. | |
SOCIAL
Node Name | Library | Description | Technical documentation |
 |
Node-RED-node-email | It allows to periodically receive emails through the IMAP protocol. Files added to the email are treated using an array of objects where each object represents an attachment. The data update time can be chosen. | |
 |
Node-RED-node-twitter | It can be used to search for tweets with a specific term, retrieving all tweets by user, or to view direct messages received from an authenticated user. | |