> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/functions/output.md).

# Output

The output of a function reflects its return value, typically generated after the function's action has been completed. Depending on the nature of the function, the output can take various forms:

* Data (string, number, integer, boolean, array, object)
* Files
* Images

{% hint style="info" %}
The return value of certain function, their output, may also only indicate the success or failure of the function's exectuion, typically represented as `true` or `false`.
{% endhint %}

## Utilizing output

Function output data can be utilized in many ways. It can:

* **Become input for another function:** Serve as an input argument for another function to build a [flow](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/functions.md#flows).
* **Trigger functions:** Initiate the execution of one or more functions.
* **Visualize data in widgets:** Processed in [display widgets](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/ui-widgets-and-elements/display-widgets.md) for UI presentation.
* **Set widget behavior properties:** Influence the behavior properties of a widget.

Furthermore, through [function extensions](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/functions.md#extensions), an output can automatically be:

* **Modified with custom code:** Processed with custom code to generate [modified data](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/function-extensions/modifier.md).
* **Filtered with code:** Subjected to code [filters](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/function-extensions/filter.md) to control flow interruption or continuation.
* **Recorded in** [**InfluxDB**](/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-and-file-storage/internal-influxdb.md)**:** Automatically recorded in the InfluxDB for storage.


---

# 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.heisenware.com/~/changes/eYCCpn9cCBKOYnZA6a8f/building-apps/data-processing/functions/output.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.