Overview
This node integrates with the RecallioAI memory API to manage user-specific memory data. The "Write Memory" operation allows users to store contextual information (memory) associated with a specific user ID, optionally tagged and with a configurable expiration time (TTL). This is useful for applications that require persistent, user-related context storage such as chatbots, personal assistants, or any system needing to remember user interactions over time.
Practical examples:
- A chatbot storing conversation context or user preferences to personalize future interactions.
- An application saving notes or tags related to a user session for later retrieval.
- Systems that need to maintain short-term memory of user actions with automatic expiry.
Properties
| Name | Meaning |
|---|---|
| Context | The textual content or memory to be stored for the user. |
| User ID | Identifier of the user for whom the memory is being written. |
| Tags | Comma-separated list of tags to categorize or label the memory (e.g., "tag1,tag2"). |
| TTL Days | Number of days before the stored memory expires and is automatically deleted (default 30). |
Output
The output JSON for the "Write Memory" operation contains a simple success confirmation:
{
"success": true
}
This indicates that the memory was successfully written to the RecallioAI service.
Dependencies
- Requires an API key credential for the RecallioAI service to authenticate requests.
- Uses the RecallioAI client library internally to communicate with the Recallio memory API.
- The node expects network connectivity to the RecallioAI API endpoint.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect or empty User ID will prevent memory from being associated correctly.
- Improperly formatted tags (e.g., extra commas or spaces) might lead to unexpected tag parsing results.
- Setting TTL Days to zero or negative values may cause immediate expiration or errors.
Error messages:
"Unknown operation: writeMemory"— This would indicate a misconfiguration in the operation parameter; ensure it is set exactly to "writeMemory".- API errors returned by RecallioAI (e.g., authentication errors, rate limits) will be propagated; check your API key validity and usage limits.
Resolution tips:
- Verify that the API key credential is correctly configured and active.
- Ensure the User ID is provided and valid.
- Use proper comma-separated format for tags without trailing commas.
- Set TTL Days to a positive integer to define a valid expiration period.
Links and References
- RecallioAI Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General info on Managing API Credentials in n8n