Global Key / Value

storage.global-key-value Storage v0.1.0

Reads, writes, deletes, and atomically increments shared JSON-compatible runtime values. Array-native: a list on the wire is N records, so the operation runs once per record (Key and Value resolved against THAT record, so one key expression addresses N keys) and returns one result per record; a single object in returns a single result, un-wrapped. A batch is PARTITIONED across the two outputs — the results whose key existed before the operation leave on Found, the rest on Not found, and both fire when the batch is mixed. An empty list runs nothing and emits an empty batch on Found.

The Global Key / Value step on the Studio canvas — The **Global Key / Value** 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 Global Key / Value (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.

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

Wired up in the builder

Global Key / Value 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.

Global Key / Value wired into a runnable workflow in the Studio builder — **Global Key / Value** 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 Global Key / Value node's settings in the Studio builder — The settings for **Global Key / Value**, 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.

Direction	Port	Label
Input	`input`	Input
Output	`found`	Found
Output	`notFound`	Not found

How data flows through it

Global Key / Value 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 key. 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 (Global Key / Value) works as well as the exact type id (storage.global-key-value).

In the Copilot panel (or any connected AI):

add a global key / value node after the trigger

As a step in a create_chain_workflow call:

{"type":"Global Key / Value","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": "Global Key / Value" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what the Runs view shows after pressing Test workflow.

On this run the node emitted on port found.

Input — what the node received

The Global Key / Value 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 Global Key / Value 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.

Property	Type	Default	Description
Operation `operation`	`select`	`"get"`	Key/value operation to perform. It runs ONCE PER RECORD — a list of ten on the input performs ten operations and returns ten results, split across the Found / Not found ports by whether each record's key existed beforehand. `deletegetincrementset`
Key `key`	`string`	`"workflow.counter"`	The global key to operate on. Supports {{ }}, resolved against THIS record — one configured key like user:{{ $json.id }} addresses N different keys across a list. An expression that resolves to nothing fails with GLOBAL_KV_CONFIG_INVALID rather than collapsing the batch onto one key.
Value `value`	`json`	`—`	Value to store (for set) — resolved against THIS record. Use the ƒ button to pick a field from the incoming data. Leave it unset and each record stores itself. Shown when `operation === "set"`
Value path `valuePath`	`field`	`—`	Dotted path to read the value from THIS record (for set). Shown when `operation === "set"`
Amount `amount`	`int`	`—`	Increment amount. Shown when `operation === "increment"`
Default value `defaultValue`	`json`	`0`	Value returned when the key is absent (for get). Shown when `operation === "get"`

Related nodes

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

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.