Output

The Output node defines the answer that goes back to the person who ran the flow, or to the system that called it through the API.

A flow without an Output node runs to completion and delivers no result at all.

Declare the fields

On the canvas, the node shows the keys that will be returned. The format follows the flow's purpose:

• A single text field suits a conversational flow, with a single answer. An answer field is usually enough.
• Several fields suit a data automation. An extraction flow can return summary, status and extracted_data separately.

Separate fields are what let another system consume the result without having to interpret free text.

What doesn't go through the output

Everything the flow produced is recorded in the run, step by step, even what wasn't declared here.

More than one output

A flow with branches can have one Output node per branch. Each path delivers its own result, and only the branch actually taken returns something.

The alternative is to bring the branches together in an Aggregation node before a single Output, which keeps the flow's contract stable.

Next steps

• See where the data comes from in Input.
• Bring branches together before the output in Logic.