> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/workflow-builder/outputs/output-node.md).

# Output Node

### What is an Output Node?

An Output node displays the results generated by other nodes in your workflow. It acts as the final delivery point in your data pipeline, where outputs from processing nodes (like LLMs or data processors) are shown to your users.

The Output node is typically connected to nodes that generate textual or structured responses, such as:

1. **LLM nodes** (to display answers or messages).
2. **Knowledge Base nodes** (to show retrieved documents or summaries).

Key benefits of the Output node:

* Provides a clear way to present results to end-users.
* Enables visibility into the results of data transformations or AI completions.
* Supports dynamic interfaces when exposed via the **Export** tab.

### How to expose Outputs externally?

To allow users to see the Output node results:

1. Go to the **Export** tab.
2. Enable the Output node in the **Outputs** section under **Fields**.
3. Click **Save Interface**.
4. The Output node’s results will now appear in your external interface when the workflow is triggered.

### What to expose in the Output node?

With the Output node, you will be able to plot the result coming out of any other node.

Here are a few quick facts:

* **Markdown:** The output node uses Markdown to format the text. You can use it to add links, imgs, headings, and more.
* **Length:** While output can have any length, you should be mindful that LLM prompts have a limit on how many words they can result.
* **Intermediate Outputs:** Use intermediate Output nodes to debug your workflow: for example, connect it to a vector store to see what chunks of text are returned.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stackai.com/workflow-builder/outputs/output-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.