# WebSocket Client Stop

## Overview

![The WebSocket Client Stop Node.](/files/BwE2d3GK206ZnacVL7hp)

The **WebSocket Client Stop Node** halts communication with a **WebSocket** connection.

**WebSocket 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 **WebSocket Client Stop** will not show up in the [**Toolbox**](/incari-studio/toolbox/overview.md). Please refer to the [**Plugins Editor**](/incari-studio/modules/plugins.md) to find out more information.

It is important to note that while the **WebSocket Client Stop Node** stops a **WebSocket** connection, it may not completely finish disconnecting from said connection when the **Node** is executed. This could lead to the **Logic** attached to its **Output Pulse** to not work even though there is technically nothing wrong. In order to avoid this, it is highly suggested to use the [**On WebSocket Stop Node**](/incari-studio/toolbox/communication/websocket/events/onwebsocketstop.md) instead. This way, it is assured that the **Logic** will execute once the connection to the **WebSocket** connection has been terminated.

Again, the user must first use the **WebSocket Client Stop Node** to close the connection. Separately, the **On WebSocket Stop Node** can be used to execute the desired **Communication Logic**.

![WebSocket Client Stop and On WebSocket Stop Configuration.](/files/U5Nmb2ffIWyjr18XpX1w)

[**Scope**](/incari-studio/toolbox/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The WebSocket Client Stop Node Attributes.](/files/XSTezelH0floJrGza4DG)

| Attribute       | Type         | Description                                                                                                                                                          |
| --------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration` | **Dropdown** | The identifying connection name that will be used, which is one that was set up in the [**Project Settings**](/incari-studio/modules/project-settings/websocket.md). |

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

* [**On WebSocket Stop**](/incari-studio/toolbox/communication/websocket/events/onwebsocketstop.md)
* [**WebSocket Client Send**](/incari-studio/toolbox/communication/websocket/websocketsend.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/toolbox/communication/websocket/websocketstop.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.