# WebSocket Client Send

## Overview

![The WebSocket Client Send Node.](/files/vFUVlQxeZzF0eiLipDL8)

The **WebSocket Client Send Node** sends a message via the open *WebSocket* connection specified in `Configuration`.

**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 Send** 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.

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

## Attributes

![The WebSocket Client Send Node Attributes.](/files/5iAiMZ3HUCDl7FvgaCxd)

| Attribute       | Type         | Description                                                                                                                                                                                               |
| --------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Is Binary`     | **Bool**     | A boolean which allows the user to choose whether the returned message is in **String** or binary format. If it is toggled on (*true*), it will be **Binary**. If off (*false*), it will be a **String**. |
| `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**.                                                                                                                     |
| `Message`         | **String** or **Bool** | The desired message to be sent through the chosen *WebSocket* connection. If `IsBinary`is toggled off, it will remain a **String**. If it is toggled on, it will be in **Binary** format. |

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

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