Make.com Slack AI Memory: Persistent Memory for Slack Scenarios
Make.com runs each scenario in isolation — your Slack automation forgets every user between runs. retainr adds persistent memory via two HTTP modules: search before the AI call, store after.
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 Slack scenario, add an HTTP GET module: https://api.retainr.dev/v1/memories/search?namespace=slack:{user_id}&q={message}&limit=5. Header: Authorization: Bearer YOUR_KEY. Inject results into your AI module.
3
Add HTTP module to store memory
After your AI module, add an HTTP POST module to https://api.retainr.dev/v1/memories. Body: namespace (slack:{user_id}), content (user message + AI response). Each Slack user now has a persistent memory record.
How do I trigger a Make.com scenario from Slack messages?
Use the Slack module in Make.com with the Watch Messages trigger. Connect your Slack workspace via OAuth, select the channel to monitor, and the scenario fires on every new message. For DMs, use the Watch Direct Messages trigger.
Should I scope memory per user or per channel in Make.com Slack scenarios?
For AI assistants responding to individual users, scope by user ID: slack:{user.id}. For channel-level bots where shared context matters, scope by channel ID: slack:channel:{channel.id}. Map the ID from the Slack trigger payload.
Can I use this with Slack Connect channels in Make.com?
Yes. Slack Connect channels have the same user ID and channel ID structure. The Make.com Slack module handles Connect channels the same way as regular channels. Namespace memory the same way.
How do I handle user opt-out requests?
Add a Router that checks for a specific keyword or slash command. In the opt-out branch, send an HTTP DELETE request to https://api.retainr.dev/v1/memories?namespace=slack:{user_id} to remove all stored memories for that user.
Can I combine Slack memory with email memory for the same user?
Yes. If you can match users across channels (e.g., by email), use a shared namespace like user:{email} in both your Slack and email scenarios. Both channels contribute to the same memory pool and draw from it on search.
Give your Make.com Slack scenario real memory
1,000 memory operations per month. Free forever. No credit card required.