Graphiti Memory

Lê e grava memória em uma instância Graphiti self-host
Join our community

Actions2

Overview

The "Graphiti Memory" node interacts with a self-hosted Graphiti instance to read and write memory data organized by groups. It supports two main operations:

  • Get Memory: Queries the Graphiti memory store for relevant messages based on a user-provided query string.
  • Add Messages: Adds new conversation messages (user and assistant) to a specified memory group.

This node is useful in scenarios where you want to maintain contextual memory for chatbots or AI assistants, enabling them to recall past interactions or relevant information dynamically. For example, it can be used to fetch related past conversations when a user asks a question or to save new dialogue exchanges to improve future responses.

Properties

Name Meaning
Operation The action to perform: either "Get Memory" to retrieve relevant messages or "Add Messages" to save new messages.
Group ID Identifier for the memory group to organize stored memories.
Query (For "Get Memory" operation) The search query string used to find relevant memories.

Output

The node outputs JSON data containing the response from the Graphiti API:

  • For Get Memory, the output JSON contains the retrieved relevant messages matching the query within the specified group.
  • For Add Messages, the output JSON contains the result of adding the user and assistant messages to the memory group.

The output is paired with the input item index for traceability. This node does not output binary data.

Dependencies

  • Requires an API key credential to authenticate requests to the Graphiti self-hosted instance.
  • Needs the base URL of the Graphiti API endpoint configured in the credentials.
  • Uses HTTP POST requests to interact with /get-memory and /messages endpoints of the Graphiti API.

Troubleshooting

  • No credentials found: The node will throw an error if the required API authentication credentials are missing. Ensure that the API key and base URL are correctly set up.
  • HTTP request failures: Network issues or incorrect API URLs may cause request errors. Verify connectivity and correct API endpoint configuration.
  • Empty or invalid query: For the "Get Memory" operation, providing an empty or malformed query string may return no results or errors.
  • If continueOnFail is enabled, errors per item will be returned as JSON with an error field instead of stopping execution.

Links and References

Discussion