Verify team access to a GitHub project
Know whether the people behind a plan can access the project it depends on.
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
Planning stalls when project permissions are assumed rather than checked.
- Check the exact organization, team, and project.
- Compare against an explicit required permission.
- Keep the workflow read-only.
Setup
Build it in a few focused steps.
- 1Connect Insighto ai and GitHub to Notis once.
- 2Create an automation to check the supplied team and classic project permission.
- 3Use an incoming webhook and select a report channel.
- 4Send one approved planning payload and review the result.
Questions about this workflow
Does the workflow grant project access?
No. It reports whether the supplied permission is already present.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Insighto ai to GitHub. A trigger fires from one place; an action lands in another.
Insighto ai 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.
Insighto ai 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.