The moment it happens

Get error alerts from your tools on Telegram

Any system that can send to a link can now alert you on your phone.

Runs: The moment it happens
Apps: Telegram
AI: Not needed
Access: bot token

Send this to your assistant

Create a ClickRuntime automation: give me a link my tools can send errors to. When one arrives, send me a Telegram message with the service name, error and link.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A developer runs a server, a cron job, a payment webhook and a deployment pipeline. Each of them can fail, and each has its own way of reporting: email, a log file, a dashboard. When something breaks overnight, the alert sits in a mailbox that nobody checks until morning. Some tools offer no alerting at all, only the ability to call a webhook.

ClickRuntime gives you a link. Any system that can call a webhook sends its error there, ClickRuntime formats the name, the error message and a link into a clean note and sends it to your Telegram. It also keeps a count of alerts using counters, so a weekly figure shows which systems fail most.

It suits developers and small teams who want one reliable place for alerts from many sources.

What you get out of it

One alert channel for everything
Instead of checking five systems, you get everything in Telegram. A single habit covers every tool that can send a webhook. One habit, one place to look, regardless of how many tools you run, and nothing to remember for each new service.
Errors reach you within seconds
Telegram notifications arrive on your phone immediately and are hard to miss. A failed job at night gets noticed in time to fix it before users see the effect. Fast notice means a shorter outage for your users, and a failed batch job gets a fix before the morning shift starts.
Even simple tools can alert
Any system that can make an HTTP request counts, from a shell script to a hosted service. Tools with no alerting of their own gain it instantly. Quickly adding alerting to a legacy script, a shell cron job or an old service is a real convenience for any developer.
Alerts are readable
The name, error and link are formatted into a short message you can understand on a lock screen. You can often tell whether something is serious without opening anything. You can judge severity at a glance from the lock screen, without logging in anywhere or opening a laptop.
Weekly counts show weak spots
Counters track how often each source fails. A job that alerts twelve times a week is an obvious candidate for a proper fix. A visible trend of failures supports the case for fixing a root cause, rather than restarting the same job again.

How it works

What happens, step by step

When one of your tools reports an error to ClickRuntime, the automation starts straight away.
It picks out the service name, the error message and a link to the logs.
An alert is sent to your Telegram chat with those details.
It also keeps a count of errors, so you can see how many came in each week.

Before it runs live

Connect Telegram
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get error alerts from your tools on Telegramjust nowSucceeded

Telegram · Errors🚨 billing-api: Timeout calling payments provider after 30s logs.example.com/run/8812

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Telegram steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

error_alert_forwarding_to_telegram.pyexample

from clickruntime import on_event, http, credentials

CHAT_ID = "YOUR_CHAT_ID"

def tg(method, **params):
    r = http.post(f"https://api.telegram.org/bot{credentials.secret('TELEGRAM_BOT_TOKEN')}/{method}", json=params)
    r.raise_for_status()
    return r.json()["result"]

@on_event
def handle(event):
    e = event.json or {}
    text = f"🚨 {e.get('service', 'unknown')}: {str(e.get('error', ''))[:500]}"
    if e.get("url"):
        text += f"\n{e['url']}"
    tg("sendMessage", chat_id=CHAT_ID, text=text)
    return {"sent": True}

FAQ

Common questions

What does my system need to send?

A simple HTTP POST to the link with a body that includes a name and an error message, in JSON or form format. A link to logs or a dashboard is optional but makes the Telegram message more useful.

Can I stop duplicate alerts from the same error?

Yes. A cooldown can suppress identical messages from the same source for a set time, for example ten minutes. That avoids a flood when a failing job retries rapidly, while still telling you the first time.

Can alerts go to a group instead of just me?

Yes. Send to a Telegram group or channel by adding the bot there and using its chat ID. Everyone on call then sees the alert at the same moment, which suits small teams. Group chats also keep the alert history visible to newcomers.

What permissions does it need?

bot token. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens