Memory Box icon

Memory Box

Interact with Memory Box API to store and retrieve memories
Join our community

Actions3

Overview

The node interacts with the Memory Box API to store and retrieve "memories," which are pieces of text data that can be semantically searched or organized into buckets. Specifically, the Search Memories operation allows users to perform a semantic search query against stored memories to find those most relevant to the input query text. This is useful in scenarios where you want to quickly retrieve related information from a large collection of textual memories, such as knowledge bases, chat histories, or document snippets.

Practical examples include:

  • Searching customer support logs to find similar past issues.
  • Retrieving relevant notes or documents based on a query phrase.
  • Finding contextually related memories in AI assistant workflows.

Properties

Name Meaning
Query The search query string used to find semantically similar memories in the storage.
Debug Mode Boolean flag to indicate whether to return additional debug information with the results.

Output

The output is an array of JSON objects representing the memories found by the semantic search. Each item corresponds to a memory entry matching the query. If "Debug Mode" is enabled, the output may include extra debug details alongside the search results.

The json field contains the memory data returned by the Memory Box API, typically including text content and metadata about each memory.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Memory Box API via an API key credential configured in n8n.
  • The node depends on internal helper functions to make authenticated HTTP requests to the Memory Box API endpoints.
  • No other external services or environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an empty or malformed query string may result in no matches or errors.
    • Network connectivity problems can prevent successful API calls.

  • Error Messages:

    • Errors from the API (e.g., rate limits, invalid parameters) will be surfaced as error messages in the node output.
    • If "Continue On Fail" is enabled, errors for individual items will be included in the output JSON under an error property.

  • Resolutions:

    • Ensure the API key credential is correctly set up and has necessary permissions.
    • Validate the query string before execution.
    • Check network access and retry if transient errors occur.

Links and References

Discussion