Module node_io 

Uniform node I/O contract types (spec §4.2–§4.4).

• NodeOutput — a node’s output, mutually exclusive {data} (success) or {errors} (failure), per JSON:API / JSON-RPC 2.0.
• NodeError — a Temporal-shaped error object (code/message/kind/ retryable/source/details).
• InputValue / StructuredInput — explicit literal-vs-ref-vs-template inputs (Step Functions lesson: encode it structurally, never sniff delimiters).
• FlowState — the per-node output namespace, keyed by node id (n8n model).

Structs

NodeError

A single error in a node’s {errors} envelope.

NodeErrorSource

Where an error originated — the node and (optionally) the input that failed.

StructuredInput

A named node input ({ name, value }).

Enums

ErrorKind

Coarse, routing/retry-oriented classification of a NodeError. This is the branch/retry key (Step Functions ErrorEquals, Temporal failure type); code stays the canonical open-ended string.

InputValue

An explicit node input value — resolved structurally, never by sniffing delimiters. Serializes to a single-key object: {literal|ref|template}.

NodeOutput

A node’s output: success carries {data}, failure carries {errors}. The two are mutually exclusive (enforced by the type); engine metadata lives in a sibling meta, never inside data.

Type Aliases

FlowState

The per-node output namespace: each node’s NodeOutput kept immutable, keyed by its stable node id. Downstream addresses <node_id>.data.<path>.