Reference · Credentials
Connect AMQP to BusyBot
Used by 1 BusyBot node.
Type
amqpApi 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Hostnamehostname | string | Yes | The hostname or IP address of the AMQP broker. |
Portport | number | Yes | The port number. Default 5672 for TCP, 5671 for TLS. |
Usernameusername | string | No | Authentication username. |
Passwordpassword | password | No | Authentication password. |
Transport TypetransportType | string | No | Optional: \ |
Setting up AMQP
- In AMQP, create the credential this connection needs — the values listed in the table above. These are issued from your own AMQP account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose AMQP.
- Paste each value into the matching field and save.
- Add the AMQP Sender 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 AMQP credentials?
One node: AMQP Sender. Create the credential once and select it in that node.
What does a AMQP credential need?
5 fields: Hostname, Port, Username, Password, Transport Type. Required: Hostname, Port. The values come from your own AMQP account.
How are AMQP 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 AMQP
One credential works across every node below — create it once and reuse it.