Files
mem0/integrations/n8n-nodes-mem0
Himanshu-Sangshetti 7417f87252 fix(n8n): address review feedback and pass the verification scanner
- Telemetry: replace client-side PostHog (which read process.env, banned in
  verified nodes) with first-party `source: "N8N"` attribution on API requests,
  mirroring OpenClaw. Removes the undisclosed-collection concern entirely.
- Verification-scanner fixes: add credential icon, use NodeConnectionTypes.Main
  instead of the 'main' literal, wrap error paths in NodeApiError, stop shipping
  .d.ts / tsbuildinfo, and align the local eslint config with the scanner.
- Add offline unit tests (jest): entity-id guard, JSON-parse errors, poll-timeout
  loop, source attribution, and Return All pagination.
- Get Many: add a Return All option that pages through all memories.
- Docs: README telemetry note and an AGENTS.md Key Directories row.

Verified: build + tsc + eslint + 5 unit tests + live E2E against api.mem0.ai, and
the packed tarball passes @n8n/scan-community-package with zero violations.
2026-07-23 19:34:00 +05:30
..

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 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:

  1. Search memory before answering, filtered by User ID.
  2. 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.

Resources

License

MIT