kartik-mem0
2a61fe1a32
The Add operation exposed app_id, includes, and excludes in Additional Fields and forwarded them to POST /v3/memories/add/. None of the three are declared on that endpoint's schema (they belong to MemoryInput, used by POST /v1/memories/), so they were silently dropped by the server. app_id was worse than a no-op: the entity-id guard accepted it as satisfying "at least one entity id", so filling only App ID passed local validation and then sent a v3 request carrying no scope v3 recognises. The guard now requires User ID, Agent ID, or Run ID. Docs corrections alongside it: - Add: document Custom Instructions and Custom Categories, which the node has always supported but the docs never mentioned - Get Many: document Return All, which the docs omitted entirely - README: Infer and Wait for Completion are independent controls; the README claimed infer=false returns synchronously, contradicting the node's own field description and its actual behaviour
82 lines
3.4 KiB
Plaintext
82 lines
3.4 KiB
Plaintext
---
|
|
title: n8n
|
|
description: "Add long-term memory to n8n workflows and AI Agents with the Mem0 community node, no code required."
|
|
---
|
|
|
|
The [`@mem0/n8n-nodes-mem0`](https://www.npmjs.com/package/@mem0/n8n-nodes-mem0) community node brings [Mem0](https://mem0.ai) memory to [n8n](https://n8n.io). Add, search, and manage long-term memories inside any workflow, and use it as a tool for the n8n AI Agent.
|
|
|
|
## Overview
|
|
|
|
The node wraps the hosted Mem0 REST API and supports six operations on the **Memory** resource:
|
|
|
|
| Operation | Endpoint |
|
|
| --- | --- |
|
|
| **Add** | `POST /v3/memories/add/` |
|
|
| **Search** | `POST /v3/memories/search/` |
|
|
| **Get** | `GET /v1/memories/{id}/` |
|
|
| **Get Many** | `POST /v3/memories/` |
|
|
| **Update** | `PUT /v1/memories/{id}/` |
|
|
| **Delete** | `DELETE /v1/memories/{id}/` |
|
|
|
|
It is marked `usableAsTool`, so the n8n AI Agent (Tools Agent) can call it directly to remember and recall information.
|
|
|
|
## Installation
|
|
|
|
Install it like any n8n community node:
|
|
|
|
1. In n8n, go to **Settings → Community Nodes → Install**.
|
|
2. Enter `@mem0/n8n-nodes-mem0` and confirm.
|
|
|
|
The node then appears in the nodes panel under the AI category.
|
|
|
|
## Authentication
|
|
|
|
Create a **Mem0 API** credential in n8n:
|
|
|
|
- **API Key**: from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-n8n" rel="nofollow">Mem0 API Key dashboard</a>. Sent as `Authorization: Token <key>`.
|
|
- **Base URL**: defaults to `https://api.mem0.ai`.
|
|
|
|
## Operations
|
|
|
|
### Add
|
|
|
|
Extracts and stores memories from one or more messages. Provide at least one entity id (**User ID**, or **Agent ID** / **Run ID** in Additional Fields); the node validates this before calling the API.
|
|
|
|
Additional Fields also expose:
|
|
|
|
| Field | Purpose |
|
|
| --- | --- |
|
|
| **Metadata (JSON)** | Arbitrary JSON attached to each extracted memory |
|
|
| **Infer** | On by default. Turn off to store messages verbatim instead of running LLM extraction |
|
|
| **Custom Instructions** | Free-text guidance steering what the extractor keeps or ignores, for this call |
|
|
| **Custom Categories** | JSON array of `{category: description}` objects, replacing the project-level catalog for this call |
|
|
|
|
Extraction is asynchronous. **Wait for Completion** (on by default) polls the event until it finishes and returns the resulting memories; turn it off to return immediately with the event ID.
|
|
|
|
### Search
|
|
|
|
Semantic search over stored memories. Provide a **Query**, a **User ID** (required, the API needs an entity filter), and an optional **Limit**.
|
|
|
|
### Get Many
|
|
|
|
Lists memories for a **User ID**. Turn on **Return All** to page through every memory automatically; leave it off to fetch a single **Page**. **Page Size** applies either way.
|
|
|
|
### Get / Update / Delete
|
|
|
|
Operate on a single memory by **Memory ID**. Update accepts new **Text** and/or **Metadata (JSON)**.
|
|
|
|
## Choosing a `userId`
|
|
|
|
The `userId` is a stable string you choose to identify whose memories these are. It is not looked up in the dashboard. Common choices are your app's internal user ID, an email, or a UUID. Use the same value across Add, Search, and Get Many so recall works.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Zapier Integration" icon="bolt" href="/integrations/zapier">
|
|
Add memory to Zaps across thousands of apps
|
|
</Card>
|
|
<Card title="Flowise Integration" icon="blocks" href="/integrations/flowise">
|
|
Add memory to Flowise chatflows
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
<Snippet file="star-on-github.mdx" />
|