Assign GitHub Roles Automatically When Someone Joins Telegram
A new contractor joins your Telegram group. Instead of remembering to go to GitHub settings and assign them a role, Notis does it in seconds. They're ready to contribute immediately.
Trigger
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Action
Assign an organization role to a user
Assigns a specific organization role to a user who is a member or an outside collaborator in a github organization, using a valid role id.
Why this helps
Onboarding new collaborators requires jumping between tools to set permissions, and missed steps mean people lack the access they need. For neurodivergent founders, this friction causes bottlenecks.
- New team members get GitHub access instantly—no manual provisioning steps
- Eliminates the cognitive load of remembering which roles to assign
- Keeps everyone in sync across Telegram and GitHub without extra work
- Reduces onboarding delays that otherwise stall new contributors
Setup
Build it in a few focused steps.
- 1Connect Telegram and GitHub to Notis.
- 2Create an automation in the portal with the prompt: 'When someone new joins this Telegram group, assign them the contributor role in our GitHub organization.'
- 3Select Telegram (New Chat Member) as the trigger and choose a Notis channel for notifications.
- 4Test by inviting a test user to your Telegram group and verify the role appears in GitHub organization settings.
Questions about this workflow
Can I assign different roles to different people?
Yes. Include the person's role in your Telegram invite message, or Notis can ask you in the group which role to assign.
What if someone is already a GitHub org member?
Notis updates their role if needed, or confirms they're already set up correctly.
Can I undo this if I make a mistake?
Yes—you can remove or change roles in GitHub org settings at any time.
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.