kartik-mem0
7495ab67ad
The n8n node was the only integration without a `pnpm.overrides` block, so its tree carried 9 advisories (7 high, 2 moderate) that pi-agent-plugin, openclaw, and vercel-ai-sdk already pin out. Adds the same block, scoped to the packages actually present in this tree (`esbuild` and `undici` are not, so their sibling entries are omitted rather than carried over as dead config). Down to 2 from 9. Both remaining are GHSA-mh99-v99m-4gvg on the 1.x and 2.x brace-expansion lines, whose fix shipped only in 5.0.8 with no backport. Forcing those lines to 5.x does clear the audit but breaks `gulp build`: rimraf -> glob -> minimatch@9 imports brace-expansion as a default export, which the 5.x ESM build does not provide. Replacement ranges are capped per major rather than left open like the siblings'. An unbounded `uuid >=11.1.1` resolves to 14.x, which is pure ESM and cannot be required by n8n-workflow under Jest's CJS runtime. All dev-only: the published package still declares zero runtime dependencies, so none of this reaches an installed node. lint, build, and the 5 tests pass; `pnpm install --frozen-lockfile` is clean.
@mem0/n8n-nodes-mem0
This is an n8n community node that lets you use Mem0 — the memory layer for AI agents — in your n8n workflows.
Mem0 gives your agents long-term memory: add memories from conversations, then search and recall them across sessions.
n8n is a fair-code licensed workflow automation platform.
Installation · Operations · Credentials · Usage · Resources
Installation
Follow the community nodes installation guide and install @mem0/n8n-nodes-mem0.
Operations
The Memory resource supports:
| Operation | Description | Endpoint |
|---|---|---|
| Add | Extract and store memories from messages | POST /v3/memories/add/ |
| Search | Semantic search over stored memories | POST /v3/memories/search/ |
| Get Many | List memories for a user (paginated) | POST /v3/memories/ |
| Get | Retrieve a single memory by ID | GET /v1/memories/{id}/ |
| Update | Update a memory's text or metadata | PUT /v1/memories/{id}/ |
| Delete | Delete a single memory by ID | DELETE /v1/memories/{id}/ |
Add & asynchronous extraction
By default, Add runs LLM-based extraction asynchronously — the API returns an event ID and the node polls until extraction finishes, then returns the resulting memories. Disable Wait for Completion to return immediately with the event ID, or set Infer = false (under Additional Fields) to store messages verbatim and return synchronously.
Credentials
You need a Mem0 API key. Create one at app.mem0.ai → Settings → API Keys. The key is sent as Authorization: Token <key>.
Usage
This node is also usable as a tool by n8n's AI Agent node — attach it so an agent can "remember" and "recall" autonomously.
A typical loop:
- Search memory before answering, filtered by
User ID. - Add durable facts after a meaningful exchange.
Memory writes are asynchronous by default; allow a moment after an Add before searching for the same content.
Telemetry
This node sends no third-party telemetry. Its API requests are tagged with source: "N8N" so Mem0 can see aggregate usage of the integration. No separate analytics service is contacted and nothing else is collected.