Himanshu-Sangshetti
98ae733f07
Match the repo's per-integration CI/CD convention (vercel-ai / pi-agent pattern): - n8n-nodes-mem0-checks.yml (lint + build + dist verify) and n8n-nodes-mem0-cd.yml (npm publish --provenance via OIDC, dispatched by the release router on tag n8n-nodes-mem0-v*). - zapier-mem0-checks.yml (zapier validate) and zapier-mem0-cd.yml (manual zapier push; requires ZAPIER_DEPLOY_KEY). Zapier deploys to Zapier's platform, not npm, so it is not in the release router. - Wire both packages into ci-gate.yml (path filters + call jobs + gate). - Register the n8n tag prefix in release.yml and document it + the Zapier manual-deploy in AGENTS.md. - Skip the Zapier E2E suite when MEM0_API_KEY is absent so CI is green offline (it still runs locally with a key).
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 by default; the action polls the event until it completes and returns the resulting memories. Turn off Wait for Completion to return immediately, or set Infer = false to store verbatim (synchronous).
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