Keep Botpress repository access understandable
On your chosen schedule, Notis checks the GitHub permissions inherited by teams working on Botpress projects and reports what needs attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check team permissions for a repository
Checks a team's permissions for a specific repository within an organization, including permissions inherited from parent teams.
Why this helps
Team permissions drift as projects and responsibilities change, but auditing inherited GitHub access is tedious enough to keep getting postponed.
- Surfaces permission drift before it becomes an incident
- Includes access inherited through parent teams
- Replaces sporadic settings reviews with a consistent report
Setup
Build it in a few focused steps.
- 1Connect Botpress and your GitHub organization to Notis.
- 2In one plain-language prompt, ask Notis to check the relevant teams' permissions for repositories that support your Botpress projects.
- 3Pick a weekly or monthly schedule and a private channel for the audit report.
- 4Run the automation once now and compare one result with GitHub.
Questions about this workflow
Does this change team permissions?
No. It checks and reports a team's effective repository permissions, including inherited access.
Can I audit several bot repositories?
Yes. Describe the repositories and teams to review in the automation prompt, and choose a schedule that matches how often access changes.
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.