Automatically Grant Actions Secrets Access on Onboarding
A new engineer joins your Telegram group. Notis immediately adds them to the secret-access list for your org's GitHub Actions secrets. They can deploy on day one.
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
Add repo to org secret with selected access
Adds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.
Why this helps
New team members lack access to deployment secrets, blocking their ability to contribute. Neurodivergent founders need frictionless onboarding that doesn't require context-switching.
- New members get secret access automatically—no manual approval needed
- Deployment pipelines work immediately for new team members
- Reduces dependency on admins for secret access approvals
- Keeps team velocity high by removing onboarding friction
Setup
Build it in a few focused steps.
- 1Connect Telegram and GitHub to Notis.
- 2Create an automation with the prompt: 'When someone joins this Telegram group, add them to the list of users with access to GitHub Actions secrets in our organization.'
- 3Select Telegram (New Chat Member) as the trigger.
- 4Test by inviting a test member and confirming they're added to the secret access list.
Questions about this workflow
Can I control which secrets they access?
Yes—create separate automations for different secret groups or mention specific secrets in the workflow setup.
Is this secure?
Yes—you control who gets added to Telegram and when. Notis respects GitHub's existing secret visibility settings.
Can I remove someone's access easily?
Yes—remove them from Telegram and create a separate automation to revoke secret access, or do it manually in GitHub org settings.
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.