# Node Pallet

The node palette lists all available actions, conditions, outputs and wildcards and enables you to find the desired node / wildcard using a search field. An entered search leads to the number of available conditions / actions / outputs and wildcards being displayed directly.

<figure><img src="/files/QwG8d5ikqQmgimMy2B9W" alt=""><figcaption><p>Node pallet conditions &#x26; actions</p></figcaption></figure>

### Selection Tab:

It is possible to switch between the individual tabs, whereby the affiliations are sorted by type. For example, there are 31 conditions in the system which are divided into 6 types. Project-related conditions, user-related conditions, file and folder-related conditions, etc.

<figure><img src="/files/fCg4wYtT8k8P260UCXU7" alt=""><figcaption><p>Type related wildcards</p></figcaption></figure>

### Available Number:

The number of available nodes / wildcards is displayed next to the name of each tab. This changes as soon as a search is applied. This makes it possible to immediately see how many nodes / wildcards are available according to the search.

### Type Relation:

If a tab is selected (for example Consitions) the corresponding types are displayed under the search field. This view changes per tab, since not all wildcards have the same types of affiliations.By clicking on of the types. If one of the types is clicked, another view opens, in which the actions / wildcards assigned to the type are displayed.

### Description Icon:

If you move the mouse over this icon, a description field opens in which the individual parameters of the respective node are displayed, as well as the function of the node and what it can be used for.

### Search Field:

Free text field to search for a wildcard / node. As soon as something is entered in this field, all tabs are filtered and the number of results per tab is automatically adjusted. The affiliation by type is then no longer visible.

### Available Type

The number next to the respective type shows how many nodes / wildcards are available for this type.


---

# Agent Instructions: 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:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/layout/node-pallet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.