Redis

Read and write data to a Redis cache. The Redis node supports a wide range of operations across strings, lists, hashes, sets, and pub/sub -- all through a single configurable node.

Requires a Redis connection.

Configuration

Field	Description	Notes
Redis Connection	The Redis connection to use	Required. Select from your configured Redis connections.
Operation	The Redis command to execute	Required. See the operation tables below.

Additional fields appear depending on the selected operation.

Operations

String Operations

Operation	Description	Required Fields
GET	Retrieve the value of a key	Key
SET	Set a key to a value	Key, Value
DEL	Delete a key	Key
EXISTS	Check whether a key exists	Key
INCR	Increment a numeric key by a given amount	Key
DECR	Decrement a numeric key by a given amount	Key
EXPIRE	Set a time-to-live (TTL) on a key	Key, TTL
TTL	Get the remaining TTL of a key in seconds	Key
MGET	Retrieve values for multiple keys at once	Keys (comma-separated)
MSET	Set multiple key-value pairs at once	Key-Value Pairs (JSON)

List Operations

Operation	Description	Required Fields
LPUSH	Push a value to the beginning of a list	Key, Value
RPUSH	Push a value to the end of a list	Key, Value
LPOP	Remove and return the first element of a list	Key
RPOP	Remove and return the last element of a list	Key
LRANGE	Return a range of elements from a list	Key, Range Start, Range Stop

Hash Operations

Operation	Description	Required Fields
HGET	Get the value of a hash field	Key, Hash Field
HSET	Set a hash field to a value	Key, Hash Field, Value
HGETALL	Get all fields and values in a hash	Key
HDEL	Delete a hash field	Key, Hash Field

Set Operations

Operation	Description	Required Fields
SADD	Add a member to a set	Key, Value
SREM	Remove a member from a set	Key, Value
SMEMBERS	Get all members of a set	Key
SISMEMBER	Check if a value is a member of a set	Key, Value

Pub/Sub

Operation	Description	Required Fields
PUBLISH	Publish a message to a channel	Channel, Value

Scanning

Operation	Description	Required Fields
SCAN	Iterate over keys matching a pattern	Pattern, Count Hint

Operation-Specific Fields

These fields appear conditionally based on the selected operation.

Field	Description	Shown For
Key	The Redis key to operate on. Supports templates.	All operations except MGET, MSET, SCAN
Keys (comma-separated)	Multiple keys, one per entry. Supports templates.	MGET
Key-Value Pairs (JSON)	A JSON object mapping keys to values, e.g. {"key1": "value1", "key2": "value2"}.	MSET
Value	The value to store or publish. Supports templates.	SET, LPUSH, RPUSH, HSET, SADD, SREM, SISMEMBER, PUBLISH
Hash Field	The field name within a Redis hash. Supports templates.	HGET, HSET, HDEL
Set Mode	Controls conditional writes: Always (default), Only If Not Exists (NX), or Only If Exists (XX).	SET
TTL (seconds)	Expiration time in seconds.	SET, EXPIRE
Increment By	The amount to increment or decrement. Defaults to 1.	INCR, DECR
Range Start	The start index for the list range. Defaults to 0.	LRANGE
Range Stop	The stop index for the list range. Defaults to -1 (end of list).	LRANGE
Channel	The pub/sub channel name. Supports templates.	PUBLISH
Pattern	A glob-style pattern to match keys. Defaults to *.	SCAN
Count Hint	Approximate number of keys to return per scan iteration. Defaults to 100.	SCAN
Value Type	Whether the value should be treated as a plain String or as JSON. When set to JSON, values are serialized before writing and automatically deserialized on read.	SET, HSET, LPUSH, RPUSH

Output

The node outputs a single item with the following fields:

Field	Description
operation	The Redis command that was executed
key	The key that was operated on (not present for MGET, MSET, SCAN, PUBLISH)
result	The result returned by Redis (value, list, hash map, boolean, or count depending on the operation)

For MGET, the output includes keys (the list of requested keys) and result (an array of values).

For MSET, the output includes pairs (the key-value map) and result.

For SCAN, the output includes pattern and result (the list of matching keys).

For PUBLISH, the output includes channel, message, and subscribers (the number of clients that received the message).

TIP

When Value Type is set to JSON, read operations (GET, HGET, LRANGE, SMEMBERS, HGETALL, LPOP, RPOP) automatically attempt to parse stored JSON strings back into structured objects. This makes it easy to round-trip complex data through Redis.

Use Cases

• Caching API responses -- Store expensive HTTP results with a TTL and retrieve them in later runs.
• Shared counters -- Use INCR/DECR to maintain counters across workflow executions.
• Workflow coordination -- Use sets or lists to track processed item IDs and avoid duplicates.
• Real-time messaging -- Use PUBLISH to send messages to external subscribers listening on Redis channels.