Redis in n8n: Built-in Nodes vs Community Nodes

n8n has three built-in Redis nodes: the Redis node for keys and messages, the Redis Trigger for channel messages, and Redis Chat Memory for AI agents. Redis community nodes add data types and commands the built-in node doesn’t list, plus chat memory and batching built for specific setups. This guide compares them, using n8n’s documentation, the description and README each author publishes on npm and our own download data.

What the built-in Redis nodes do

• Redis: per n8n’s documentation, delete a key, get a key’s value, set a key’s value, increment a key by 1 (creating it if needed), get all keys matching a pattern, get information about the Redis instance, and publish a message to a channel.
• Redis Trigger: subscribes to a Redis channel and starts the workflow whenever the channel receives a message.
• Redis Chat Memory: stores an AI agent’s conversation in Redis, with a session key, a session time to live and a context window length. The docs warn that all Redis Chat Memory nodes in a workflow share the same memory instance unless you give them different session IDs.

Redis community nodes

Our Redis hub lists 13 packages that pass our quality rule, with 431 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):

Versions and dates come from the npm registry. Weekly downloads: npm, last 7 days, adjusted for npm outage days.

@vicenterusso/n8n-nodes-redis-enhanced

The most downloaded Redis package lists 35 operations in its README:

• Keys and strings: get, set with NX or XX modes and a TTL, delete, exists, append, string length, get-set and increment with an optional TTL.
• Bulk: multi get, multi set, and Scan, which it calls the production-safe way to iterate keys, next to the keys pattern search.
• Lists, sets, sorted sets and hashes: push and pop, blocking pops (BLPOP and BRPOP), set membership, sorted set ranges, and hash fields, keys, values and lengths.
• TTL: read a key’s TTL, remove an expiration or expire at a set time.
• Advanced: run Lua scripts with Eval, and publish to channels.

It has its own Redis Enhanced credential with host, port, database, password, a username for Redis 6 ACLs and SSL. @codingfrog/n8n-nodes-redis-enhanced carries the same README and has a newer release (0.2.0, November 2025).

@iaconnecto/n8n-nodes-redis-extended

Adds hash operations to the core ones: get a hash field (HGET), delete fields (HDEL) and list a hash’s field names (HKEYS). Its README also lists push and pop on lists, TTLs on keys, dot notation for nested values and automatic JSON parsing.

n8n-nodes-memory-redis-isolated

Chat memory for AI agents, written for n8n’s queue mode with several workers. Its README points to two differences from the built-in Redis Chat Memory: chat histories are kept apart per workflow using a hashed workflow ID, and the node uses its own credential type that the Redis operation nodes can’t use, so a Redis node can’t read other workflows’ chat history through the same credential. By default it reuses the Redis connection of your n8n queue (one database number higher), and every session expires, after at most 24 hours. Its README notes that the node appears as Redis Chat Memory (Isolated) in the AI Agent’s Memory input, and that searching for “isolated” finds it more easily than “redis”.

@andresfrei/n8n-nodes-redis-debounce

Collects items in Redis and releases them as one batch once no new item has arrived for a set number of seconds; each new item resets the timer. Its README’s example is chat messages: a webhook workflow adds each message under the user’s ID, and a second workflow on a Schedule Trigger processes the batches that are ready.

Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.

How to choose

• Get, set, increment and publish, or start a workflow from a channel: the built-in Redis and Redis Trigger nodes, with nothing to install.
• Lists, sets, sorted sets, hashes, TTLs or Lua scripts: @vicenterusso/n8n-nodes-redis-enhanced.
• Only hash fields: @iaconnecto/n8n-nodes-redis-extended.
• AI agent memory in queue mode, kept apart per workflow: n8n-nodes-memory-redis-isolated.
• Answer once when a user sends several messages in a row: @andresfrei/n8n-nodes-redis-debounce.

To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Related: Qdrant and n8n.

FAQ

Does n8n have a Redis node?

Yes, three: Redis for keys and publishing, Redis Trigger for channel messages, and Redis Chat Memory for AI agents. Community nodes add more Redis commands and data types.

Can the n8n Redis node work with hashes and lists?

The built-in node’s documented operations are get, set, delete, increment, keys, info and publish. For hash fields, lists, sets and sorted sets, use a community node such as @vicenterusso/n8n-nodes-redis-enhanced.

How do I use Redis as memory for an n8n AI agent?

Connect the built-in Redis Chat Memory node to the AI Agent’s memory input and set a session key. In queue mode with several workers, n8n-nodes-memory-redis-isolated is built for that setup.

What is the most used Redis community node?

@vicenterusso/n8n-nodes-redis-enhanced, with 275 weekly npm downloads on 28 October 2026.