# UDP Send

## Overview

![The UDP Send Node.](/files/NvTkcFod7XysMB4Q37AL)

**UDP Send** takes a `Message` and passes it through the currently established *UDP* *connection*. This *connection* can be set using the [UDP guideline](/incari-studio/2022.2/toolbox/communication/udp.md#udp-guideline).

Note that if a *connection* has not been established, a new one will be attempted to be made before sending the `Message`. Because of the nature of *UDP*, this is possible and the `Message` will send after the new *connection* is established.

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

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

## Attributes

![The UDP Send Node Attributes.](/files/aeWpmG7OGwrBu580OgQq)

| Attribute       | Type          | Description                                                                                                                                                                     |
| --------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Is Binary`     | **Bool**      | Can be toggled on or off depending on if the `Message` body is binary or not.                                                                                                   |
| `Configuration` | **Drop-Down** | The desired *UDP* server, which refers back to the selections made under *UDP* in the [**Project Settings**](/incari-studio/2022.2/modules/project-settings/udp-connection.md). |

## Inputs

| Input             | Type       | Description                                                           |
| ----------------- | ---------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**  | A standard **Input Pulse**, to trigger the execution of the **Node**. |
| `Message`         | **String** | The *datagram* to be sent to the endpoint.                            |

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

* [Introduction to UDP Nodes](/incari-studio/2022.2/toolbox/communication/udp.md#introduction)


---

# 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/2022.2/toolbox/communication/udp/udpsend.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.