Valkey vector datastore node
The idea is:
Add a Valkey Vector Store community node for n8n that works with Amazon ElastiCache for Valkey 8.2 and self‑hosted Valkey. The node should focus on Valkey’s deployed vector search capabilities (KNN/HNSW with COSINE/L2/IP and hybrid tag/numeric filters).
There is a node for Redis Vector Store, and although Valkey is largely protocol‑compatible with Redis, their search/vector modules differ, so the current Redis node’s behavior is incompatible with Valkey. See the existing issue: Redis Vector Store node incompatible with AWS ElastiCache Valkey - TEXT field not supported · Issue #21361 · n8n-io/n8n · GitHub
My use case:
Some community users run vector search on Valkey (not Redis), especially via ElastiCache for Valkey 8.2, to power RAG, semantic caching, and agent memory. When using n8n’s Redis Vector Store node, document inserts fail because the node tries to create a TEXT field in the index—Valkey’s Search/Vector path on these deployments doesn’t support that, so the workflow breaks. (Error example: Unknown argument TEXT.)
I think it would be beneficial to add this because:
- Unblocks Valkey users. Today, inserts fail and RAG workflows can’t proceed; a Valkey‑aware node restores “insert → search → retrieve” without schema conflicts.
- Meets users where they already are. Many teams standardize on Valkey in AWS/GCP; this node lets them add vector search to n8n without introducing a new database.
- Fits n8n’s ecosystem. New integrations belong in community nodes and can be verified for easy, in‑app installation.e solve? →
Any resources to support this?
Valkey - https://valkey.io/
Valkey Search module - Valkey Documentation · Valkey Search
Existing Redis node issue - Redis Vector Store node incompatible with AWS ElastiCache Valkey - TEXT field not supported · Issue #21361 · n8n-io/n8n · GitHub
Are you willing to work on this?
Yes. I’m happy to author and maintain a Valkey Vector Store community node (publish to npm, provide README and examples), submit for n8n verification.