> 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/app-builder/app-builder/flowboard.md).

# Flowboard

The Flowboard holds the logic of the whole App: what it fetches, computes, stores, and sends to machines and other systems. It runs even when nobody has a page open.

You build it by dragging functions onto the board, where each becomes an [executor](https://docs.heisenware.com/concepts/executors-and-instances.md), and wiring the executors together.

## Putting executors on the board

* **From the Explorer**: drag a function out of the [Functions explorer](https://docs.heisenware.com/app-builder/app-builder/functions.md) and drop it on the board.
* **From the toolbar**: **New Echo Executor**, the first icon, drops an `echo`, the carrier that hands a value on unchanged. The other everyday functions sit in the Functions explorer under *Utilities*: [Data Processing](https://docs.heisenware.com/reference/functions/utilities/data-processing.md) holds `combine`, `jsonParse` and the rest, [Event Simulation](https://docs.heisenware.com/reference/functions/utilities/event-simulation.md) the impulses.
* **Duplicate**: select executors or a section and use **Duplicate** in the toolbar.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-961514f940ed1a1fee223620bd97d87cc54ac5e1%2Fdrop-a-function-on-the-board.gif?alt=media" alt="A function is dragged out of the Functions explorer and dropped on the board, where it becomes an executor"><figcaption><p>A function dropped on the board becomes an executor</p></figcaption></figure>

## Wiring

Drag from an item of one executor and drop it on an item of another. What the wire does depends on where it lands:

* **Output to input**: the value arrives at that argument. That alone does not run anything.
* **Output to trigger**: the second executor runs when the first produces. No value is handed over.
* **Own input to its own trigger**: a **hot input**. Every value that arrives there runs the executor, whoever wrote it: a wire, a widget, the Player.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-a6102ed6321eb69b38805b6a913fbbfacc0fe00f%2Fwire-a-hot-input.gif?alt=media" alt="An output is dragged onto another executor&#x27;s input, which draws the wire; then that input is dragged onto its own trigger, which comes to read on input update"><figcaption><p>First the wire, then the same input dropped on its own trigger</p></figcaption></figure>

Dropping on a trigger adds the source with *update* and opens its menu at once, so you can switch to *change*, *true* or *all updated*. A page dropped on a trigger makes it *on page load*; a widget dropped on it makes a widget event.

{% hint style="warning" %}
A value arriving at an input never runs an executor by itself. Something has to trigger it. See [Triggers and wires](https://docs.heisenware.com/concepts/triggers-and-wires.md).
{% endhint %}

What happens when several wires meet, and which user sees which value, is in [When streams meet](https://docs.heisenware.com/concepts/when-streams-meet.md) and [Scopes](https://docs.heisenware.com/concepts/scopes.md).

## What sits on an executor

* The **trigger** on the left: the list of reasons to run. Right-click it for **App Start** with its interval, **App Stop**, **Process One By One**, **Delay execution**, and on a subflow blueprint **Time out**. A click runs the executor once.
* The **inputs**, in the order of the function's arguments. Right-click one for **Secret Input**, **Insert Variable** or **Clear Content**.
* The **outputs** on the right: the return, and one event output per value an event or a callback delivers. See [Backend events](https://docs.heisenware.com/concepts/backend-events.md).
* **Extensions** on any output: [modifier](https://docs.heisenware.com/app-builder/app-builder/flowboard/modifier.md), [filter](https://docs.heisenware.com/app-builder/app-builder/flowboard/filter.md), [recorder](https://docs.heisenware.com/app-builder/app-builder/flowboard/recorder.md) and [error handler](https://docs.heisenware.com/app-builder/app-builder/flowboard/error-handler.md). The **+** on the output adds one.
* The [**status dot**](https://docs.heisenware.com/concepts/executors-and-instances.md#status) on the header, and the executor's **comment**, the line you write to say why the node is there. Right-click the executor for **Add Comment**, **Publish as Endpoint…**, the address entries, **Clear Cache** and **Delete Executor**.

## Sections

A section is a titled, colored frame around the executors of one stage. Select two or more executors and click the group icon in the toolbar; with a section selected as well, the same icon adds them to it, and selecting framed executors lets it release them again. An executor belongs to at most one section.

A frame can be collapsed, and the toolbar folds or unfolds every section at once. Sections are a visual aid: the logic never sees them, and a released App does not carry them.

A section can become a reusable executor of its own: **Activate Subflow** on its title bar. **New Subflow** in the toolbar drops an empty one, a section with its blueprint ready. See [Subflows](https://docs.heisenware.com/concepts/subflows.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-f7f0aa61963b10c1b6377b9ccdbe23ea8867cb80%2Fframe-a-section.gif?alt=media" alt="Two executors are selected with Ctrl and a click, and the group icon draws a titled frame around them"><figcaption><p>Select the executors of one stage, then the group icon</p></figcaption></figure>

## Annotations

Place documentation cards anywhere on the board with the annotation tool, for example to sketch the architecture of an App, explain a path that spans several executors, or leave instructions for other members.

A card holds rich text: headings, lists, tables, quotes, code blocks, links, and pictures from the media library. Double-click a card to edit it; a code block in the `mermaid` language is drawn as a diagram. **Card colour** in the editor's header tints it, for example in the color of the section it explains. Cards keep the width you give them and grow with their content. Zoomed out, the text lifts a little to stay legible but never leaves its card.

Annotations say what no single node can say. Why one executor is there belongs in its comment.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-89f02de6cdd53614d17de3c30e036bc7658a82d4%2Fflowboard-annotation.png?alt=media" alt="An annotation card with a heading, a paragraph, a mermaid flowchart and a list, tinted in the colour of its section"><figcaption><p>A card explaining a path that spans several executors, with a <code>mermaid</code> block drawn as a diagram</p></figcaption></figure>

## Finding your way

* **Panning**: trackpad, the mouse wheel for vertical and Shift with the wheel for horizontal movement, or the WASD keys.
* **Zooming**: pinch, Ctrl with the mouse wheel, the toolbar's **Zoom In** and **Zoom Out**, or the Q and E keys.
* **Fit**: **F**, or the fit icon. With something selected it frames the selection.
* **Trace**: select one executor or extension and the toolbar offers **Trace Upstream** (left Alt and click), **Trace Downstream** (right Alt and click) and **Trace Full Stream**. The board then highlights what feeds this node, what it feeds, or both.

Pan and zoom behave the way the [App Builder settings](https://docs.heisenware.com/app-builder/app-builder.md#settings) say.

## Tidying up

The board previews every layout change before it keeps it: moved nodes turn orange, and the toolbar offers **Accept Layout Shifts** (the check) and **Discard Layout Shifts** (the arrow).

* **Clear Collisions**: moves nodes just far enough apart to remove overlaps.
* **Auto-Format All**: rebuilds the whole layout, grouping connected logic into islands. With a selection it formats the selection alone.
* A new node that lands on top of others pushes them aside the same way.

## Search and replace

Select at least two executors to activate **Replace** in the toolbar, then replace a string across the whole selection, for example a machine's IP address or an instance name.

{% hint style="warning" %}
The replacement runs over everything the selected executors hold, their cached values included. Search for something distinctive, and look at the result before you build on it.
{% endhint %}

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-f32f5cb262c99a72e82b80b1b105a498286f3987%2Fsearch-and-replace.gif?alt=media" alt="With two executors selected, Replace asks for the string and its replacement and rewrites both"><figcaption><p>The oven controller moved to another address, in both executors at once</p></figcaption></figure>


---

# 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/app-builder/app-builder/flowboard.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.
