Review team access on Bubble-tracked GitHub repositories
Bring team permission checks into a recurring review of the repositories and teams your Bubble app tracks.
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 access can drift as projects change, making it hard to remember which repository permissions need a second look.
- Make team access checks easier to revisit.
- Focus on team and repository pairs identified in Bubble.
- Review inherited as well as directly configured permissions.
Setup
Build it in a few focused steps.
- 1Connect Bubble and GitHub once in the Notis portal.
- 2Create an automation and describe which organization teams and repositories to check using Bubble records.
- 3Choose a Notis cron trigger and set the review cadence.
- 4Choose where run reports should go.
- 5Test with one real organization team and repository.
Questions about this workflow
Does this change team permissions?
No. It checks a team's permissions for a repository, including permissions inherited from parent teams.
Can it check personal repositories?
This action is for a team and a repository within an organization.
What if Bubble does not include a team slug?
Provide the team's organization slug in the Bubble data or automation prompt; the check needs a valid team and repository reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bubble to GitHub. A trigger fires from one place; an action lands in another.
Bubble triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Bubble and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.