Memory Box icon

Memory Box

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

Actions3

Overview

The "Memory Box" node interacts with a Memory Box API to store and retrieve memories or memory buckets. It supports operations on two main resources: individual memories and buckets of memories.

Specifically, the Get From Bucket operation under the Memory resource retrieves all memories stored within a specified bucket. This is useful when you want to fetch grouped or categorized memories for further processing or analysis in your workflow.

Practical examples:

  • Retrieving all notes or data entries saved under a particular project bucket.
  • Fetching user session memories grouped by a bucket ID for personalized automation.
  • Collecting related memories for summarization or reporting.

Properties

Name Meaning
Bucket ID The identifier of the bucket from which to retrieve memories. If not provided, defaults to retrieving from no specific bucket.

Output

The output is an array of JSON objects, each representing a memory retrieved from the specified bucket. Each item contains the memory data as returned by the Memory Box API.

  • The json field holds the memory details.
  • No binary data output is indicated for this operation.

Example output structure (simplified):

[
  {
    "json": {
      "id": "memory1",
      "text": "Sample memory text",
      "bucketId": "bucket123",
      ...
    }
  },
  {
    "json": {
      "id": "memory2",
      "text": "Another memory",
      "bucketId": "bucket123",
      ...
    }
  }
]

Dependencies

  • Requires connection to the Memory Box API via an API key credential configured in n8n.
  • The node uses internal helper functions to make authenticated HTTP requests to the API.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Missing or invalid Bucket ID: If the bucket ID is incorrect or does not exist, the API may return an empty list or an error. Verify the bucket ID is correct.
  • API authentication errors: Ensure the API key credential is properly set up and has permissions to access the requested bucket.
  • Network issues: Connectivity problems can cause request failures; check network settings and API availability.
  • Empty results: If no memories are returned, confirm that the bucket contains stored memories.

Common error messages might include:

  • Unauthorized or authentication failed — check API credentials.
  • Bucket not found — verify the bucket ID.
  • Request timeout or network error — retry or check connectivity.

Links and References

Discussion