Redis

storage.redis Storage v0.1.0

Talks to a Redis server over the dependency-free RESP2 wire client: get/set/del/incr/expire, list push/pop, hash set/get-all, or any raw command. Leave the value blank to store the record's own payload. Array-native: a list on the wire is N records, so a key operation runs once per record (Key, Value and Field resolved against THAT record) and returns one result per record — all pipelined over ONE connection, so ten records cost one connect and one round trip. A single object in returns a single result, un-wrapped; an empty list runs no command and opens no connection. The raw command operation never fans out: its argv varies on nothing per record and may be whole-keyspace (FLUSHALL, SCAN, INFO).

The Redis step on the Studio canvas
The Redis step as it appears on the Studio canvas — input pins on the left, output ports on the right.

Finding it in the library

Search the builder's node library for Redis (it lives under Storage). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Redis in the node library, with the in-editor docs panel open
The library entry and the in-editor docs panel for Redis — the same reference this page is generated from.

Wired up in the builder

Redis in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Redis wired into a runnable workflow in the Studio builder
Redis wired into a runnable flow — input on the left, output on the right.

How it’s configured

The node’s settings as the builder shows them — every field laid out with real values. In the Studio these are edited on the node: click the chevron on the divider under its ports to open them.

The Redis node's settings in the Studio builder
The settings for Redis, showing the values from the flow above.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

DirectionPortLabelWhat flows through it
InputinputInput
OutputoutputResult

How data flows through it

Redis consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

String-typed properties accept {{ }} expressions evaluated against the incoming item at run time — e.g. {{ $json.customer.email }}. On this node that’s host, password, key, value, field. JSON- and code-typed fields never interpolate — they are passed through literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Redis) works as well as the exact type id (storage.redis).

In the Copilot panel (or any connected AI):

add a redis node after the trigger

As a step in a create_chain_workflow call:

{"type":"Redis","config":{}}
Raw MCP call — add this node to a workflow with add_node 
curl -s -X POST http://localhost:4800/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Redis" } } }'

Example input & output

Hand-crafted example (captured shape — regenerating live needs a Redis server reachable from the capture machine).

Input — what the node received

The Redis node's input envelope in the run data viewer
The input envelope in the Runs view — Flowdrome always shows the whole envelope, with the payload inside body.

Output — what the node produced

The Redis node's output envelope in the run data viewer
The output envelope after the step ran.

Property reference

Every setting, with its type and default — the same fields shown configured above.

PropertyTypeDefaultDescription
Credential
credentialId		 credential "" Use a stored credential for this connection — its fields are filled in at run start. Pick "None" to enter the connection details manually.
accepts credential templates: redis
Host
host		 string "localhost" Redis server hostname.
Port
port		 int 6379 Redis server port.
Password
password		 string "" AUTH password — supports ${credential.NAME.FIELD}. Leave blank to skip AUTH.
Database
db		 int 0 Logical database index — SELECT is sent when greater than 0.
TLS
tls		 boolean false Connect over TLS.
Operation
operation		 select "get" get/set/del/incr/expire work on a key; lpush/rpop on a list; hset/hgetall on a hash; command runs a raw argv array. The key operations run ONCE PER RECORD — a list of ten on the input sends ten commands (pipelined over one connection) and returns ten results; command stays a single call whatever arrives.
commanddelexpiregethgetallhsetincrlpushrpopset
Key
key		 string "" The Redis key to operate on. Supports {{ }}, resolved against THIS record — user:{{ $json.id }} over a list of ten addresses ten keys. An expression that resolves to nothing fails with REDIS_CONFIG_INVALID rather than pointing every record at the same key.
Shown when (operation ?? "get") !== "command"
Value
value		 string "" Value to store, resolved against THIS record. Leave blank to store the record's own payload (strings as-is, anything else as JSON), so a list stores each element under its own key.
Shown when ["set", "lpush", "hset"].includes(operation ?? "get")
TTL (seconds)
ttlSeconds		 int 0 set: expiry via EX when greater than 0. expire: the TTL to apply.
Shown when operation === "set" || operation === "expire"
Hash field
field		 string "" The hash field to set (hset). Supports {{ }}, resolved against THIS record.
Shown when operation === "hset"
Command
commandJson		 json [] Raw command as a JSON argv array, e.g. ["ZADD", "k", "1", "m"].
Shown when operation === "command"
Timeout (ms)
timeoutMs		 int 15000 Abort the whole conversation after this many milliseconds.
Verify TLS certificate
rejectUnauthorized		 boolean false Verify the server's TLS certificate. Off (default) accepts self-signed certificates — the storage.sql "require" semantics.
Shown when tls === true

Related nodes

The rest of the Storage group — the same folder you’d scan in the editor’s library.

  • Read File Reads file content from a configured path or input path
  • Global Key / Value Reads, writes, deletes, and atomically increments shared JSON-compatible runtime values
  • Memory Read/write durable cross-run memory (append/recall/get/set/clear) via the state engine
  • Write File Writes workflow data to a file — pretty JSON, raw text, or decoded base64 bytes — with optional append and par
  • SQL Query Runs a SQL query against PostgreSQL or MySQL with real server-side positional parameters ($1…$n / ?) — no stri
  • S3 Storage Reads and writes objects in S3-compatible storage (AWS S3, MinIO, R2) with Signature V4: put, get, delete, lis
  • FTP Lists, downloads, uploads, deletes, or creates directories on an FTP server (optional explicit FTPS via AUTH T
  • MongoDB Runs one MongoDB operation over the dependency-free OP_MSG wire client: find, insert many, update many, delete

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.