Himanshu-Sangshetti
cf861ebf5a
Zapier: - Bound the poll budget under Zapier's step timeout and default Wait for Completion off; timeout message notes the add likely still succeeded - Add offline unit tests (mocked z.request) and run them in CI - Expose a Page input on Get Memories - Encode memory_id in the delete path - Update E2E to test the default no-wait path (add then search-retry) n8n: - Clarify the Infer description (controls extraction, not waiting) - Add an App ID field and require at least one entity id before add - Pass itemIndex into pollEvent errors - Unwrap event results so wait-path output matches search and get many
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
npm install
MEM0_API_KEY=m0-... npm test # runs the E2E suite against api.mem0.ai
To deploy (maintainers): zapier login && zapier push.
License
MIT