Make.com HTTP Module

Make.com Discord AI Memory: Persistent Memory for Discord Scenarios

Make.com runs each scenario in isolation — your Discord automation forgets every user between runs. retainr adds persistent memory via two HTTP modules: search before the AI call, store after. No database required.

Add Discord 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 Discord scenario, add an HTTP GET module: https://api.retainr.dev/v1/memories/search?namespace=discord:{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 (discord:{user_id}), content (user message + AI response). Each Discord user now has a persistent memory record.

Make.com Discord memory — frequently asked questions

How do I trigger a Make.com scenario from Discord messages?
Make.com does not have a native Discord module for watching messages. Use a Discord bot with a webhook trigger: configure your Discord bot to POST message payloads to a Make.com webhook URL. The scenario fires on each incoming message.
How do I scope memory per user vs per server in Make.com?
For per-user memory, use discord:{user.id} as the namespace. For server-wide shared memory, use discord:server:{guild.id}. Both approaches use the same HTTP module setup — only the namespace value changes.
Does retainr work with the Make.com HTTP Request module?
Yes. The Make.com HTTP Request module is the standard way to call external APIs. Set the URL, method, and add the Authorization header. Map your webhook payload fields to the URL parameters (search) or JSON body (store).
Can I use this for a Discord community bot that remembers all members?
Yes. Use the server namespace discord:server:{guild_id} for shared community knowledge, or per-user namespaces discord:{user_id} if you want individual user memory. Both approaches work with the same 2 HTTP module pattern.
How many Discord users can I serve on the free plan?
The free plan includes 1,000 memory operations per month. Each scenario run uses 2 operations (1 search + 1 store), supporting 500 conversations per month across all users. Paid plans start at 20,000 operations per month for higher volumes.

Give your Make.com Discord scenario real memory

1,000 memory operations per month. Free forever. No credit card required.

Start free