Skip to main content
Runchat works with three data shapes: items, lists, and objects. All parameter data is stored internally as flat arrays, which keeps data flow simple and predictable.

Items

A single value, like one piece of text or one image URL. When you type into a node’s input, you’re setting one item per parameter. Internally Runchat stores it as an array with a single element.

Lists

More than one value in the same parameter. You can create a list by:
  • Adding more values to an Input node, for example clicking Add on an Image input to upload several images
  • Setting an Agent node’s More > Output format to List
  • Returning an array from a Code node
  • Receiving a list back from an API
When a parameter holds a list, the node shows Previous item and Next item controls so you can step through inputs and outputs.

Objects

JSON objects describe things using key-value pairs. They’re heavily used by language models, third-party APIs (YouTube, Maps, etc.), and anywhere structured data needs to flow between nodes. Object values can themselves be lists, nested objects, or any other type.

How data flows between nodes

When a node runs, Runchat collects the data from each input parameter (always as an array) and passes it to the node’s calculation function. If a parameter has multiple items, the node processes each one and returns a matching list of outputs. You control how lists are processed at each input with the list handling chip on the input row: Each, All or Flatten. It determines whether items are processed individually, processed all at once, or flattened from nested arrays. See Data Matching for the full behaviour.

Next steps

  • Data Matching: how Each, All and Flatten control list behaviour across multiple inputs
  • Data Types: the type each value carries and how casting works
  • Loops: pass output back upstream for recursive workflows