Himanshu-Sangshetti
6c224425d3
The Mem0 API rejects an add with no entity ID ("At least one entity ID is
required: user_id, agent_id, app_id, or run_id"), but Add Memory marked
user_id optional, so Zapier let users submit an empty step and hit a confusing
HTTP 400 at run time. Search Memories and Get Memories already require user_id;
this makes Add Memory consistent and surfaces the requirement in the editor
before the Zap runs.
Zapier integration for Mem0
A Zapier integration for Mem0 — the memory layer for AI agents. Add, search, list, and delete long-term memories from any Zap.
Built with the Zapier Platform CLI.
Actions
| Type | Name | Endpoint |
|---|---|---|
| Create | Add Memory | POST /v3/memories/add/ |
| Create | Delete Memory | DELETE /v1/memories/{id}/ |
| Search | Search Memories | POST /v3/memories/search/ |
| Search | Get Memories | POST /v3/memories/ |
Add Memory runs LLM extraction asynchronously and returns immediately with an event ID by default. Turn on Wait for Completion to have the action poll until extraction finishes and return the resulting memories — note that extraction can take longer than Zapier allows a single step to run, and a timeout there does not mean the add failed (it typically still completes server-side). Set Infer = false to store the message verbatim instead of extracting.
Get Memories returns one page at a time; use the Page and Limit fields to page through larger result sets.
Authentication
Custom (API key) auth. Provide a Mem0 API key from app.mem0.ai → Settings → API Keys. It is sent as Authorization: Token <key>.
Development
Written in TypeScript; the app compiles to dist/ (Zapier runs the compiled JS).
pnpm install
pnpm build # compile src/ → dist/
pnpm test:unit # offline unit tests (mocked, no network)
MEM0_API_KEY=m0-... pnpm test # unit + live E2E against api.mem0.ai
Anonymous usage telemetry is sent to Mem0; opt out with MEM0_TELEMETRY=false.
To deploy (maintainers): pnpm build && zapier push.
License
MIT