Verify GitHub Team Access to a Project
Send Notis the project access question and it checks whether the team has read, write, or admin permissions in GitHub.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check team permissions for a project
Checks if a team has 'read', 'write', or 'admin' permissions for an organization's specific classic project, returning the project's details if access is confirmed.
Why this helps
Project access questions create extra back-and-forth when the answer is buried in organization settings.
- Check project access when a question comes in.
- See whether the team has read, write, or admin permissions.
- Keep access review results in one report channel.
Setup
Build it in a few focused steps.
- 1Connect Api labz and GitHub once in the Notis portal.
- 2Create a named automation in Automations, New Automation.
- 3Tell Notis in one instruction which organization, team, and classic project to check for permissions.
- 4Choose the notis_webhook trigger and select a report channel.
- 5Test with one real team and project.
Questions about this workflow
Does this apply to every GitHub project type?
The listed action checks permissions for an organization's specific classic project.
Will it grant access if the team has none?
No. This action checks access and does not update permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api labz to GitHub. A trigger fires from one place; an action lands in another.
Api labz 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.
Api labz 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.