Overview
The Result node is a terminal viewing node in a Weave Workflow. It displays the upstream data as a table in the canvas — without writing to any destination. Result accepts one input from an upstream node and produces no downstream output; running the Workflow populates the Result node’s display with the final processed data. Result is the design-time companion to Output: where Output persists data to a Datasource or Connector destination, Result simply shows what the Workflow produces.
Result nodes are added to Workflows from the node panel on the Design canvas, under the Data category alongside Data Import and Output. The node has no configurable settings per source content — drop it on the canvas, connect an upstream input, and run.
Note: “Workflow” is the in-UI term for what some Weave documentation calls a pipeline. This reference uses “Workflow.”
When to use it
- Verifying that a Workflow’s transformation chain produces the expected output during authoring.
- Spot-checking intermediate or final data without committing to a destination write.
- Demonstrating a Workflow’s behavior to stakeholders during design review.
- Debugging Workflow logic — connect Result at different branch points to see what each section of the Workflow produces.
- Cases where the analytical goal is inspection only, with no persistent destination needed.
Result vs. Output
Result and Output are the two terminal node types in a Weave Workflow. They serve different purposes; understanding the distinction is essential to Workflow design.
| Primary purpose | Inspection during design-time | Persistent write to a destination |
| Destination | None — displays in the canvas only | Datasource (database table) or Connector (file) |
| Write modes | Not applicable | Override, Append, Update, Upsert |
| Data persistence | Not persisted; closes with the Workflow session | Persisted at the configured destination |
| Configuration | None | Destination, write mode, primary key (Update/Upsert), columns, file settings |
| Use during | Authoring and debugging | Scheduled or triggered Workflow runs |
| Multiple per Workflow | Supported — connect at different branch points to inspect intermediate data | Supported — fan-out to multiple destinations |
Key behaviors
Result is terminal and view-only. The Result node displays its upstream data in the canvas. It accepts no downstream connections and writes nothing to any external destination. The Workflow ends at the Result node from a data-flow standpoint, though additional Output nodes can also be present terminating the same upstream branch points.
No configuration. Per source content, Result has no configurable settings — no destination, no mode, no schema controls. The node’s behavior is fully determined by what flows into it from upstream. This makes Result the simplest node type in the Workflow family.
Multiple Result nodes for branch inspection. A Workflow can include multiple Result nodes connected at different points in the transformation chain. This lets Designers inspect what each section of the Workflow produces — a Result node after Data Import shows the raw input; a Result node after a Filter shows the post-filter rows; a Result node at the end shows the final output. Useful for debugging.
Coexists with Output. Result and Output are not mutually exclusive — a Workflow can have one or more Result nodes for design-time inspection alongside one or more Output nodes for persistent destination writes. They consume the same upstream data; their treatment of it differs (display vs. write).