Skip to content
Nappai Documentation

Store Message

The Store Message component lets you keep a chat message in the system’s memory so you can use it later in your workflow. It simply takes the message you give it, saves it, and then passes the same message on to the next component.

How it Works

When you drop this component into your dashboard, it receives a Message object (the text, sender, timestamp, etc.). Inside the component, the message is handed to a small internal function that writes it to Nappai’s local storage. After storing, the component updates its status with the current list of stored messages and then returns the original message unchanged. No external services are called, so the operation is fast and keeps all data on your own system.

Inputs

Input Fields

  • Message: The chat message you want to store.
    • Visible in: All

Outputs

The component outputs the same Message it received. You can connect this output to other components that need the message later, such as a “Retrieve Message” component or a logging component.

Usage Example

  1. Generate a message – Use a “Generate Text” component to create a response to a user query.
  2. Store the message – Connect the output of the text generator to the Store Message component.
  3. Continue the workflow – The output of Store Message can feed into a “Send Message” component to deliver the response, or into a “Log” component to keep a record.

This simple chain ensures every message you send or receive is saved for future reference or analysis.

  • Retrieve Message – Pulls a stored message back into the workflow.
  • Delete Message – Removes a message from storage.
  • Log Message – Writes a message to a log file or database.

Tips and Best Practices

  • Store after creation – Save a message immediately after it’s generated to avoid losing data if the workflow stops.
  • Check message format – Ensure the message object contains all required fields (text, sender, timestamp) before storing.
  • Use in loops carefully – If you’re storing many messages in a loop, consider batching to improve performance.

Security Considerations

  • All messages are stored locally on the Nappai server; no external API calls are made.
  • Make sure your server’s storage is secured and backed up if the messages contain sensitive information.
  • If you need to share stored messages with other users, use Nappai’s built‑in access controls rather than exposing raw data.