Skip to content
Nappai Documentation

Chat Input

Chat Input is a simple tool that lets you send a text message (or attach files) to Nappai’s chat system.
You can choose who is sending the message, give it a name, and decide whether the message should be kept in the chat history for later reference.

How it Works

When you type a message into the Text field, the component creates a Message object that contains all the information you entered: the text, the sender type (AI or User), the sender’s name, session and conversation IDs, and any attached files.
If you tick Store Messages, the component saves that Message in the system’s history so you can retrieve it later.
The component does all of this locally inside Nappai; it does not call any external APIs.

Inputs

  • Files: Attach one or more files (text, images, audio, or video) to go along with your message.
  • Conversation ID: A unique identifier that groups messages together in the same conversation thread.
  • Text: The main content of your message.
  • Sender Type: Choose whether the message is coming from the AI or from a user.
  • Sender Name: The name that will appear next to the message.
  • Session ID: A unique identifier for the current chat session.
  • Store Messages: Check this box if you want the message to be saved in the chat history.

Outputs

  • Message: The component returns a Message object that contains everything you entered.
    This output can be used by other components to display the message, trigger actions, or store it in a database.

Usage Example

  1. Drag the Chat Input component onto your workflow.
  2. In the Text field, type: “Hello, Nappai! Can you summarize the last report?”
  3. Leave Sender Type as User and Sender Name as John.
  4. Check Store Messages so the conversation is saved.
  5. Connect the Message output to a Display Message component to show the text on the dashboard, or to a Process Message component that will send the text to an AI model for a response.

The message you just created will appear in the chat history, and you can refer back to it later or use it as input for other automation steps.

  • Chat Component – Handles receiving and displaying chat messages in the dashboard.
  • MessageTextInput – A simple text field that can be reused in other components.
  • FileInput – Lets you attach files to messages or other data objects.

Tips and Best Practices

  • Keep the Text field concise; long messages can slow down processing.
  • Use a consistent Session ID for all messages in a single user session to make it easier to track the conversation.
  • If you’re sending sensitive information, double‑check that Store Messages is unchecked or that the data is encrypted before saving.
  • Attach files only when necessary; large files can increase load times.

Security Considerations

  • Avoid uploading confidential documents unless you’re sure the system’s storage is secure.
  • If you enable Store Messages, remember that the message will be saved in the system’s history and could be accessed by anyone with permission to view that history.
  • Use the Sender Name and Sender Type fields to clearly label who sent each message, which helps prevent confusion in shared workspaces.