BusyBot
Search all guides

Reference · Credentials

Connect Kafka to BusyBot

Used by 1 BusyBot node.

Type kafkaApi 12 fields

Fields

FieldTypeRequiredNotes
Client ID
clientId		 string No —
Brokers
brokers		 string Yes —
SSL
ssl		 boolean No —
SSL CA Certificate (PEM)
sslCa		 string No PEM-encoded CA certificate to trust
SSL Client Certificate (PEM)
sslCert		 string No PEM-encoded client certificate for mTLS
SSL Client Key (PEM)
sslKey		 string No PEM-encoded client private key for mTLS
Reject Unauthorized
sslRejectUnauthorized		 boolean No Reject connections with invalid TLS certificates. Set false only for self-signed certs in dev.
SSL Server Name (SNI)
sslServername		 string No Server name for SNI/hostname verification
Authentication
authentication		 boolean No —
SASL Mechanism
saslMechanism		 options No —
Username
username		 string No —
Password
password		 password No —

Setting up Kafka

  1. In Kafka, create the credential this connection needs — the values listed in the table above. These are issued from your own Kafka account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Kafka.
  3. Paste each value into the matching field and save.
  4. Add the Kafka 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 Kafka credentials?

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

What does a Kafka credential need?

12 fields: Client ID, Brokers, SSL, SSL CA Certificate (PEM), SSL Client Certificate (PEM), SSL Client Key (PEM), Reject Unauthorized, SSL Server Name (SNI), Authentication, SASL Mechanism, Username, Password. Required: Brokers. The values come from your own Kafka account.

How are Kafka 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 Kafka

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