Output Data

Every node produces output data when it executes. You can inspect this data to verify your workflow is working correctly and to debug issues.

Viewing Output

1. After a workflow executes, click on any completed node
2. The output panel shows the data that node produced
3. Each item is displayed as a JSON object

Pagination

For nodes that produce many items (e.g., database queries returning hundreds of rows), output is paginated:

• Items are stored in chunks of up to 2,000 items per chunk
• Use the pagination controls to browse through results
• Each item is displayed individually for easy inspection

Output Structure

Node output is typically an array of items. For example, a database query might produce:

[
  { "id": 1, "name": "Alice", "email": "alice@example.com" },
  { "id": 2, "name": "Bob", "email": "bob@example.com" },
  { "id": 3, "name": "Charlie", "email": "charlie@example.com" }
]

Each item appears as a separate entry in the output viewer with its own index number.

Streaming Output

Nodes that support streaming (like SFTP Stream Read) produce output incrementally. Depending on the execution mode:

• Piped mode — items stream to downstream nodes as they're produced, and output data appears incrementally in the viewer
• Gated mode — all items are collected first, then available as a complete dataset

Data Flow Between Nodes

Output from one node becomes input for connected downstream nodes. The edge between nodes determines which output handle feeds which input:

• Most nodes have a single output handle
• Conditional nodes (like Switch) route items to specific handles
• Only items that reach a node's connected handle are processed