# Socket.IO Subscribe

## Overview

![The Socket.IO Subscribe Node.](/files/cjINd1CHgtQbH9HK0Zcj)

The **Socket.IO Subscribe Node** starts listening to the specific **Socket.IO** event given. This means that the server filters for the desired data with the particular `Namespace` and `Event name`.

**Socket.IO Communication** in **Incari** is available as a plugin and is enabled as default. However, in the case that it is disabled in the **Plugins Editor**, it will not appear in the **Project Settings** and **Socket.IO Subscribe** will not show up in the [**Toolbox**](/incari-studio/2023.1/toolbox/overview.md). Please refer to the [**Plugins Editor**](/incari-studio/2023.1/modules/plugins/communication/socketiomanager.md) to find out more information.

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

## Attributes

![The Socket.IO Subscribe Node Attributes.](/files/ewtmbOTAB4mp3GyirzVz)

| Attribute       | Type          | Description                                                                                                                                                                           |
| --------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration` | **Drop-Down** | The desired *Socket.IO* server, which refers back to the selections made under *Socket.IO* in the [**Project Settings**](/incari-studio/2023.1/modules/project-settings/socketio.md). |

## Inputs

| Input             | Type       | Description                                                                                                          |
| ----------------- | ---------- | -------------------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**  | A standard **Input Pulse**, to trigger the execution of the **Node**.                                                |
| `Event Name`      | **String** | The identifying name of the **Socket.IO** event.                                                                     |
| `Namespace`       | **String** | An identifying name that is *parent* to an event or events in the **Socket.IO** protocol. The default is simply `/`. |

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

* [**Socket.IO Unsubscribe**](/incari-studio/2023.1/toolbox/communication/socketio/socketiounsubscribe.md)


---

# 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.incari.com/incari-studio/2023.1/toolbox/communication/socketio/socketiosubscribe.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.