> For the complete documentation index, see [llms.txt](https://docs.helmut.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.cloud/high5/stream-designer-studio/node-catalogs.md).

# Node Catalogs

Node Catalogs organize nodes into logical groups based on their source, functionality, or integration. They help users quickly find and use the appropriate nodes when building streams in the Stream Designer Studio (SDS).

You can access Node Catalogs from the left sidebar by clicking **Nodes**.

### Catalog Structure

The Node Catalog is organized into:

* **Catalog Provider** – The source of the nodes (for example, helmut.cloud or Cosmo Catalog)
* **Categories** – Functional groupings within a catalog
* **Nodes** – Individual components that perform specific actions

This structure helps organize nodes in a clear and scalable way.

### Using Nodes from a Catalog

To use a node from a catalog:

1. Open the **Nodes** panel in the left sidebar.
2. Expand the desired catalog (for example, helmut.cloud or Cosmo Catalog).
3. Expand a category.
4. Drag the node onto the canvas.

Once added, the node can be configured and connected to other nodes.


---

# 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.cloud/high5/stream-designer-studio/node-catalogs.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.