Reference · Credentials
Connect RabbitMQ to BusyBot
Used by 1 BusyBot node.
Type
rabbitMqApi 12 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Hostnamehostname | string | Yes | — |
Portport | number | Yes | — |
Usernameusername | string | No | — |
Passwordpassword | password | No | — |
Virtual Hostvhost | string | No | — |
SSLssl | boolean | No | — |
Reject Unauthorized TLSrejectUnauthorized | boolean | No | — |
CA Certificateca | password | No | — |
SASL Externalpasswordless | boolean | No | — |
Client Certificatecert | password | No | — |
Client Keykey | password | No | — |
Passphrasepassphrase | password | No | — |
Setting up RabbitMQ
- In RabbitMQ, create the credential this connection needs — the values listed in the table above. These are issued from your own RabbitMQ account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose RabbitMQ.
- Paste each value into the matching field and save.
- Add the RabbitMQ 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 RabbitMQ credentials?
One node: RabbitMQ. Create the credential once and select it in that node.
What does a RabbitMQ credential need?
12 fields: Hostname, Port, Username, Password, Virtual Host, SSL, Reject Unauthorized TLS, CA Certificate, SASL External, Client Certificate, Client Key, Passphrase. Required: Hostname, Port. The values come from your own RabbitMQ account.
How are RabbitMQ 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 RabbitMQ
One credential works across every node below — create it once and reuse it.