Chat Input
On this page
Purpose
Chat Input accepts a chat turn and creates a Message with text, sender fields, a session ID, timestamp, and optional file references.
When to use it
- Start an Agent Core or Language Model chat flow.
- Store user messages in a session.
- Pass supported text or image file references to a downstream component.
How to use it
- Add Chat Input and leave Input Text blank for normal Playground use.
- Connect Chat Message to Agent Core or another Message-compatible input.
- Connect the final response to Chat Output.
- Test the flow in the Playground.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Input Text | Text placed in the output Message. It has no upstream connection handle. | Leave blank for runtime chat input. |
| Initiate Conversation | Lets a Platform client request an opening turn for a fresh session. | Leave on only when the downstream instructions define a suitable greeting. |
| Store Messages | Stores the input when a session ID exists. | Leave on for multi-turn chat. |
| Sender Type | Sets the sender role. | Keep User. |
| Sender Name | Sets the display name. | Keep User. |
| Session ID | Groups stored messages. | Leave blank to use the current session. |
| Files | Adds temporary file references to the Message. | Use only when downstream components handle the files. |
Expected result
Chat Input returns one Message. It stores the message only when Store Messages is on and a session ID resolves. It does not retrieve history, answer the user, or parse attached files. Agent Core separately reads session history.
Reference details
Initiate Conversation is available for Platform build, share, and Playground flows. Current Flow Runtime message requests do not use that kickoff path. The visible greeting comes from downstream agent instructions, not Chat Input.
Related components
- Agent Core receives the chat Message.
- Language Model receives a direct chat prompt.
- Chat Output displays the final response.