In n8n, add a Redis node (or a community Redis node if your setup needs it), then create credentials with your host, port, and password. If you use Redis Cloud, copy the connection details from the dashboard. For self-hosted Redis, confirm network access from your n8n instance (VPN, VPC, or firewall rules). Test with a simple GET/SET workflow first. Once it works, you can reuse the same credentials across workflows.

Quite a lot, honestly. You can watch key changes to trigger alerts, throttle noisy webhooks, store workflow state, or coordinate long-running jobs. Many teams automate cache warming after a deploy, clearing specific keys when product data changes, and writing counters for usage tracking. Redis also works well for deduplication: store an event ID with a TTL so you don’t process the same message twice. Pair it with Slack, Google Sheets, or webhooks for quick visibility.

Yes—you’ll need access to a Redis instance (Redis Cloud or your own server) to run Redis workflows.

Common use cases include rate-limit guards (block repeated actions for about 10 minutes), lightweight queues, session checks, and “single source of truth” flags for workflows. Redis is great when you need fast reads/writes and expiring data. Limitations: it’s not a long-term analytics database, and data can be evicted depending on memory policies. Also, if your Redis sits in a private network, n8n must run where it can reach it. Plan connectivity first, then automate.