Files and URLs
Images, videos, audio, 3D meshes, PDFs and other binary files are always uploaded to Runchat’s storage and represented as URL strings. This keeps workflow file sizes small and latency low. When you wire a file output into another node, what flows is the URL, not the file content.Objects
JSON objects are key-value structures used to represent properties of things. Many third-party APIs (language models, YouTube, Maps, etc.) return data as objects, so Runchat works with them natively.Lists and arrays
All parameter data is stored internally as an array. When a parameter holds more than one item, the node shows pagination controls so you can step through inputs and outputs. List behaviour (each, all, flatten) is controlled by depth, not by a separate “list” type. See Data Structure for how depth works.Casting between types
You can connect any two parameters. Runchat casts the value automatically using these rules:- To text: numbers and booleans stringify; messages and contexts extract their text content; images use their flattened URL.
- To number: text parses to a number (0 if not parseable); booleans become 1 or 0.
- To boolean: text “true” (case-insensitive) becomes true, anything else false.
- To object: messages and contexts extract as JSON; images become
{ imageUrl, layers }; text is parsed as JSON. - To message or context: URL strings become image messages; PDFs become file data.
- To URL: extracts the URL from messages or images; text passes through.
- To code, markdown or HTML: extracts code blocks or text from messages.
Type reference
The full list of types Runchat understands. Connect any two and casting is automatic.Text
Numbers and logic
Code and markup
Media
Files and identifiers
Chat
Collections
UI and control
Next steps
- Data Structure: how depth, “each” and “all” control list behaviour
- Data Matching: how Runchat lines up multiple inputs across runs
- Connecting Nodes: drawing edges, references, and published parameters