HTTP Node

An HTTP node in a data workflow system is a component that allows for the integration of external HTTP-based APIs or web services. It can send requests (GET, POST, etc.) to retrieve or send data.

What is a HTTP?

The HTTP serves as a versatile tool for integrating external data sources into workflows by enabling communication via HTTP methods like POST and GET. This functionality allows users to seamlessly send data to the workflow or receive it from various IoT cloud services. Integrations with platforms such as Microsoft Azure IoT Hub, Actility ThingPark, and Digital Matter OEM Server illustrate its broad applicability across diverse IoT ecosystems. By leveraging HTTP, users can establish bidirectional communication channels, facilitating the exchange of real-time data between the workflow and external systems. This capability empowers organizations to harness data from IoT devices and cloud services, enabling informed decision-making, proactive monitoring, and automation within their applications and processes.

Outputs

The HTTP node will output each device’s payload in the order that they are received

How to Use

Implementation

In the Rayven Workflow Builder:

Select Inputs.
Drag the HTTP node to the canvas.
Double click on the HTTP node to open the configuration window.

Configuration

Section: General
This section contains basic configuration elements required for any HTTP implementation
Field	Requirement	Comments
Node Name	Mandatory	Enter a name for this node. This provides a handle to which you and others can refer, so it should be simple but meaningful and explain the node’s purpose.
URL	Autofilled	This unique URL points to the Rayven server and can’t be changed. Example of URL: https://my.rayven.io:8082/api/main?uid=1564c1d5321f0154422882bd3f80853587a3&deviceid=[[device_id]] When transmitting to this URL make sure to change the [[device_id]] to be the same as will appear in the Device Management system, so that the system can authorize the data from the device to be saved in the system.
Password	Optional	The password set must be at least 8 characters long (include one lower case character, one upper case character and one special character). This will allow an extra layer of security by creating an authentication with a password at your device.
Payload Format	Mandatory	In this field, select the format from the dropdown menu that you will be sending the data (JSON is the default format). JSON XML CSV Bulk Compressed XML Zip Bulk Compressed CSV JSON Array GET Query Strings

Section: Advanced Features
In the case that you would like the timestamp of the data to be based on the data coming from the device, and if the device is coordinated with a time zone, you will need to define the following three fields:
Field	Requirement	Comments
Location of Child Array	Optional	If you choose JSON Array please specify the fields leading to this Array, for example: “parent_field.path”
Date Field Name	Optional	Define the name of the date field coming in from your device.
Date Format	Optional	Define the format of how the data will be coming through, for example: EPOCH, EPOCHMS, dd/MM/yyyy HH:mm:ss. If the date is coming through in 24 hour format, the hours need to be in capital letters, (ie. HH/mm/ss).
Timezone	Optional	Define from a drop down list, the time zone that the device is recording the data.

Activation

Once the node has been configured, click the Activate button and then click Save. The node is ready to receive data into the workflow.