BusyBot
Search all guides

Reference · Credentials

Connect Redis to BusyBot

Used by 1 BusyBot node.

Type redisActionApi 9 fields

Fields

FieldTypeRequiredNotes
Deployment Mode
mode		 options No Standalone Redis (default)
Host
host		 string Yes For Cluster mode, a comma-separated list like \
Port
port		 number Yes —
Sentinels
sentinels		 string No Comma-separated sentinel endpoints (e.g. \
Sentinel Master Name
sentinelName		 string No Master group name advertised by Sentinel. Required when mode is \
Username
username		 string No Redis 6+ ACL username
Password
password		 password No —
Database Number
database		 number No —
SSL
ssl		 boolean No Enable TLS. Certificate verification is always enforced.

Setting up Redis

  1. 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.
  2. In BusyBot, open Credentials → Add credential and choose Redis.
  3. Paste each value into the matching field and save.
  4. 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, 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 Redis credentials?

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

What does a Redis credential need?

9 fields: Deployment Mode, Host, Port, Sentinels, Sentinel Master Name, Username, Password, Database Number, SSL. Required: Host, Port. The values come from your own Redis account.

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

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