Make.com WhatsApp AI Memory: Persistent Memory for WhatsApp Scenarios
Make.com runs each scenario in isolation — your WhatsApp automation has no memory of the same customer from previous runs. retainr adds persistent memory via two HTTP modules: search before the AI call, store after. No database. No code. No extra infrastructure.
Every Make.com scenario execution is independent. Context from one run is not available in the next — even for the same phone number. Make.com Data Stores require manual schema design and have no semantic search. retainr is purpose-built for this: two HTTP modules add permanent per-user memory to any WhatsApp scenario.
Add WhatsApp memory to Make.com in 3 steps
1
Get your retainr API key
Create a free retainr account at retainr.dev/dashboard. Copy your API key. Takes 30 seconds.
2
Add HTTP module to search memory
At the start of your Make.com scenario, add an HTTP module: GET https://api.retainr.dev/v1/memories/search?namespace=wa:{phone}&q={message}&limit=5. Header: Authorization: Bearer YOUR_KEY. Inject the results into your AI module prompt.
3
Add HTTP module to store memory
After your AI module, add another HTTP module: POST https://api.retainr.dev/v1/memories. Body: namespace (the phone number), content (user message + AI response). The scenario now builds memory for every WhatsApp user.
360dialog, WATI, Twilio, and MessageBird all have native Make.com modules or can be connected via HTTP Request module. The retainr memory modules are provider-agnostic — they slot into any Make.com WhatsApp scenario regardless of which WhatsApp provider you use.
How do I scope memory per user in a multi-user WhatsApp scenario?
Use the sender phone number as the namespace: wa:+14155238886. Map this from the WhatsApp trigger payload. Each phone number gets completely isolated memory — one user never sees another user context in search results.
Does retainr work with the Make.com HTTP module without extra setup?
Yes. Add an HTTP module, set the method and URL, add the Authorization header with your API key, and map your scenario variables to the body fields. No custom app installation, no OAuth flow — just two HTTP module configurations.
Can I use this with Make.com WhatsApp Business Cloud?
Yes. Make.com has a native WhatsApp Business Cloud module. Use it as your trigger to receive messages and as the final action to send replies. The retainr HTTP modules sit in between, handling the memory search and store steps.
How do I handle opt-out requests for GDPR compliance?
When a user sends a stop or delete request, call DELETE https://api.retainr.dev/v1/memories?namespace=wa:{phone} via HTTP module. This permanently deletes all stored memories for that phone number. Log the deletion event in your CRM for GDPR records.
Give your Make.com WhatsApp scenario real memory
1,000 memory operations per month. Free forever. No credit card required.