ConHiveConHive Docs
ModulesAgent Orchestrator

Agent Orchestrator workflow nodes

Workflow builder nodes of the Agent Orchestrator module.

These nodes appear in the workflow builder when the Agent Orchestrator module is available.

NATS Sender

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.

Inputs

NameDescriptionTypeRequired
DataToSendThe data to be sent to the NATS Streaming server, provided as a key-value map.group of fieldsYes

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
UrlThe NATS server URL, which may include username and password. Example: 'nats://derek:pass@localhost:4222'.textYes1 to 512 characters
SubjectThe subject for NATS subscription or publishing. Wildcards are supported (e.g., 'foo.*' or 'bar.>').textYes1 to 200 characters
ClientidThe client ID used for the NATS connection.textYes1 to 128 characters

NATS Receiver

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.

Outputs

NameDescriptionType
NatssDataThe data received from the NATS Streaming server, formatted as a key-value map representing the payload from the subscribed channel.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
UrlThe NATS server URL, which may include username and password. Example: 'nats://derek:pass@localhost:4222'.textYes1 to 512 characters
SubjectThe subject for NATS subscription or publishing. Wildcards are supported (e.g., 'foo.*' or 'bar.>').textYes1 to 200 characters
ClientidThe client ID used for the NATS connection.textYes1 to 128 characters

HTTP Push

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.

Inputs

NameDescriptionTypeRequired
EventEvent to pushgroup of fieldsYes

NATS Publisher

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.

Inputs

NameDescriptionTypeRequired
EventEvent to publishgroup of fieldsYes

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
UrlNATS server URLtextYes8 to 512 characters
SubjectNATS subject to publish totextYes
Credentials filePath to NATS credentials filetextNo
TokenNATS authentication tokentextYesat most 512 characters
Cert fileTLS certificate filetextNo
Key fileTLS key filetextNo
Ca fileTLS CA certificate filetextNo
Connect timeout msConnection timeout in millisecondsnumberNoat least 5005000
Reconnect wait msReconnect wait time in millisecondsnumberNoat least 1001000
Max reconnectsMaximum reconnection attempts (-1 = unlimited)numberNo-1

HTTP Client

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.

Inputs

NameDescriptionTypeRequired
TriggerTriggeryes/noYes

Outputs

NameDescriptionType
HttpDataThe data received from the HTTP server, formatted as an 'any' type.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
MethodThe HTTP method to use for the request (e.g., GET, POST, PUT, DELETE).textYes2 to 7 charactersGET
UrlThe full URL to send the HTTP request to.textYes1 to 350 characters
HeadersOptional headers to send with the HTTP request.key-value listNomap[string]string{}

HTTP Receiver

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.

Outputs

NameDescriptionType
HttpDataThe data of the incoming HTTP request, formatted as a key-value map.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
EndpointThe endpoint to listen for incoming HTTP requests.textYes1 to 512 characters
PortThe port on which the HTTP server will listen for requests.textYes1 to 5 characters
HeadersOptional headers to include in the HTTP response, such as content-type.key-value listNomap[string]string{}
Bind addressLocal 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.textNoat most 253 characters
Auth tokenShared 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.textNoat most 256 characters

HTTP Sender

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.

Inputs

NameDescriptionTypeRequired
DataToSendThe data to be sent to the HTTP server, provided as a key-value map.group of fieldsYes

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
UrlThe URL to connect to.textYes1 to 512 characters
HeadersOptional headers to send with the HTTP request.key-value listNomap[string]string{}

MQTT Receiver

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.

Outputs

NameDescriptionType
MqttDataThe data received from the MQTT broker, formatted as a key-value map representing the payload from the subscribed topic.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
BrokerURI 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.textNo1 to 250 characters
TopicThe topic to which the message will be published or subscribed.textNo1 to 250 characters
QosQuality 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.numberNo0 to 20
UsernameSet 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.textNo2 to 100 characters
PasswordSet 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.textNo4 to 100 characters
Client idSet 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.textNoat most 100 characters
Order mattersWhether the order of the messages matters.yes/noNofalse
Auto reconnectWhether to automatically reconnect on connection loss.yes/noNotrue
Connect retryWhether to retry the initial connection on failure.yes/noNotrue
Connect retry intervalThe retry interval in seconds between connection attempts.numberNo0 to 10000005
With tlsWhether to use TLS for the connection.yes/noNofalse
Root certificateThe root certificate for TLS verification.textNoat most 100000 characters
Client certificateThe client certificate for mutual TLS authentication.textNoat most 100000 characters
Client keyThe client private key for mutual TLS authentication.textNoat most 100000 characters

MQTT Sender

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.

Inputs

NameDescriptionTypeRequired
DataToSendThe data to be sent to the MQTT broker, formatted as a key-value map.group of fieldsYes

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
BrokerURI 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.textNo1 to 250 characters
TopicThe topic to which the message will be published or subscribed.textNo1 to 250 characters
QosQuality 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.numberNo0 to 20
UsernameSet 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.textNo2 to 100 characters
PasswordSet 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.textNo4 to 100 characters
Client idSet 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.textNoat most 100 characters
Order mattersWhether the order of the messages matters.yes/noNofalse
Auto reconnectWhether to automatically reconnect on connection loss.yes/noNotrue
Connect retryWhether to retry the initial connection on failure.yes/noNotrue
Connect retry intervalThe retry interval in seconds between connection attempts.numberNo0 to 10000005
With tlsWhether to use TLS for the connection.yes/noNofalse
Root certificateThe root certificate for TLS verification.textNoat most 100000 characters
Client certificateThe client certificate for mutual TLS authentication.textNoat most 100000 characters
Client keyThe client private key for mutual TLS authentication.textNoat most 100000 characters

Static Text

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.

Inputs

NameDescriptionTypeRequired
TriggerTriggeryes/noYes

Outputs

NameDescriptionType
StaticTextThe configured static text emitted by the node.text (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
TextThe static text to emit.textYes1 to 2000 characters
Emit on startIf true, the node will emit the text immediately when the flow starts.yes/noNofalse