# WebSocket Client Stop

## Overview

![The WebSocket Client Stop Node.](https://1553081948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU990HLHWA30dTfELtDUK%2Fuploads%2Fgit-blob-03f0077597b0988787c20e23133243b9e917a593%2Fwebsocketclientstopnode20241.png?alt=media)

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**](https://docs.incari.com/incari-studio/toolbox/overview). Please refer to the [**Plugins Editor**](https://docs.incari.com/incari-studio/modules/plugins) 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**](https://docs.incari.com/incari-studio/toolbox/communication/websocket/events/onwebsocketstop) 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.](https://1553081948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU990HLHWA30dTfELtDUK%2Fuploads%2Fgit-blob-d57329b0b1ee5c80f698f93eb1af243761a1b8f6%2Fwebsocketstoponstopexample.png?alt=media)

[**Scope**](https://docs.incari.com/incari-studio/overview#scopes): **Project**, **Scene**.

## Attributes

![The WebSocket Client Stop Node Attributes.](https://1553081948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FU990HLHWA30dTfELtDUK%2Fuploads%2Fgit-blob-7ed969ea6d1d357a5d50a4ec8c60041c1e530304%2Fwebsocketclientstopatts.png?alt=media)

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

## 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**](https://docs.incari.com/incari-studio/toolbox/communication/websocket/events/onwebsocketstop)
* [**WebSocket Client Send**](https://docs.incari.com/incari-studio/toolbox/communication/websocket/websocketsend)