Telegram Notifications
Get failure alerts straight to your Telegram — available on Pro and Business plans. One setup, all your jobs covered.
Why Telegram?
Email is great for documentation, but when a cron job fails at 3 AM, you need something you'll actually notice. If you're building Telegram bots or just live in the app day-to-day, a Telegram alert is instant and hard to miss. No inbox to check, no risk of it landing in spam.
How to set it up
- Create a Telegram bot — open Telegram, message
@BotFather, run/newbot, and follow the prompts. You'll get a bot token like7123456789:AAxxxxxxxxxxxxxxxxxxxxxx. - Get your chat ID — send any message to your new bot, then open this URL in a browser (replace
TOKENwith yours):https://api.telegram.org/botTOKEN/getUpdates
Find thechat.idin the response. It's a number like123456789. If you want alerts in a group chat, add the bot to the group first and it'll appear ingetUpdates. - Connect in QuzenixCron — go to
Settings → Telegram, paste the bot token and chat ID, and click Save & Test. You'll get a test message immediately confirming it works.
sendMessage using your bot, so the alert looks like it came from your own bot.What the alert looks like
When a job fails (after exhausting all retries), you'll receive a message like:
🚨 Job Failed: Telegram Bot Keepalive URL: https://your-bot.onrender.com/ping Status: 503 Service Unavailable Attempts: 4 of 4 Time: 2026-04-27 03:12 UTC → View job in QuzenixCron
Per-job control
Telegram alerts follow the same settings as email alerts. In the job edit form under Reliability:
Notify on failure — toggle off to silence all alerts (email and Telegram) for that specific job.
Notify after N failures— set to 2 or 3 if the job is occasionally flaky. You won't get pinged for a one-off hiccup, only when it's been broken multiple times in a row.
Disconnecting
Go to Settings → Telegram and click Disconnect. All jobs immediately fall back to email-only alerts — nothing else changes.