Redis

Node catalog Actions
On this page

Guided actions for Redis keys, hashes, and lists

Usage and specifics

Choose an operation for keys, hashes or lists. ttlSeconds uses seconds. The existing Redis value type must match the operation.

Technical type : redis. Runtime : nodulz.

Credentials and prerequisites

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter Type Default Values / limits
credentialId string "" -
operation enum "get" get, set, delete, exists, increment, expire, ttl, hash_get, hash_set, hash_delete, list_push, list_range
key string "" -
field string "" -
value string "" -
ttlSeconds number 0 -; ≥ 0
incrementBy number 1 -
rangeStart number 0 -
rangeStop number -1 -

Configuration help

credentialId
Redis credential
Select a Redis vector credential with a redis:// or rediss:// URL and optional password.
operation
Operation
Choose a guided Redis command.
key
Key
Redis key. Workflow expressions are supported.
field
Field
Field name within the hash.
value
Value
Text to write to Redis. Workflow expressions are supported.
ttlSeconds
Time to live (seconds)
For SET, 0 keeps the key without expiration. For EXPIRE, enter a positive value.
incrementBy
Increment
Integer added to the current value. May be negative.
rangeStart
Start
Inclusive first index. Negative indexes count from the end.
rangeStop
Stop
Inclusive last index. -1 means the final item.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json
{
  "credentialId": "",
  "operation": "get",
  "key": "",
  "field": "",
  "value": "",
  "ttlSeconds": 0,
  "incrementBy": 1,
  "rangeStart": 0,
  "rangeStop": -1
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : Expressions and data, Executions, Node catalog.