Output

Capture and persist a value as the final result of your workflow run.

Overview

The Output node stores a resolved value as the workflow run's result. It is a terminal node — it has an input handle but no output handle, making it a structural endpoint in your workflow graph.

When the workflow finishes, the output is available in the run history, via the API, and — if the workflow was triggered from chat — directly in the chat message.

Best for: Returning summaries, structured data, extracted values, or any final result from a workflow run.

How it works

1. You configure a value field using a template expression that references outputs from previous nodes.
2. At execution time, the template is resolved — variables like {{agent.output.structured.summary}} are replaced with actual values.
3. The resolved value is persisted in the workflow run's output JSON object, keyed by the node's slug.
4. If the workflow was triggered from chat, the output is pushed back to the originating message so the user sees the result inline.

Multiple Output nodes

A workflow can have more than one Output node. Each one contributes a separate key (its slug) to the run's output object. For example, if you have two Output nodes with slugs summary and actionItems, the run output looks like:

{
  "summary": "Q1 revenue grew by 12% driven by enterprise expansion...",
  "actionItems": "1. Schedule board review\n2. Update forecast model\n3. ..."
}

Configuration

Value

The core field of the Output node. Define what data to capture using a template expression with variables from previous nodes.

{{agent.output.structured.summary}}

You can combine multiple variables and static text:

Report for {{trigger.output.customer_name}}:

{{agent.output.structured.analysis}}

Generated on {{trigger.output.date}}

The Output node currently supports Manual mode only — you write the template expression directly. This gives you full control over exactly what gets returned.

Slug

The slug is the key under which this output is stored. It's auto-generated from the node name in camelCase (e.g., "Final Summary" becomes finalSummary). If your workflow has multiple Output nodes, each must have a unique slug.

Error Handling

Configure how errors are handled if the value cannot be resolved:

Strategy	Behavior
Stop	Workflow stops immediately on error
Callback	Route to an error handling branch
Continue	Continue with error data available

Default: Stop

Chat integration

When a workflow is triggered from chat (either via @-mention or through an agent), the Output node writes its result directly back into the chat message. The user sees the workflow output inline without having to navigate to the workflow run history.

The output appears as a formatted result panel in the chat, showing the workflow name, execution time, and the output content.

If the workflow has no Output node, the chat shows a generic "completed" status instead of a detailed result.

Example

A workflow that analyzes a support ticket and returns a structured response:

**Priority:** {{agent.output.structured.priority}}
**Category:** {{agent.output.structured.category}}
**Suggested response:**

{{agent.output.structured.draft_reply}}

This resolves to the actual values at runtime and is stored as a single string under the node's slug.

Best Practices

Return only the data your consumer needs. If the workflow is triggered from
chat, a concise summary is more useful than dumping all intermediate data.



If your workflow has multiple Output nodes, give them descriptive names so
the output keys are self-explanatory (e.g., `summary`, `recommendations`,
`rawData`).



Use an Agent node to synthesize data from multiple previous steps, then pass
the agent's structured output into the Output node. This keeps your final
result clean and well-formatted.



After running a workflow, check the Output node in the run timeline to see
exactly what value was captured. This helps debug template expression issues.

Next Steps

• Variable Usage — Learn how to reference data from previous nodes

• Agent Node — Generate structured data to feed into outputs

• Workflows in Chat — Trigger workflows from chat and see output inline

• Core Concepts — Understand workflow fundamentals