Reference · Credentials
Redis credentials
Used by 1 BusyBot node.
Type
redisActionApi 9 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Deployment Modemode | options | No | Standalone Redis (default) |
Hosthost | string | Yes | For Cluster mode, a comma-separated list like \ |
Portport | number | Yes | — |
Sentinelssentinels | string | No | Comma-separated sentinel endpoints (e.g. \ |
Sentinel Master NamesentinelName | string | No | Master group name advertised by Sentinel. Required when mode is \ |
Usernameusername | string | No | Redis 6+ ACL username |
Passwordpassword | password | No | — |
Database Numberdatabase | number | No | — |
SSLssl | boolean | No | Enable TLS. Certificate verification is always enforced. |
Setting up Redis
- In Redis, create the credential this connection needs — the values listed in the table above. These are issued from your own Redis account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Redis.
- Paste each value into the matching field and save.
- Add the Redis 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 and are never shown again after saving.
- 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.
Nodes that use Redis
One credential works across every node below — create it once and reuse it.