Catch CI Breaks Before They Break Your Day
Your workflow fails silently and you don't know until tomorrow morning when you try to merge something else. Get a Telegram alert the moment CI fails so you can fix it while the error is still in your head.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
GitHub Actions workflow runs in the background and fails. You don't see it until the next day when you're trying to deploy and discover the build is broken. Now you've got to context-switch hard and burn time.
- Fix build failures immediately while the error is fresh
- Stop discovering broken builds when you're ready to ship
- Keep development velocity high by not letting CI silently break
Setup
Build it in a few focused steps.
- 1Connect GitHub and Telegram to Notis.
- 2Tell Notis: 'Alert me in Telegram if a workflow run fails', or create the automation in the portal.
- 3Select 'GitHub Workflow Run State Changed' as the trigger.
- 4Specify your Telegram notification channel.
- 5Test by making a commit that fails CI and confirm the failure alert arrives.
Questions about this workflow
Will I get notified for every workflow or just the main branch?
You can configure this. Most teams alert on main branch only to avoid noise.
What if I only care about failed runs, not successful ones?
Perfect. Tell Notis to only alert on failures and you won't get spammed with success messages.
Can I get details about what failed in the Telegram message?
Yes. Notis can include the failure reason and a link to the full logs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Telegram. A trigger fires from one place; an action lands in another.
GitHub triggers
Telegram actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete Message
Delete a message, including service messages, with certain limitations.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Edit Message
Edit text messages sent by the bot.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just GitHub and Telegram. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.