-
-
Notifications
You must be signed in to change notification settings - Fork 5
Chat Message Node
Vitor Lima edited this page Mar 19, 2026
·
1 revision
The Chat Message node posts a message into the chat. This is how your agent "speaks" — it takes text and a participant, and creates a visible message in the conversation.
| Input | Type | Required | Description |
|---|---|---|---|
| Response | String | Yes | The text content of the message to post. |
| Participant ID | String | Yes | Who "says" this message. Connect a Trigger's Participant ID, a Participant Picker, or any node that outputs a participant ID. |
| Output | Description |
|---|---|
| Message ID | The ID of the newly created message. Useful if you need to reference or modify it later. |
- The node receives text and a participant ID.
- If the participant is "user", the message appears as a user message. Otherwise, it appears as a character message attributed to that participant.
- The message is added to the current chat at the end of the conversation.
- Both inputs are required. The node will fail if either the text or participant ID is missing.
- This is the main way to make your agent visible. Without a Chat Message node, your agent works "behind the scenes" — it runs but doesn't post anything the user can see.
- Good for debugging — connect any node's output to a Chat Message to see what value it's producing directly in the chat.
- Messages created by agents are tagged internally, so other event-based agents won't re-trigger from them (no infinite loops).