BusyBot
Search all guides

Reference · Credentials

Connect MQTT to BusyBot

Used by 1 BusyBot node.

Type mqttApi 13 fields

Fields

FieldTypeRequiredNotes
Protocol
protocol		 options Yes —
Host
host		 string Yes —
Port
port		 number Yes —
Username
username		 string No —
Password
password		 password No —
Clean Session
clean		 boolean No —
Client ID
clientId		 string No —
SSL
ssl		 boolean No —
TLS CA Certificate (PEM)
ca		 string No PEM-encoded CA certificate for verifying broker TLS
TLS Client Certificate (PEM)
cert		 string No PEM-encoded client certificate for mTLS
TLS Client Key (PEM)
key		 string No PEM-encoded client private key for mTLS
Reject Unauthorized Certs
rejectUnauthorized		 boolean No When false, accepts self-signed/invalid TLS certs (dev only — INSECURE)
TLS SNI Server Name
servername		 string No Optional SNI server name override for TLS

Setting up MQTT

  1. In MQTT, create the credential this connection needs — the values listed in the table above. These are issued from your own MQTT account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose MQTT.
  3. Paste each value into the matching field and save.
  4. Add the MQTT node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use MQTT credentials?

One node: MQTT. Create the credential once and select it in that node.

What does a MQTT credential need?

13 fields: Protocol, Host, Port, Username, Password, Clean Session, Client ID, SSL, TLS CA Certificate (PEM), TLS Client Certificate (PEM), TLS Client Key (PEM), Reject Unauthorized Certs, TLS SNI Server Name. Required: Protocol, Host, Port. The values come from your own MQTT account.

How are MQTT secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use MQTT

One credential works across every node below — create it once and reuse it.