# Chat

> Chat nodes for modeling conversational experiences in Maestro Flow, covering routing control, conversational AI turns, and deterministic messages.

The **Chat** nodes build a conversational Flow. Once deployed, it reaches end-users through **[every chat channel](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-deployment)** supported for conversational agents — iFrame embeds, Assistant, Microsoft Teams, Slack, and custom surfaces built with the UiPath TypeScript SDK. Monitor its performance, metrics, and user feedback through **[chat agent observability](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-observability)**.

## Available nodes

| Node | What it does |
|---|---|
| [Conversation Trigger](./node-conversation-trigger.md) | Marks the Flow as **conversational** and starts it when a user initiates a chat on any channel. |
| [Wait for Message](./node-wait-for-message.md) | Suspends until the user sends a message, then outputs the latest conversation context (chat history) for downstream nodes to consume. |
| [Conversational Agent](./node-conversational-agent.md) | Runs a single chat agent turn. Streams its responses and takes actions through tool-calls. |
| [Send Message](./node-send-message.md) | Writes an arbitrary message to the conversation. Use for fixed replies, routing messages, and emitting data from other nodes to the chat. |
| [Get Conversation Context](./node-get-conversation-context.md) | Reads the current conversation history and metadata without suspending the Flow. Generally not needed, but can be used when a downstream node needs to inspect latest chat messages without waiting for new input. |

## Capability examples

Combine the conversational nodes with the rest of Flow's palette to unlock a variety of capabilities, such as:

* **Deterministic branching** — route to different node paths based on message content or agent output.
* **Agent hand-off** — pass the conversation between multiple conversational agents, each with its own prompt and tools.
* **Parallel branches** — launch any other Flow branches in parallel - such as [human approval tasks](./node-human-task.md) - while the conversation continues seamlessly to the user.
* **Chat termination** — end the conversation when a goal is reached.
* **Zero-agent conversations** — build a fully deterministic chat experience with no LLM turns at all.

## End-to-end walkthrough

Visit **[build a chat agent workflow](./build-a-chat-agent-workflow.md)** for a step-by-step example that combines the chat nodes into an agent-handoff routing pattern.

## Related

* [Chat conversational agents](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-chat) — surface overview in the Agents user guide.
* [Chat deployment](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-deployment) — publish to Orchestrator and expose through Instance Management, Assistant, Teams, Slack, iFrame, or the TypeScript SDK.