Skip to main content
External data provides a flexible key-value store for attaching arbitrary JSON data to a document. This is separate from the hierarchical content node structure and is ideal for storing processing results, cached computations, or any structured data that doesn’t fit into the node tree.

Overview

External data features:
  • Named Keys: Organize data under different keys (default key is “default”)
  • JSON Values: Store any JSON-serializable data structure
  • Document-Level: Data is attached to the document, not individual nodes
  • Persistence: Saved with the document in KDDB format

Setting External Data

Basic Usage

Complex Data Structures

External data supports any JSON-serializable structure:

Retrieving External Data

Get by Key

List All Keys

Updating External Data

Setting external data with the same key replaces the previous value:
External data replacement is atomic at the key level. To merge data, read the existing value first, merge in your changes, then write back.

Merging Data

Use Cases

Caching Computed Results

Store expensive computation results to avoid recalculating:

Storing Processing State

Track workflow state across multiple processing steps:

Multi-Model Results

Store results from different ML models:

External Data vs Metadata