Skip to content
ClickRuntime

Connect GitHub to Telegram

Telegram is where many developers get their personal alerts, because it is fast, quiet and on every device. Connecting GitHub to a Telegram bot sends issue updates, backup results, fork status and daily summaries to your phone without the noise of GitHub's own notifications.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with GitHub and Telegram

Issue updates, daily summaries, bug alerts, backups and fork checks, from GitHub to a Telegram chat. These are ready-made starting points. Anything else you can describe works too.
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.

See how it works
On a schedule

Back up to GitHub with Telegram alerts

Every day your exports are saved to a GitHub repository, and Telegram tells you which files changed.

See how it works
On a schedule

Get told on Telegram when your forks fall behind

Telegram tells you when one of your GitHub forks falls behind the original project, and by how many commits.

See how it works
On a scheduleAI

Get a daily summary of merged work on Telegram

Each morning Telegram sends a short summary of the pull requests merged in your repository yesterday.

See how it works
The moment it happensAI

File 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 works
The moment it happens

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 works
The moment it happens

Save 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 works
Every 5 minutes

Get a Telegram alert when a GitHub Actions run fails

Every 5 minutes ClickRuntime checks your repos for failed GitHub Actions runs and sends a Telegram message with the branch, commit and a link to the logs.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with GitHub and Telegram, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any GitHub and Telegram automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between GitHub and Telegram in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Only message me on Telegram when a GitHub Actions run fails on main twice in a row, and include the failing step.

Each evening, send me a Telegram digest of new issues across my repos, with AI tagging each as bug, question or feature request.

Use cases

Why people connect GitHub and Telegram

How the two apps work together

  • GitHub webhooks send events such as pushes, workflow runs, issues and releases to a ClickRuntime trigger link.
  • The script filters and formats the event and sends it through your Telegram bot to a chat, group or channel.
  • Messages to your bot can also reach a trigger link, so a command in Telegram can create a GitHub issue.

  • Deploy and CI results on your phone

    Solo developers get a Telegram message when a GitHub Actions workflow fails on the main branch. The message names the workflow, commit and author with a link to the run.

  • New issues for open source maintainers

    Maintainers receive new issues and pull requests from their repositories in a private Telegram chat. They can triage from their phone without opening email.

  • Release announcements to a community group

    Projects with a Telegram community post release notes to their group when a GitHub release is published. The post includes the tag and a short changelog.

  • Star and fork milestones

    Indie makers track repository stars and forks and get a Telegram message at milestones like 100 or 1,000 stars.

More apps

GitHub, Telegram and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Release notes to Telegram and Discord

When we publish a GitHub release, post the release notes to our Telegram channel and our Discord #announcements channel.

Production errors and fixes in one chat

Send new Sentry errors to my Telegram, and when a GitHub PR that mentions the Sentry issue ID is merged, send a follow-up message.

Deploy status from Vercel and GitHub

When a Vercel production deploy fails, message me on Telegram with the GitHub commit message and author.

Setup

Connect GitHub and Telegram once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

GitHub

Developer / Source control

  1. In GitHub, open your profile picture, then Settings, Developer settings, Personal access tokens, Fine-grained tokens, and choose Generate new token.
  2. Give it a name and an expiration, and choose the resource owner (you or your organization).
  3. Under repository access, pick only the repos the automation needs, then set the minimum permissions, such as Issues, Pull requests or Contents.
  4. Generate the token and copy it.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for GitHub.

Telegram

Messaging

  1. In Telegram, open a chat with @BotFather and send /newbot.
  2. Choose a name and a username for your bot, then copy the token BotFather sends (it looks like 123456:ABC-...).
  3. Open your new bot and press Start, so it is allowed to message you. For groups or channels, add the bot and give it admin rights if it should post or delete.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the bot token.

FAQ

Questions about connecting GitHub and Telegram

Do I need my own Telegram bot?
Yes. Create one with Telegram's BotFather in a minute, then save its token as a secret in your ClickRuntime dashboard. Messages come from your bot, to you or a group you add it to.
Can the messages go to a group?
Yes. Add your bot to the group and use the group's chat id. Everyone in the group sees the updates.
Does it work with private repositories?
Yes, as long as the GitHub account you connect can read them.
Will I get a message for every small change?
Only for the events each automation is set up for. You can narrow them further, for example to issues with a certain label.
Can I create GitHub issues from Telegram?
Yes. Messages sent to your bot can reach a ClickRuntime trigger link, and the script can create an issue from the text, for example after a /bug command.
Can it watch several repositories?
Yes. Add the webhook to each repository or to the organization, and the script can tag each message with the repository name.
How fast do the messages arrive?
GitHub webhook events are handled as they arrive. If you prefer scheduled checks instead, they run every 5 minutes or slower.

Related pages

Keep exploring

Tell your assistant what GitHub and Telegram should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude