Make.com Telegram AI Memory: Persistent Memory for Telegram Scenarios
Make.com runs each scenario in isolation — your Telegram automation has no memory of previous runs. retainr adds persistent memory via two HTTP modules. No database. No code.
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 Telegram scenario, add an HTTP GET module: https://api.retainr.dev/v1/memories/search?namespace=tg:{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 (tg:{user_id}), content (user message + AI response). The scenario now builds memory for every Telegram user.
How do I trigger a Make.com scenario from Telegram messages?
Use the Telegram Bot module in Make.com (Watch Updates trigger) or connect via the Telegram Bot API webhook to a Make.com HTTP trigger. The Telegram Bot module is the simpler option — add your bot token and select the message trigger type.
How do I scope memory per user in a multi-user Telegram scenario?
Map the sender user ID from the Telegram trigger payload to the namespace field: tg:{user.id}. Each Telegram user ID is unique and stable. Map consistently in both the search and store HTTP modules so they use the same namespace.
Does retainr work with the Make.com HTTP module without extra setup?
Yes. Add an HTTP Request module, set the URL, method, and Authorization header with your API key. Map your scenario variables to the URL query parameters (for search) or request body (for store). No OAuth, no app installation.
Can I handle the /forget command in Make.com?
Yes. Add a Router after the Telegram trigger that checks if the message starts with /forget. In that branch, send an HTTP DELETE request to https://api.retainr.dev/v1/memories?namespace=tg:{user_id} to clear the user memory.
Can I share Telegram memory with other Make.com channels?
Yes. Use a consistent namespace like user:{email} across all your channels if you want shared memory. Use channel-specific prefixes like tg:{user_id} if you want separate memory pools per channel for the same user.
Give your Make.com Telegram scenario real memory
1,000 memory operations per month. Free forever. No credit card required.