I want to use Redis for session management in a custom node, and I am trying to connect the custom node with a Redis Chat Memory node as session storage like the AI Agent node. More specifically, I am using the NodeConnectionTypes.AiMemory as input of the custom node to attach a Redis Chat Memory.
I would like to know if such usage is allowed for a verified custom node or not, as per my understanding a verified custom node is subject to a set of rules to ensure the robustness, security and performance.
Based on the [verification guidelines]( Verification guidelines | n8n Docs ), using `NodeConnectionTypes.AiMemory` in your custom node should be allowed for verification since it’s part of n8n’s core functionality rather than an external dependency. The key requirement is that verified nodes must have **no external dependencies** - but connecting to n8n’s built-in AI memory system (like Redis Chat Memory nodes) uses n8n’s internal APIs, not external packages.
However, make sure your custom node doesn’t directly import Redis libraries or other external dependencies in its `package.json`. Instead, rely on n8n’s memory connection system to handle the Redis integration. I’d recommend testing your node with the [n8n-node CLI tool]( Building community nodes | n8n Docs ) and running the linter to ensure it meets all verification requirements before submitting.
I ended up using Redis nodes for session management, as the AiMemory itself is not a general purpose tool node but more for chat memory which stores the chat input and output with fixed schema. While it is technically possible to store session info in AiMemory, semantically I don’t think that such usage will be encouraged.