Skip to main content

TCP Activities

Use the TCP group for integrations that exchange framed byte payloads directly with a TCP endpoint.

Available activities​

ActivityPurpose
TCP ConnectionDefines the host, port, keep-alive behavior, timeouts, and optional TLS settings
TCP ClientSends bytes and optionally reads a framed reply

Configure a TCP request​

  1. Add a TCP Connection resource and configure the endpoint.
  2. Enable TLS when the server supports it and configure the required certificate trust.
  3. Add TCP Client and select the connection.
  4. Map the outbound payload in the encoding expected by the target system.
  5. Configure reply framing and timeouts when a response is expected.
  6. Test with representative binary and boundary-size payloads.

TCP is a transport rather than a message format. The workflow and receiving system must agree on encoding, framing, maximum size, and whether a response is expected.

Troubleshooting​

  • A timeout can indicate an unreachable endpoint, incorrect framing, or a server waiting for more bytes.
  • Truncated or combined messages usually indicate a framing mismatch.
  • TLS handshake failures commonly result from certificate trust, protocol, or hostname mismatches.
  • Retrying a send can duplicate a business operation unless the application protocol provides idempotency.