Match GitHub team access to active Bubble work
When a team takes ownership of a project, give that team the agreed GitHub access without a separate admin session.
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 ownership changes in the project plan, but repository permissions lag behind and block execution.
- Keeps access consistent with current ownership
- Reduces permission-related interruptions
- Makes handoffs faster across teams
Setup
Build it in a few focused steps.
- 1Connect Project bubble and GitHub to Notis.
- 2Open a new automation in the portal or ask Notis to create it.
- 3Describe in one prompt how an approved Project bubble team-assignment webhook should update that team's GitHub repository permission.
- 4Select Incoming webhook, choose a run-report channel, and test with one team and repository.
Questions about this workflow
Which permission levels are supported?
The action can set the valid GitHub team permission level for the repository, provided the team belongs to the organization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Project bubble to GitHub. A trigger fires from one place; an action lands in another.
Project bubble 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 Project bubble 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.