This node acts as a NATS Streaming sender, transmitting data to a configured NATS Streaming server with details such as address, port, and optional credentials. It sends data as an 'any' type, supporting various message structures. Configuration via the NodeNatssConfig is required to ensure a reliable connection and successful data transmission.
This node subscribes to a NATS Streaming channel, receiving messages from a configured NATS Streaming server in real time. It requires server details including address, port, and optional credentials. The received messages are passed along as an 'any' type, offering flexibility in message structure. Proper configuration via the NodeNatssConfig ensures reliable data reception.
Forwards any incoming event as a JSON POST request to a configured HTTP endpoint. Supports configurable batch size and retry-on-failure behavior so that transient network errors do not silently drop events. Use this node as the final sink whenever you need to push flow results to an external REST API, a cloud ingestion endpoint, or a webhook receiver. Example: forward classified bird call events to a cloud dashboard API, or push sensor anomaly alerts to a Slack incoming webhook. Pair with a ThresholdFilter or FilterString upstream to avoid sending low-confidence or irrelevant events.
Publishes any incoming event as a JSON message to a configured NATS subject. Unlike MqttSender (which targets MQTT brokers), NATSPush targets a NATS server and is intended for ConHive-internal event distribution — e.g., forwarding agent-side flow results to a cloud module or another agent over the ConHive NATS backbone. Use this node when you need low-latency, reliable fan-out of flow events to multiple consumers. Example: publish a ClassificationResult to 'agents.audio.events' so that a cloud analytics module and a local alert module both receive the detection simultaneously.
This node acts as an HTTP client that retrieves data from an external HTTP server. It is set up with the server's URL and the HTTP verb for the request (e.g., GET, POST, PUT, DELETE). The node sends a request and processes the response as an 'any' type. This is useful for accessing external APIs, web services, or remote servers.
This node acts as an HTTP receiver: it listens for incoming HTTP requests on the configured port and endpoint, optionally bound to a specific address and protected by a shared auth token, and emits the received data as an 'any' type. Use it to let external systems push data into a flow. To fetch data from an external server instead, use the HttpClient node.
The endpoint to listen for incoming HTTP requests.
text
Yes
1 to 512 characters
Port
The port on which the HTTP server will listen for requests.
text
Yes
1 to 5 characters
Headers
Optional headers to include in the HTTP response, such as content-type.
key-value list
No
map[string]string{}
Bind address
Local IP address or host name the HTTP server binds to, e.g. "127.0.0.1" to accept only local senders. Empty (default) binds all interfaces, which is the current behaviour and exposes the endpoint on every network the device is attached to.
text
No
at most 253 characters
Auth token
Shared secret that senders must present as "Authorization: Bearer <token>" or "X-Auth-Token: <token>". Requests without a matching token are answered with 401. Empty (default) disables the check, which is the current behaviour; the node then logs a warning at start because anyone who can reach the port can feed data into the flow. The token is stored in the flow configuration.
This node acts as an HTTP sender that transmits data to an external HTTP server. It is configured with the server's URL, the HTTP verb (e.g., POST), and optional headers for the request. The node sends data as an 'any' type, facilitating interaction with various external systems. Use this node to send data to external services over HTTP.
This node acts as an MQTT receiver that retrieves data from a configured MQTT broker. It requires broker details such as address, port, and optional authentication credentials. The node subscribes to a specified topic to receive real-time messages, which are then passed along as an 'any' type to accommodate various message structures. Configuration via the NodeMqttConfig is required to establish a successful connection.
URI to the broker to be used. The format should be scheme://host:port where scheme is one of tcp, ssl, ws, wss. host is the IP address or hostname of the broker. port is the port number of the broker. For example, tcp://localhost:1883.
text
No
1 to 250 characters
Topic
The topic to which the message will be published or subscribed.
text
No
1 to 250 characters
Qos
Quality of service level to be used when publishing or subscribing to a topic. The value can be 0, 1, or 2. 0 means at most once delivery, 1 means at least once delivery, and 2 means exactly once delivery.
number
No
0 to 2
0
Username
Set the username to be used by this client when connecting to the MQTT broker. Note: without the use of SSL/TLS, this information will be sent in plaintext across the wire.
text
No
2 to 100 characters
Password
Set the password to be used by this client when connecting to the MQTT broker. Note: without the use of SSL/TLS, this information will be sent in plaintext across the wire.
text
No
4 to 100 characters
Client id
Set the client id to be used by this client when connecting to the MQTT broker. According to the MQTT specification, client ids must be unique per broker. An auto-generated client id is used if not provided.
text
No
at most 100 characters
Order matters
Whether the order of the messages matters.
yes/no
No
false
Auto reconnect
Whether to automatically reconnect on connection loss.
yes/no
No
true
Connect retry
Whether to retry the initial connection on failure.
yes/no
No
true
Connect retry interval
The retry interval in seconds between connection attempts.
number
No
0 to 1000000
5
With tls
Whether to use TLS for the connection.
yes/no
No
false
Root certificate
The root certificate for TLS verification.
text
No
at most 100000 characters
Client certificate
The client certificate for mutual TLS authentication.
text
No
at most 100000 characters
Client key
The client private key for mutual TLS authentication.
This node functions as an MQTT sender for transmitting data to a specified MQTT broker. It requires broker details such as address, port, and optional authentication credentials. The node sends data as an 'any' type, supporting various message structures. Configuration via the NodeMqttConfig is necessary to ensure proper connection and data transmission.
URI to the broker to be used. The format should be scheme://host:port where scheme is one of tcp, ssl, ws, wss. host is the IP address or hostname of the broker. port is the port number of the broker. For example, tcp://localhost:1883.
text
No
1 to 250 characters
Topic
The topic to which the message will be published or subscribed.
text
No
1 to 250 characters
Qos
Quality of service level to be used when publishing or subscribing to a topic. The value can be 0, 1, or 2. 0 means at most once delivery, 1 means at least once delivery, and 2 means exactly once delivery.
number
No
0 to 2
0
Username
Set the username to be used by this client when connecting to the MQTT broker. Note: without the use of SSL/TLS, this information will be sent in plaintext across the wire.
text
No
2 to 100 characters
Password
Set the password to be used by this client when connecting to the MQTT broker. Note: without the use of SSL/TLS, this information will be sent in plaintext across the wire.
text
No
4 to 100 characters
Client id
Set the client id to be used by this client when connecting to the MQTT broker. According to the MQTT specification, client ids must be unique per broker. An auto-generated client id is used if not provided.
text
No
at most 100 characters
Order matters
Whether the order of the messages matters.
yes/no
No
false
Auto reconnect
Whether to automatically reconnect on connection loss.
yes/no
No
true
Connect retry
Whether to retry the initial connection on failure.
yes/no
No
true
Connect retry interval
The retry interval in seconds between connection attempts.
number
No
0 to 1000000
5
With tls
Whether to use TLS for the connection.
yes/no
No
false
Root certificate
The root certificate for TLS verification.
text
No
at most 100000 characters
Client certificate
The client certificate for mutual TLS authentication.
text
No
at most 100000 characters
Client key
The client private key for mutual TLS authentication.
This node emits a predefined text string. Configure the text in the node configuration (NodeStaticTextConfig). The node can act as a trigger (is_start) or be invoked by setting its input to true; it will then output the configured text as a string.