RoundRobin: Memory Recall icon

RoundRobin: Memory Recall

Recall and inspect conversation memory from RoundRobin nodes
Join our community

Overview

The RoundRobin: Memory Recall node is designed to retrieve and inspect the raw memory state of a conversation previously stored by other RoundRobin nodes in n8n. It allows users to recall conversation data—including messages, roles, and metadata—for debugging, auditing, or further processing within workflows. This node is particularly useful for scenarios where you need to review the history or context of automated conversations, such as chatbots, meeting notes, support chats, or any collaborative workflow that leverages conversational memory.

Practical examples:

  • Debugging chatbot flows by inspecting the full message history and role assignments.
  • Auditing customer service interactions by recalling stored conversation logs.
  • Extracting meeting notes or strategy discussions for reporting or analysis.

Properties

Display Name Type Description
Recall Options notice Informs the user about the purpose of the node (for inspection/debugging of conversation memory).
Binary Output Property string Name of the binary property from which to read the memory data (default: data).
Storage ID string Optional custom ID for conversation storage; used if "Use Custom Storage ID" is enabled.
Use Custom Storage ID boolean Whether to use a custom storage ID instead of the default workflow ID.
Include Messages boolean Whether to include message history in the output.
Include Roles boolean Whether to include role definitions in the output.
Include Metadata boolean Whether to include conversation metadata in the output.
Memory Selection notice Informs the user to select which conversation memory to retrieve.
Conversation Memory options Selects which predefined or custom conversation memory to recall.
Custom Memory ID string If "Custom ID" is selected above, enter the specific memory ID to recall.

Output

The node outputs an array with a single item containing:

JSON Output Structure

{
  "status": "success" | "warning" | "error",
  "operation": "recall", // Only present on success
  "timestamp": "<ISO timestamp>",
  "memoryId": "<ID used for recall>",
  "conversation_id": "<conversationId or memoryId>",
  "memory": {
    "messages": [ /* Array of message objects, if included */ ],
    "roles": [ /* Array of role definitions, if included */ ],
    "spotCount": <number>,      // Only if metadata included
    "roundCount": <number>,     // Only if metadata included
    "maxRounds": <number>,      // Only if metadata included
    "lastUpdated": "<ISO date>",// Only if metadata included
    "title": "<string>",        // Only if metadata included
    "context": "<string>",      // Only if metadata included
    "talkingPoints": [ /* Array, only if metadata included */ ],
    "isNewConversation": <boolean> // Only if metadata included
  }
}
  • On success, all requested fields are populated.
  • On warning (e.g., no binary data found), the output includes a message and minimal info.
  • On error (e.g., invalid binary data), the output includes an error message and available binary properties.

Binary Output

  • The node passes through the original binary data unchanged. No new binary data is generated.

Dependencies

  • External Storage Manager: The node relies on an external storage manager module (createStorageManager) to load memory data from binary input.
  • Input Requirements: The node expects binary data to be present in the specified property (default: data). This binary data should originate from a compatible RoundRobin node.
  • No API keys or environment variables are required for this node itself.

Troubleshooting

Common Issues:

  • No binary data found:
    • Message: "No memory data found. Nothing to recall."
      • Cause: The previous node did not provide binary data, or the wrong property was specified.
      • Solution: Ensure the node is connected after a compatible RoundRobin node and the correct binary property is set.
  • Invalid binary data:
    • Message: "No valid binary data found. Please connect this node to a previous RoundRobin node."
      • Cause: The binary data structure is missing or corrupted.
      • Solution: Check that the upstream node outputs valid memory data and that the binary property name matches.
  • Workflow ID undefined:
    • Warning in logs: Falls back to node name if workflow ID is missing.
      • Solution: Normally not critical, but ensure your workflow is properly saved and named.

Error Handling:

  • Any unexpected errors are wrapped and reported as n8n NodeOperationError with a descriptive message.

Links and References

Discussion