Skip to content
Nappai Documentation

Cassandra Chat Memory

This component acts like a secure storage box for your chat messages within Nappai’s automation system. It uses a database called Cassandra (or AstraDB, a cloud version of Cassandra) to keep your chat history safe and readily available. This ensures that your chat logs are persistent and easily retrievable.

Relationship with Cassandra/AstraDB

This component uses Cassandra or AstraDB, powerful databases that store and manage large amounts of data reliably. It handles the technical details of connecting to and interacting with these databases so you don’t have to.

Inputs

  • Contact Points / Astra Database ID: This is the address of your Cassandra database or the ID of your AstraDB database. Think of it as the location of your chat message storage. This is required.

  • Username: Your username for your Cassandra database. Leave this blank if you’re using AstraDB. This is not required.

  • Password / AstraDB Token: Your password for your Cassandra database or your AstraDB token. This is crucial for security and is required.

  • Keyspace: This specifies the section of your database where your chat messages are stored. Think of it as a folder within your storage box. This is required.

  • Table Name: The name of the specific table within your database where the chat messages are kept. This is like a specific file within the folder. This is required.

  • Session ID (Advanced): A unique identifier for a specific chat session. This is optional and for more advanced users.

  • Cluster arguments (Advanced): Additional settings for connecting to the database. This is optional and for advanced users.

Outputs

This component doesn’t directly produce outputs you’ll see in the dashboard. Instead, it quietly stores and retrieves chat messages from your Cassandra or AstraDB database, making them available for other Nappai components to use.

Usage Example

Imagine you want to save all the messages from a customer service chat. You would configure this component with your database details (Contact Points/Astra Database ID, Password/AstraDB Token, Keyspace, and Table Name). Other Nappai components can then access this stored chat history to analyze the conversation, provide insights, or automate responses.

Templates

[List of templates where the component can be seen and its configuration. This section will be populated based on where this component is used in Nappai’s flow templates.]

  • Chat Memory: This component retrieves chat messages, potentially from different sources, including this Cassandra Chat Memory component.
  • Store Message: This component saves chat messages, and can save them to this Cassandra Chat Memory component.
  • Retrieval QA History: This uses stored chat history (like the one stored here) for question-answering.
  • Runnable With Message History: This component executes actions using the chat history stored here.
  • Tool Calling Agent: This agent can use the chat history stored here to inform its actions.

Tips and Best Practices

  • Ensure you have the correct database credentials before configuring this component.
  • For security, store your database password/token securely and avoid hardcoding it directly into your Nappai configuration.
  • If you’re unsure about the Keyspace and Table Name, consult your database administrator.

Security Considerations

  • Never share your database password/token with anyone.
  • Use strong passwords and regularly update them.
  • Consider using environment variables to store sensitive information instead of hardcoding them directly into the component configuration. This helps prevent accidental exposure.