The moment it happens
Get GitHub issue updates on Telegram
Telegram messages you when an issue in your repository is opened, commented on or closed, with the title and a link.
- Runs
- The moment it happens
- Apps
- GitHub, Telegram
- AI
- Not needed
- Access
- GitHub webhook admin on repo; bot token
Send this to your assistant
Create a ClickRuntime automation: message me on Telegram whenever an issue in acme/app is opened, gets a comment, or is closed.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A developer maintains a side project with a growing number of users. GitHub's email notifications get lost among work mail, so new bug reports wait days for a first reply and users assume the project is abandoned.
A Telegram message for each issue event reaches them wherever they are, without the clutter of email. Quick replies keep users engaged, and they can decide from the message whether something needs attention now.
What you get out of it
Faster first replies
Seeing a new issue on your phone means you can acknowledge it the same day. Users feel heard.
Out of the email pile
Issue updates no longer compete with work mail. They arrive in a chat you check anyway.
Short and readable
Each message has the repository, what happened, the title and a link. You know at a glance whether to act.
Works for teams too
Send updates to a group chat and the whole team sees them. Nobody needs to watch the repository.
How it works
What happens, step by step
When an issue is opened, commented on or closed, GitHub notifies ClickRuntime straight away.
ClickRuntime checks the notification really came from GitHub.
It builds a short message with the repository, what happened, the issue title and a link.
The message is sent to your Telegram chat by your bot.
Before it runs live
- Connect GitHub
- Connect Telegram
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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 GitHub and Telegram steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, verify
CHAT_ID = "123456789"
def telegram(text):
http.post(f"https://api.telegram.org/bot{credentials.secret('TELEGRAM_BOT_TOKEN')}/sendMessage",
json={"chat_id": CHAT_ID, "text": text, "disable_web_page_preview": True}).raise_for_status()
@on_event
def handle(event):
if not verify.github(event.body, event.header("X-Hub-Signature-256"), credentials.secret("GITHUB_WEBHOOK_SECRET")):
return {"ignored": "bad signature"}
kind, body = event.header("X-GitHub-Event"), event.json
if kind not in ("issues", "issue_comment") or body["action"] not in ("opened", "created", "closed", "reopened"):
return {"ignored": True}
issue, repo = body["issue"], body["repository"]["full_name"]
if kind == "issue_comment":
text = f"💬 {body['comment']['user']['login']} commented on {repo}#{issue['number']} {issue['title']}\n{body['comment']['body'][:300]}"
else:
icon = {"opened": "🆕", "closed": "✅", "reopened": "🔁"}[body["action"]]
text = f"{icon} {repo}#{issue['number']} {body['action']}: {issue['title']}"
telegram(f"{text}\n{issue['html_url']}")
return {"sent": True}FAQ
Common questions
Can I limit it to certain labels?
Does it include the comment text?
Can it cover pull requests as well?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Back up Telegram bot messages to GitHub
Every message your Telegram bot receives is saved, and at 02:00 the day's messages are committed to a private GitHub repo as one file.
See how it worksSave notes from Telegram to a GitHub repo
Send your bot a thought, link or to-do, and it is committed to your GitHub notes repo as a Markdown file you can pull into Obsidian or any editor.
See how it worksFile incoming bug reports as GitHub issues with a Telegram alert
Each bug report sent to your trigger link becomes a GitHub issue with a clear title, severity and labels, and Telegram alerts you.
See how it worksKeep exploring
Set up “Get GitHub issue updates on Telegram” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.