> 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/template-node.md).

# Template Node

### What is a Template Node?

A Template Node allows user to control how information is presented before it is shown to a user or sent somewhere else (such as email, report, or message). Instead of passing raw or unstructured data that comes from any node, users can turn it into something standardized or readable to their liking.

<figure><img src="/files/N16anTmAdEi3gSnN7UOU" alt=""><figcaption></figcaption></figure>

This node is typically connected to upstream nodes that supply data, enables users to format that data in a preferred structure, and passes the formatted output to downstream nodes that rely on it.

<figure><img src="/files/5yAIusXumr9NRykFSNE8" alt=""><figcaption></figcaption></figure>

Typically, this node is further connected to nodes that display or send information, such as:

* an [Output node](/workflow-builder/outputs/output-node.md) (showing results to the user), or
* some Send Email node, such as [Gmail](/workflow-builder/apps/gmail.md) node (sending formatted content via email), or
* some Send Message node, such as [Teams](/interface-and-deployment/end-user-interfaces/microsoft-teams.md) node (sending formatted messages via some messaging app), etc.

The benefits of the Template Node is that it facilitates:

* formatting output from any node before sending it onward
* reusing information from across the workflow, and combining them

  <figure><img src="/files/jc31f4Td3Nx84FDorQyr" alt=""><figcaption></figcaption></figure>
* using existing, standardized templates by uploading them directly to the workflow<img src="/files/SR3hpEyadjFO4QHcUvcu" alt="" data-size="original">


---

# 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/template-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.