Recheck repository access tied to Bubble records
Make access reviews easier to complete by checking the users and repositories your Bubble app tracks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Why this helps
Access records become stale, leaving teams unsure whether the right people still have repository collaboration access.
- Surface collaborator access that may need review.
- Keep the review focused on users and repositories tracked in Bubble.
- Turn a recurring check into a clear report for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Bubble and GitHub once in the Notis portal.
- 2Create an automation and describe which Bubble user and repository records to verify for collaborator access.
- 3Choose a Notis cron trigger and set the review cadence.
- 4Choose where run reports should go.
- 5Test with one real user and repository and confirm how the result is reported.
Questions about this workflow
Does this remove access that should no longer exist?
No. The selected GitHub action checks collaborator status; it does not remove access.
What does a not-found result mean?
GitHub can return not found when a user or repository is invalid, as well as when the user is not a collaborator. Verify the references before interpreting the result.
How should we use the report?
Use it as a review queue, then handle any required access changes through an approved process.
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.