Integration · Database
Redis + OrchestrAI
Catalog exported 2026-09-02 · Redis website
Read and set Redis keys from chat, check server and cluster info, and flush a database only after confirming.
OrchestrAI exposes 4 Redis operations: 2 are low-risk (read-only or low-impact), and 2 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Engineers use it to read a specific key such as a feature flag or a cached config blob while debugging, to set a value during an incident, and to pull server and cluster info to check memory, connected clients, and replication state before a scaling decision. Flushing a database deletes every key, so it is rated high risk and stops for confirmation. What is missing is any way to enumerate keys, delete a single key, or set a TTL, so cleaning up one stale cache entry still requires redis-cli.
Every Redis operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Get Redis Cluster Info |
Get Redis cluster/server info | Low risk | No |
Get Redis Key |
Get Redis key value | Low risk | No |
Set Redis Key |
Set Redis key value | Creates resources | No |
Flush Redis Database |
Flush Redis database (DANGER: deletes all keys) | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A Redis credential (stored as redis).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Get the value of feature:checkout_v2 from the production Redis
- Set maintenance_mode to true in the sessions Redis instance
- Show me the memory usage and replication status of the cache cluster
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI accidentally flush my Redis database?
- redis_flush is rated high risk and marked confirm, so it names the target and waits for an explicit yes before anything is removed. Reads and single-key sets carry no such gate.
- Can OrchestrAI list all keys in Redis?
- No, The available operations are get, set, cluster info, and flush. There is no scan or keys operation, so you need to know the key name you want.
- How does OrchestrAI authenticate to Redis?
- You add a Redis credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.