Skip to content

Static Data Node

Static Data lets you keep a small tabular dataset inside the workflow config. You edit cells in the node editor, paste from a spreadsheet, or import CSV/TSV/Excel once. Downstream nodes read the output port like any other tabular source.

Unlike File Input, Static Data does not keep an uploaded file, engine file attachment, or past-file history after the grid is in the node. The grid in config is the source of truth.

  • Lookup / replace / map tables that belong with the workflow template
  • Collapsing stacks of per-field replace operations into one lookup-driven transform
  • Small to medium tables you want versioned with the workflow

Use File Input when the dataset is a large operational file that belongs on disk or the engine file store.

  • Open the node editor Static Data tab for VirtualDataGrid editing
  • Paste from Excel, Google Sheets, or LibreOffice at the selection (TSV, CSV, ;-separated locales, and HTML table clips)
  • Import CSV, TSV, or XLSX (pick one sheet for multi-sheet workbooks). Import replaces the entire grid; you confirm when the grid is non-empty
  • Clear grid keeps column definitions and empties all rows
  • Shift-click selects a row range; Delete or Backspace removes selected rows (row menu Delete also covers the selection)
  • Column types sit on each header (string by default, or number, boolean, date). Paste and import coerce into the declared type and fail closed on bad values

Wire Static Data output into another node’s input. New canvas wires default to mergeStrategy: "lookup" (switch to Auto-Merge on the Ports tab if you need a row merge). Operations, filter, compute, Jinja, and AI nodes already consume that lookups map. On an Operation node, add the Lookup transformation to match a primary field to a lookup column and copy selected columns (take: [{ column, as? }]) without writing a custom function. You do not need a siphon port or a dedicated lookup handle.

Explore templates Static Data Replacements and Multi-table Lookup Enrichment show stacked Lookup ops against one or more Static Data tables.

Canvas agents can create and update Static Data nodes (canvas_createStaticDataNode / canvas_updateStaticDataNode), wire lookup edges (Static Data to main input defaults to lookup), and add Lookup transforms on Operation nodes. Prefer Lookup over a custom function that reads lookups.

The natural-language Operations composer also emits Lookup (lookupKey, match fields, and take columns). Re-seed agents and skills after platform updates so those prompts stay current.

The card shows a small aspect-ratio grid preview (same layout language as Subgrid) plus row×column counts. Edit in the node editor, not on the card.