Skip to content

Plan Icon Ultimate

MQTT Broker Sync#

See Integration Hub

Use the MQTT Broker integration to connect mybusiness AI to an MQTT broker and reuse that connection inside flows.

This integration is typically used when devices, machines, gateways, or external systems exchange events through MQTT topics and a flow should publish data to those topics.

What this integration does#

The MQTT Broker integration stores the broker connection settings that are used by MQTT flow nodes.

With this integration you can configure:

  • Broker host and port
  • MQTT client ID
  • Optional username and password authentication
  • Topic definitions used by your flows
  • Optional TLS or mutual TLS authentication

Basic configuration#

Create a new integration of type MQTT Broker in the Integration Hub and fill in the required connection data.

Fields#

Host : Hostname or IP address of the MQTT broker.

Port : Network port of the MQTT broker. Common values are 1883 for non-TLS connections and 8883 for TLS-secured connections.

Client ID : Unique MQTT client identifier used by mybusiness AI when connecting to the broker.

Username : Optional broker username if the broker requires username/password authentication.

Password : Optional broker password.

Topics : Comma-separated list of MQTT topics that belong to this integration and are used by your flows.

TLS and certificate authentication#

If your broker requires encrypted communication or certificate-based authentication, enable TLS in the integration.

When TLS is enabled, additional fields are available.

TLS fields#

CA Certificate : Certificate authority used to validate the MQTT broker certificate. Upload a PEM, CRT, or CER file.

Client PKCS#12 Keystore : PKCS#12 keystore containing the client certificate and private key used for mutual TLS authentication. Supported file types are .p12 and .pfx.

Client Keystore Password : Password required to open the uploaded PKCS#12 keystore.

When to use which setup#

Use only Host, Port, Client ID, and optionally Username and Password if your broker does not require TLS.

Enable TLS and upload certificates if:

  • the broker is exposed over TLS
  • the broker certificate must be validated against a custom CA
  • the broker requires a client certificate for mutual TLS authentication

Using the integration in flows#

After the integration is created, it can be selected in the MQTT node inside a flow.

For general information about building and running flows, see Flow Designer.

Typical flow usage:

  1. Add an MQTT node to your flow.
  2. Select the MQTT Broker integration in the node.
  3. Define the target topic.
  4. Define the message as a fixed value or as a flow variable.
  5. Run the flow to publish the message to the broker.

Certificate preparation#

Some MQTT providers deliver the client certificate, private key, and CA certificate as separate files instead of a PKCS#12 archive.

In that case, convert them into a .p12 or .pfx file before uploading the client credentials to mybusiness AI.

Typical input files are:

  • client.crt
  • client.key
  • ca.crt

Notes#

  • TLS settings are only applied when TLS is enabled.
  • Existing non-TLS MQTT integrations continue to work without certificate files.
  • Sensitive files and passwords are stored as protected integration data and are not returned as plain values in the UI.

Troubleshooting#

If the connection does not work, verify the following points:

  • Host and Port are correct and reachable from the platform
  • the broker accepts the configured Client ID
  • username and password are correct if broker authentication is enabled
  • the uploaded CA certificate matches the broker certificate chain
  • the PKCS#12 file contains the expected client certificate and private key
  • the keystore password is correct

Typical symptoms:

  • Connection refused: broker address, port, credentials, or topic permissions may be incorrect
  • TLS handshake errors: CA certificate, client certificate, or keystore password is likely incorrect
  • Client already connected or rejected: the Client ID may already be in use or not accepted by the broker