> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/helmutfx/streams/main-functionalities/add-stream.md).

# Add Stream

Opens the Add New Stream dialog for entering the name, the host and the trigger of the stream to be created. By clicking on "Cancel" the dialog can be ended and via "Save" the category is created.

![Add Stream Button](/files/NKdKKOTvJDEjTSVEq2a5)

<figure><img src="/files/Stoq2EB8Pmt74iBrUx5s" alt=""><figcaption><p>Add new stream dialog</p></figcaption></figure>

### Name:

Shows the assigned name of the stream. Clicking on the name opens the stream engine which can be used to edit the stream.

### Event:

In order to identify the particular event trigger of a stream, the column **Event** is displaying the related trigger. The corresponding entry can be every trigger in FX, e.g. CONNECTED or CUSTOM\_FX. By clicking a certain trigger in that table view the list will be filtered by that type of event.

### Stream Host:

In general there are two types of streams - **server streams** and **client streams**. The stream's host can be set when a stream will be added. In case the host for an existing stream needs to be changed, this can be edit afterwards in the event trigger for a certain stream.

In case the host is the server, the server will perform all operations in the stream. On the other side  all operations are performed by the workstation over which the stream was triggered, when the host will be the client.

A server stream in the table view can identified by the following icon:

![Icon for Server Stream](/files/YsEVzmWniNZLwusegYXL)

A client stream in the table view can identified by the following icon:

![Icon for Client Stream](/files/bTkEWdlAfoBn2QSP0ueD)


---

# 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.helmut.de/helmut4-releases/v4.6.0/helmut4-components/helmutfx/streams/main-functionalities/add-stream.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.
