AMQP 1.0
The AMQP 1.0 connection allows the Intelligence Hub to connect to brokers that support the AMQP 1.0 protocol for reading and writing messages.
Connection Settings
| Setting | Description |
|---|
| Authentication Type | How the connection authenticates with the broker. Default is None. See the options below. |
| Host | The hostname or IP address of the broker. |
| Port | The port the broker listens on. Default is 5672. Brokers commonly listen for TLS connections on 5671. |
| Virtual Host | The broker virtual host to connect to. Default is /, the broker’s default virtual host. Enter the name exactly as defined on the broker. A leading / is part of the name, so /myHost and myHost are different virtual hosts. |
| Container ID | Identifies this connection to the broker, similar to an MQTT client ID. Leave blank to generate an ID. |
| Connect Timeout (seconds) | Maximum time to wait for the connection to the broker to open. Also limits the OAuth 2.0 token request, attaching to an address, and how long a write waits for the broker to accept a message. Valid range is 1–300 seconds, default 10 seconds. |
| Idle Timeout (seconds) | The idle timeout requested from the broker, used to detect a dead connection. Valid range is 0–3600 seconds, default 60 seconds. 0 disables it, so a broker or network failure that does not close the connection can go undetected. |
| Enable SSL | Enable for brokers that require transport layer security. Disabled by default. Required by the OAuth 2.0 and Certificate authentication types. See additional TLS options below. |
Authentication Type Options:
| Option | Description |
|---|
| None | Connect without credentials, using the SASL ANONYMOUS mechanism. |
| Username / Password | Authenticate with a username and password, using the SASL PLAIN mechanism. The Password supports Secrets. |
| OAuth 2.0 | Authenticate with an access token requested from an identity provider. Requires Enable SSL. See OAuth 2.0 Authentication below. |
| Certificate | Authenticate with the client certificate presented during the TLS handshake, using the SASL EXTERNAL mechanism. Select the Client Certificate/Key Pair from the certificate store. Requires Enable SSL. |
TLS Options (shown when Enable SSL is enabled):
| Option | Description |
|---|
| Ignore Self-Signed Certificate | Accepts any certificate returned from the broker. Use only for testing. Disabled by default. |
| Server Certificate | The broker’s CA certificate imported into the certificate store. When blank, the broker’s certificate is validated against the default Java trust store, which works for brokers using certificates from a public CA. Shown when Ignore Self-Signed Certificate is disabled. |
OAuth 2.0 Authentication
The connection requests an access token with the OAuth 2.0 client credentials grant and presents it to the broker when connecting. The token is reused until shortly before it expires.
| Setting | Description |
|---|
| Token URL | The OAuth 2.0 token endpoint the access token is requested from. Must be an http or https URL. |
| Client ID | The OAuth 2.0 client ID. |
| Client Secret | The OAuth 2.0 client secret. Supports Secrets. |
| Username | The identity sent to the broker alongside the access token. Required. |
| SASL Mechanism | How the access token is presented to the broker. Default is PLAIN. See the options below. |
| Scope | Optional scope to request. |
| Audience | Optional list of audience values to request. |
| Client Authentication | Where the Client ID and Client Secret are sent on the token request: Send as Basic Auth Header (default) or Send client credentials in body. |
SASL Mechanism Options
| Mechanism | Description |
|---|
| PLAIN | Sends the access token as the password. |
| XOAUTH2 | Used by brokers such as Solace and Apache Qpid Broker-J. |
| OAUTHBEARER | The standard OAuth 2.0 SASL mechanism (RFC 7628). |
AMQP 1.0 inputs support subscriptions and can be used as a source in an Event Trigger.
| Setting | Description |
|---|
| Address | The broker node to receive messages from. The address syntax, including any wildcard support, is defined by the broker. |
| Message Format | How to decode the message payload. Default is Auto. See the options below. |
| Include Metadata | When enabled, the address and AMQP metadata of the message are included alongside the value in the read data. Disabled by default. See the example below. |
| Prefetch | Maximum number of messages the broker may send ahead of them being consumed. Valid range is 1–1000, default 10. Inputs that share an address use the value set by the first one to start. |
| Type | Description |
|---|
| Auto | The payload can be JSON, String, or Binary. |
| JSON | The payload is deserialized as JSON. A payload that is not valid JSON returns a bad value. |
| String | The payload is treated as a UTF-8 string. |
| Binary | The payload is treated as a byte array. |
Reading Messages
Inputs consume the messages they receive, and the Intelligence Hub acknowledges each message as it arrives. Consumed messages are removed from the queue, so an input competes with any other consumer of the same queue.
- A read, including a test read, returns the last message received on the address. Before the first message arrives, the read returns no value.
- An Event Trigger subscription receives every message in the order it arrives.
The first read of an input, including a test read, attaches the connection to the address. The connection keeps consuming messages from it until the connection is stopped or restarted, even if the input is no longer read. Messages that arrive between reads are acknowledged and only the last one is returned. Avoid reading from queues that other consumers depend on.
{
"_address": "/queues/factory.events",
"_messageId": "",
"_correlationId": "",
"_subject": "",
"_contentType": "application/json",
"_replyTo": "",
"_groupId": "",
"_creationTime": "2026-10-01T14:03:12.512Z",
"_timestamp": "2026-10-01T14:03:12.530Z",
"_properties": {
"line": "line1"
},
"value": {
"temperature": 72.4
}
}
| Field | Description |
|---|
| _address | The address the message was sent to, or the input’s Address when the message does not include one. |
| _messageId, _correlationId, _subject, _contentType, _replyTo, _groupId | The AMQP message properties. Properties the sender did not set are empty strings. |
| _creationTime | The time the sender created the message. When the sender did not set one, the time the message was received. |
| _timestamp | The time the Intelligence Hub received the message. |
| _properties | The message’s application properties as name/value pairs. |
| value | The decoded payload. |
Output Settings
| Setting | Description |
|---|
| Address | The broker node to send messages to. The address syntax is defined by the broker. |
| Persist Messages | When enabled, messages are marked durable so the broker persists them and they survive a broker restart. Enabled by default. |
| Message Id | Optional message ID set on each message. When left blank, no message ID is set. |
| Include Properties | When enabled, the Message Properties are attached to each message as AMQP application properties. Disabled by default. |
| Message Properties | A list of Name/Value pairs to attach to each message. Name and Value are required, and names must be unique. Shown when Include Properties is enabled. |
Each message is sent as JSON with the content type application/json, and its creation time is set to the time it is sent. A write completes when the broker accepts the message.