from oficial page of n8n How to build a Telegram AI bot with n8n – Step-by-step tutorial

Haha, fair enough! 😄 I figured some ideas might be off the mark, but hey, that’s how brainstorming works, right? Let me throw a few more ideas your way. Haven’t tested them, but I guess they might work: 🤔 1. Engaging Multiple Clients Individually Okay, so if the Window Memory Node doesn’t quite fit here, maybe a Key/Value Memory Node could do the job? I mean, it sounds like it could store user-specific data like chat_id, conversation history, and even interaction timestamps.Alternatively, you might use a Google Sheets Node as a lightweight database, or go a bit more advanced with a PostgreSQL Node if you want something more scalable. ⏰ 2. Scheduling Follow-up Messages Every 2 Days at 8:30 AM So, if the Cron Node isn't the vibe, maybe the Schedule Trigger Node could work? I think you can set it up to trigger actions at specific times.Another guess: you could use a Wait Node combined with a Loop Node to create a more dynamic reminder system that only runs if certain conditions are met (like no response detected within a certain time window). 📬 3. Getting Notified When Clients Respond Besides Webhooks and Google Sheets, what about using the Telegram Send Message Node to DM yourself directly in a separate chat?Alternatively, you could integrate it with Slack if you prefer, or even set up a Gmail Node to shoot yourself an email whenever someone replies. I'm guessing this flexibility might help if you want notifications outside of Telegram. 🛑 4. Turning Off the Bot Once the Client Re-engages Okay, this one made me think a bit more. Instead of using a Switch Node alone, maybe combine it with a Function Node to track when the last response was received.You could write a small JavaScript snippet to check if there was activity in the past X days. If not, deactivate the Cron Node or any other scheduled workflow dynamically. Sounds like it could work! 🧠 Bonus Idea: Alternative to Window Memory Node - Redis Node: If performance matters, maybe caching conversation context in Redis could work. - File Node: For simpler cases, just saving context in a JSON file might be enough. - n8n Data Store Node: Haven’t tried it, but logically, it sounds like a native option for storing session-based memory.

100 k on the way, we can help with that!

Perfect

Of course! Just to give you some additional ideas—right now, in places like Ibiza, where preparations for the tourism season (March-April to October) are already underway, hotels struggle greatly with staff shortages. AI-powered booking agents are a fantastic and scalable solution. The lack of personnel is a major issue in destinations like Ibiza, Menorca, Mallorca, and the Greek islands. Roles such as billing assistants and stock control managers are essential, yet most people have no idea about the tools available today. The same applies to all hospitality-related services. Feel free to chat with me—these are definitely applicable ideas. As for my own business models, I will share them in the appropriate space to respect the rules, as they are important. I'll be here if you’d like to discuss this further!

Hi everyone! You can reach me at [email protected]. I intend to stay here and learn, as I’m still very new. From what I can see, @Nate Herk shares the same point of view as I do, along with the optimism and focus we really need. Remember: If you want to go fast, go alone. If you want to go far, go together.

My response is that @Jessica Leighty Leighty has explained it very clearly—this is a perfect example of when self-hosting is a good idea. Otherwise, it really depends on the plan you have for the number of n8n automation flows (correct me if I’m misunderstanding).