> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/toolbox/communication/mqtt/mqttsubscribe.md).

# MQTT Subscribe

## Overview

![The MQTT Subscribe Node.](/files/9PEKHdGxnbIDqjetUp2b)

The **MQTT Subscribe** subscribes to all specified `Topics`, which [**On MQTT Topic**](/incari-studio/toolbox/communication/mqtt/events/onmqtttopic.md) is then able to receive, based on the chosen configuration in [**Project Settings**](/incari-studio/modules/project-settings/mqtt.md). `Topics` are *strings* that act as filters for *Messages* and are hierarchical, meaning there are different levels. Remember, they are case sensitive.

[**Scope**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2025.1/toolbox/communication/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The MQTT Subscribe Node Attributes.](/files/6FOB5qocfpEMVqiX3kgm)

| Attribute       | Type           | Description                                                       |
| --------------- | -------------- | ----------------------------------------------------------------- |
| `Configuration` | **Drop-down**  | The connection, or signal name, that will be used.                |
| `Topic`         | **User Input** | The key in the **MQTT** key/value pair, in the form *Topic/name*. |

## Inputs

| Input             | Type      | Description                                                           |
| ----------------- | --------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**. |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [**MQTT Start**](/incari-studio/toolbox/communication/mqtt/mqttstart.md)
* [**MQTT Stop**](/incari-studio/toolbox/communication/mqtt/mqttstop.md)
* [**MQTT Publish**](/incari-studio/toolbox/communication/mqtt/mqttpublish.md)

## External Links

* [*An in-depth explanation of Topics*](http://www.steves-internet-guide.com/understanding-mqtt-topics/#:~:text=%20Understanding%20MQTT%20Topics%20%201%20The%20%24SYS,publish%20to%20an%20individual%20topic.%20That...%20More%20)


---

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

```
GET https://docs.incari.com/incari-studio/toolbox/communication/mqtt/mqttsubscribe.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.