# TCP Send

## Overview

![The TCP Send Node.](/files/2Qoy8azfbpWwZ92ntfEU)

**TCP Send** takes a `Message` and passes it through the currently established **TCP** connection to the endpoint.

Note that if a connection has not been established, a new one will be attempted to be made before sending the `Message`. However, because of the nature of **TCP**, the `Message` will not send if no connection was made prior to execution.

**TCP 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 **TCP Send** 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/tcpconnectionsmanager.md) to find out more information.

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

## Attributes

![The TCP Send Node Attributes.](/files/wfSk61B2J05yB5HALbti)

| 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 *TCP* server, which refers back to the selections made under *TCP* in the [**Project Settings**](/incari-studio/2023.1/modules/project-settings/tcp-connection.md). |

## Inputs

| Input             | Type       | Description                                                           |
| ----------------- | ---------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**  | A standard **Input Pulse**, to trigger the execution of the **Node**. |
| `Message`         | **String** | The `Message` 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

* [**TCP Guideline**](/incari-studio/2023.1/toolbox/communication/tcp.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/tcp/tcpsend.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.