Update Branch Protection Rules from Edited Telegram Messages
You announce branch access changes in Telegram, then realize you made a mistake. Edit your message and Notis updates the GitHub protection rules to match.
Trigger
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Action
Add user access restrictions
Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]` removes all restrictions.
Why this helps
Async communication about access changes often goes out of sync with GitHub. Neurodivergent founders need editable workflows that propagate corrections automatically.
- Branch protection rules update when you edit Telegram messages
- Corrections propagate automatically without manual fixes
- Keeps access rules synchronized with latest decisions
- Reduces need for follow-up corrections in GitHub
Setup
Build it in a few focused steps.
- 1Connect Telegram and GitHub to Notis.
- 2Create an automation with the prompt: 'When I edit a Telegram message about who can push to a branch, update the GitHub branch protection rules to allow those users.'
- 3Select Telegram (Message Edited) as the trigger.
- 4Test by sending a message about branch access, editing it, and verify the change in GitHub protection settings.
Questions about this workflow
Can I specify different access levels?
Yes—mention the access level in your message: 'main branch: maintainers only' and Notis applies that rule.
What if I mention a user who doesn't exist?
Notis will ask for clarification or suggest the closest matching GitHub user.
Can I remove access by editing my message?
Yes—edit the message to remove usernames and Notis removes them from branch access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to GitHub. A trigger fires from one place; an action lands in another.
Telegram triggers
GitHub actions
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Telegram and GitHub. 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 GitHub.