Viewing a Node's Data Shape in the Workflow Builder

Viktor Ristic
Viktor Ristic
  • Updated

Overview

When writing TypeScript in a node's mapper or condition function, you often need to know exactly what fields an upstream node produces before you can reference them. The View data details panel shows the inferred shape of that data — field names, types, and whether they're required — directly from the chart, without running the workflow.

In this article, we'll be covering how to open the data details panel, how the information is organized, and how it differs from the data you see in a workflow execution.

 

Opening the data details panel

  1. Open your workflow in the builder
  2. Hover over a node on the chart to reveal its kebab (⋮) menu
  3. Click View data details

 

Reading the data details panel

The panel is split into two sections:

  • Node input state — the data available to this node, organized into three groups
  • Node output — the data this node produces

Node input state groups upstream data into:

  • Latest step — the node or nodes that run immediately before this one
  • Previous steps — every other node earlier in the chart
  • Context data — state fields outside of steps, such as the trigger's own fields (for example objectId or input)

Each node appears as a card you can expand to see its field tree, with the type of each field. A card with no output shows "No fields." A group with nothing to show — for example, a node placed right after the trigger has no previous steps — is hidden rather than shown empty.

Some node types don't expose an inferable output shape. In that case, you can set one explicitly using Configure output schema on the node's side panel.

 

Understanding shape vs. actual data

The data details panel shows the shape of your data — field names and types — inferred from node configuration, without running anything. It does not show real values from an execution.

To see the actual data produced by a specific run, use the execution history instead. See Understanding Workflow Executions.

 

Understanding limitations

  • Very deeply nested schemas may not load in full — a warning appears when some fields were left out.
  • If the data shape can't be loaded at all, the panel shows an error state.

Related to

Was this article helpful?

Have more questions? Submit a request