> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2023.1/toolbox/communication/tcp/events/ontcppacketreceive.md).

# On TCP Packet Receive

## Overview

![The On TCP Packet Receive Node.](/files/XTsvcz6V9zKH0uNSRr1e)

**On TCP Packet Receive** is an **Event Listener Node** that listens to an established **TCP** connection and outputs the `Message` data given, therefore enabling the user to trigger a **Logic Branch** when the `Message` is received.

**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 **On TCP Packet Receive** will not show up in the [**Toolbox**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2023.1/toolbox/communication/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 On TCP Packet Receive Node Attributes.](/files/VVeTQ4nbX6oQUBOsUvHY)

| 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). |

## 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. |
| `Message`          | **String** | The returned `Message`.                                                                                                                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.incari.com/incari-studio/2023.1/toolbox/communication/tcp/events/ontcppacketreceive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.