Carry team access approvals into GitHub
When a Botpress access flow records the final decision, Notis updates the team's GitHub repository permission without leaving a tiny admin task behind.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Team access decisions often happen in conversation, while the actual GitHub permission update becomes a separate task that is easy to delay or misremember.
- Closes the gap between permission approval and execution
- Reduces repeated navigation through organization settings
- Reports each access change in a channel you already monitor
Setup
Build it in a few focused steps.
- 1Connect Botpress and your GitHub organization to Notis.
- 2Write one automation prompt describing which approved Botpress requests may update a team's repository permission and to what level.
- 3Pick an incoming webhook trigger and a run-report channel.
- 4Test with a non-critical repository and confirm the team's effective permission.
Questions about this workflow
Which permission levels are supported?
The GitHub action sets or updates a team's supported repository permission level, subject to the organization's repository rules.
Can this add a team from another organization?
No. The team must belong to the same GitHub organization as the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
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 Botpress and GitHub. Any combination from 1,000+ 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.