Skip to main content
Zaps fire and forget. The Mem0 app gives them memory: store durable facts from a form submission, a support ticket, or a chat message, then recall them later from any of Zapier’s thousands of apps. No code, no server.

​
Overview

  1. Connect your Mem0 API key once as a Zapier connection.
  2. Use Add Memory to store what a Zap learns.
  3. Use Search Memories or Get Memories to pull that context back into a later step.
  4. Use Delete Memory to remove one by ID.

​
Prerequisites

  1. A Mem0 API key from the API Keys dashboard (sign up at app.mem0.ai if you do not have an account).
  2. A Zapier account on any plan.
The Mem0 app is not yet listed in Zapier’s public App Directory, so you need an invite link to add it to a Zap. Email [email protected] to request one.

​
Setup

1

Add a Mem0 step

In the Zap editor, search for Mem0 and pick an action such as Add Memory.
2

Connect your account

Select Sign in, paste your Mem0 API Key (it starts with m0-), and leave Base URL at https://api.mem0.ai unless you run Mem0 somewhere else.
3

Confirm the connection

Zapier validates the key against Mem0 the moment you save it. A connection labelled Mem0 means the key works.
The key is a password field, so Zapier masks it in the editor. It is sent to Mem0 as Authorization: Token <key>.

​
Quickstart

Remember what a user tells you:
Set Content to the message text and User ID to a stable identifier for that person, such as their email. Then recall it in a later Zap:
Set Query to the incoming message and User ID to the same value. The matched memories become available to every step after it.
Extraction is asynchronous. Add Memory returns immediately with an event ID by default, so a Search fired a second later may not see the new memory yet. See Waiting for extraction.

​
Actions

​
Add Memory

Includes and Excludes narrow what extraction keeps. Sending “I am vegetarian and I never eat mushrooms. I drive a blue Toyota Corolla and my parking spot is B12” stores three memories by default; with Includes: "only record food and diet preferences" it stores just the dietary one.

​
Waiting for extraction

Extraction runs asynchronously, so Add Memory returns an event ID and moves on unless you turn on Wait for Completion. When you do, the step polls for up to 60 seconds and returns the extracted memories instead.
Extraction can take longer than Zapier allows a single step to run, which is why waiting is opt-in. If the step times out, the add was still accepted and typically completes on Mem0’s side, so do not retry it blindly.

​
Search Memories

​
Get Memories

Returns one page per run. Raise Page to walk through larger result sets.

​
Delete Memory

Takes a Memory ID and deletes that memory. Pair it with Search Memories or Get Memories to get the ID first.

​
Choosing a User ID

The User ID is a stable string you pick to identify whose memories these are. It is not looked up in the dashboard, so any consistent value works: your app’s internal user ID, an email, or a UUID. Use the same value on Add, Search, and Get Memories or recall returns nothing.

​
Troubleshooting

  • Mem0 does not appear in the Zap editor: the app is not yet in the public App Directory. Email [email protected] for an invite link.
  • The connection fails when you paste the key: check that it starts with m0- and has not been revoked in the API Keys dashboard.
  • Search returns nothing right after an Add: extraction is asynchronous. Turn on Wait for Completion, or put a Zapier Delay step before the Search.
  • “Metadata must be valid JSON” or “Custom Categories must be valid JSON”: those fields take raw JSON. Check for smart quotes and trailing commas.
  • The Add step times out: the memory was still accepted and is likely finishing server-side. Confirm with Get Memories before re-running.

n8n Integration

Build workflows with the Mem0 n8n community node

Flowise Integration

Add memory to Flowise chatflows
Using Mem0? Star us on GitHub to help more developers discover memory for AI apps.