> 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/reference/functions.md).

# Functions

A function is one piece of code your logic can call: `read` of the OPC UA client, `increment` of the counter. Functions come in classes, and agents offer them: the platform's internal agents, the add-ons you install, and the agents you run in your own network. Drag a function from the [Functions explorer](https://docs.heisenware.com/app-builder/app-builder/functions.md) onto the Flowboard and it becomes an executor.

The pages here are the reference: for every class its functions, their parameters, what they return and what they do.

* [Connectors](https://docs.heisenware.com/reference/functions/connectors.md): machines, protocols and business systems. OPC UA, Modbus, S7, MQTT, HTTP, email, SAP and the rest.
* [Storage](https://docs.heisenware.com/reference/functions/storage.md): the relational and the timeseries database, the [file store](https://docs.heisenware.com/reference/functions/storage/files.md), and the in-memory stores (buffer, data store, accumulator).
* [Utilities](https://docs.heisenware.com/reference/functions/utilities.md): data processing, timers, counters, cron, simulation, barcodes, PDFs, users.
* [Add-ons](https://docs.heisenware.com/reference/functions/add-ons.md): extra classes that arrive with a container of their own.

The explorer groups the same classes under **Connectors**, **Storage**, **Utilities** and **Custom**, which holds your [subflows](https://docs.heisenware.com/concepts/subflows.md). An add-on and an agent of your own appear under their own name.

## How to read a function page

A class offers its functions in a few kinds, and the page says which one each is:

* **static function**: it needs no instance. Call it and it answers.
* **constructor** (`create`) and **destructor** (`delete`): they bring an instance into being and end it.
* **instance function**: it acts on one instance, the one the executor's address names.
* **event function**: it is called once and then delivers values as they happen, on the executor's event outputs. See [Backend events](https://docs.heisenware.com/concepts/backend-events.md).

Most connectors stand for something that lives on: a connection, a server, a port. That is the **instance**, created once with `create` and reached by its name from every App of the workspace. [Executors and instances](https://docs.heisenware.com/concepts/executors-and-instances.md) explains what that means for your flows, and [Triggers and wires](https://docs.heisenware.com/concepts/triggers-and-wires.md) when an executor runs.

A function's own documentation also sits in the Builder: hover an executor to read it, and the assistant reads the same text before it wires anything.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.heisenware.com/reference/functions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
