I’m planning to set up a Telegram bot that utilizes a webhook for real-time message handling. I’m curious if Heroku’s free tier can serve as the endpoint for this bot’s operations. The bot is being developed using Node.js, and I would appreciate insights on configuring the webhook properly so that incoming text messages are processed efficiently.
i tested hosting my telegram bot on heroku free, works if uptime pings are used. the dyno sleep issue is real so you’ll see delays sometimes. proper ssl config is a must. good for testing, not toooo heavy use.
I have also experimented with hosting my Telegram bot on Heroku’s free plan using Node.js. My experience indicates that while it is feasible, primarily for small-scale or demo projects, the challenge remains the sporadic dyno shutdowns, which can cause interruptions if not managed appropriately. I made sure to adjust my webhook configuration and used a reliable external service to keep the bot awake during long periods of inactivity. It is important to ensure that your SSL certificates are correctly set up and that you monitor the bot regularly to catch any downtime issues.
After working on a similar project, I can say that it is feasible to host a Telegram bot on Heroku’s free tier using Node.js, but it requires a few workarounds. I encountered the dyno idle problem which can lead to sporadic downtimes, so I integrated a simple workaround using a scheduled task to periodically send requests to the bot, keeping it active. Although the SSL configuration must be correct, and you may need to monitor your bot more closely, this setup can be effective for development and low-traffic use.
i used heroku free for my bot and it’s ok for testing low traffic. dyno sleep though is a hassle. if you plan prod use, consider a paid plan or alternative host
Based on personal experience, it is possible to host a Telegram bot with webhook functionality on Heroku’s free plan using Node.js. The primary challenge is that free dynos tend to sleep after periods of inactivity, which could interrupt your real-time message handling. In my implementation, I relied on an external uptime monitor to periodically wake the dyno, ensuring that the webhook endpoint remained responsive. Additionally, proper SSL configuration is necessary for Telegram webhooks. Overall, while viable for smaller projects or testing, careful planning is required to handle potential downtime issues.