Know What Just Shipped Without Leaving Telegram
A commit lands on main and you don't know what changed until hours later when you pull. Get a Telegram alert the instant something ships so you can keep your local in sync and stay informed.
Trigger
Commit Event
Triggered when a new commit is pushed to a repository.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Your team ships multiple times a day on main. You don't know when they commit so your local branch gets stale. You waste time rebasing or merging conflicts when you finally pull.
- Know what shipped so you can plan your next work
- Pull main before conflicts pile up
- Stay current with team velocity and what's live
Setup
Build it in a few focused steps.
- 1Connect GitHub and Telegram to Notis.
- 2Ask Notis: 'Alert me in Telegram when someone commits to main', or create in the portal.
- 3Select 'Commit Event' as the trigger.
- 4Choose your Telegram channel for shipping notifications.
- 5Test by committing to main and verifying the alert appears in Telegram.
Questions about this workflow
Can I filter to only specific branches like main and staging?
Yes. Customize your automation to alert only on commits to main or specific branches.
Will I get spammed with a notification per commit?
One notification per commit. If that's too many, ask Notis to batch hourly or daily instead.
What information is included about the commit?
Notis includes the commit message, author, and a link to the diff so you know exactly what changed.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
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.
Edit Message
Edit text messages sent by the bot.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
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.
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.).
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.
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.
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 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.
GitHub and Telegram, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Telegram.