Overview
This node integrates with the RecallioAI memory API to manage user or project memories. It supports multiple operations including writing new memory entries, recalling memories based on queries or tags, exporting memory data, and deleting memories.
The Delete Memory operation specifically allows users to delete stored memories scoped either to a specific user or an entire project. This is useful for managing data retention, complying with privacy requirements, or clearing outdated information.
Practical example:
A customer support automation workflow might use this node to delete all memory data related to a user when their account is closed, ensuring no residual personal data remains.
Properties
| Name | Meaning |
|---|---|
| User ID | The identifier of the user whose memory data will be deleted. |
| Delete Scope | The scope of deletion: either "User" to delete memories related to the specified user, or "Project" to delete all memories within the project. |
Output
The output JSON contains a success confirmation and a message indicating which scope's memories were deleted. Example:
{
"success": true,
"message": "Deleted memories for scope: user"
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the RecallioAI memory API.
- The node uses an internal Recallio client library to communicate with the external Recallio service.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an invalid user ID or scope may result in no data being deleted or errors from the API.
- Error messages:
"Unknown operation: <operation>"indicates that the operation parameter was set incorrectly.- API errors returned from Recallio (e.g., network issues, permission denied) will be surfaced as error messages.
- Resolution tips:
- Ensure the API key credential is correctly configured and valid.
- Verify that the user ID exists and the delete scope is correctly chosen.
- Use the "Continue On Fail" option in n8n to handle errors gracefully if needed.
Links and References
- RecallioAI official documentation (hypothetical link)
- n8n documentation on creating custom nodes