Back to Blog
2026-03-25 • 5 min read

Telegram Alerts for Cron Job Monitoring: A Practical Guide

A practical guide to how Telegram alerts actually work in QuietPulse: connect Telegram from the dashboard, send heartbeat pings from your jobs, and get notified when a run is missed.

How Telegram Alerts Work in QuietPulse

QuietPulse already has the Telegram bot integration built in. You do not need to create your own bot, generate a bot token, or look up a chat ID manually.

The actual user flow is:

  1. Create a job in the QuietPulse dashboard
  2. Add the generated heartbeat URL to your cron job or scheduled task
  3. Click Connect Telegram in the dashboard
  4. Open the QuietPulse bot link and press Start
  5. QuietPulse sends alerts to that connected chat when a job becomes MISSING

What QuietPulse Monitors

QuietPulse uses heartbeat monitoring for scheduled jobs.

That means:

  1. Your job calls a unique heartbeat URL after a successful run
  2. QuietPulse expects the next ping based on the job interval you configured
  3. If the ping does not arrive in time, the job moves from OK or LATE to MISSING
  4. Once the job is MISSING, QuietPulse sends a Telegram alert to your connected chat

The scheduler checks jobs every minute, so missed runs are detected automatically without adding any Telegram code to your app.

Step 1: Create a Job in the Dashboard

Start in the QuietPulse dashboard and create a new job.

For each job you configure:

  • Name: a label like "Nightly backup" or "Hourly sync"
  • Expected interval: how often the job should ping
  • Grace period: extra time before QuietPulse treats a late run as missing

After saving, QuietPulse gives you a unique heartbeat URL for that job.

https://quietpulse.xyz/ping/your-unique-token

Step 2: Add the Heartbeat URL to Your Job

Call the heartbeat URL after a successful run.

Simple example:

curl -s https://quietpulse.xyz/ping/your-unique-token

The important part is when you call it:

  • Ping only when the job really succeeded
  • Put the ping at the end of the workflow
  • Use a separate heartbeat URL for each monitored job

If a job crashes before that ping is sent, QuietPulse can detect the missing run later and alert you.

Step 3: Connect Telegram from the Dashboard

In the dashboard, click Connect Telegram.

QuietPulse then generates a secure Telegram deep link for your account and opens the bot in a new tab:

text 
https://t.me/quietpulse_bot?start=your-connect-token

That token is generated by QuietPulse and is used to link the Telegram chat to your account. In the current implementation, the connect token expires after 10 minutes, so if it expires you can simply generate a new one from the dashboard.

You do not need to copy a chat ID, configure a webhook, or register a bot yourself as a product user.

Once you press Start in Telegram, QuietPulse stores the chat connection and marks Telegram as connected for your account.

Step 4: What Alert You Actually Receive

When a monitored job is missing, QuietPulse sends a message like this:

text 
❌ Job "Nightly backup" missed.
Last ping: 2026-03-25T01:00:00.000Z
Time: 2026-03-25T02:07:00.000Z

This matches the current backend behavior:

  • the alert is sent only if Telegram is connected for that user
  • alerts fire when the job status becomes MISSING
  • if the job stays missing, QuietPulse avoids spamming continuously and only re-alerts after the job interval passes again

What Counts as OK, Late, or Missing

QuietPulse calculates job status from:

  • expected_interval_minutes
  • grace_period_minutes
  • last_ping_at

In practice:

  • OK: the heartbeat arrived on time
  • LATE: the expected time passed, but the grace period has not expired yet
  • MISSING: the heartbeat still has not arrived after the grace period

Telegram alerts are tied to the MISSING state, which helps reduce noise from short delays.

Best Practices for Real QuietPulse Setups

To get reliable Telegram alerts in QuietPulse:

  1. Use one job per real scheduled task
  2. Set the expected interval to match the real run frequency
  3. Add a sensible grace period so small delays do not become false alarms
  4. Ping the heartbeat URL only after success
  5. Reconnect Telegram from the dashboard if you disconnect or want to switch chats

If you reuse one heartbeat URL across unrelated tasks, alerts become harder to interpret.

Troubleshooting

I clicked Connect Telegram but do not get alerts

Check these first:

  • Did you press Start in the QuietPulse bot after opening the link?
  • Did the connect link expire before you used it?
  • Is the job actually sending heartbeat pings?
  • Is the job currently MISSING, not just LATE?

My job runs, but QuietPulse still alerts

Usually that means one of these:

  • the heartbeat URL is not being called on every successful run
  • the expected interval is shorter than the real schedule
  • the grace period is too small for your environment

I want to stop alerts

You can disconnect Telegram from the dashboard. QuietPulse also supports /disconnect in the bot, but the dashboard is the simplest path for users.

Conclusion

In QuietPulse, Telegram alerts are intentionally simple for the user: create a monitored job, connect Telegram from the dashboard, and send heartbeat pings from your cron job.

You do not manage bots or chat IDs yourself. QuietPulse handles that connection flow for you, then sends alerts when a job misses its expected heartbeat and becomes MISSING.