Check GitHub team project permissions
Keep planning access dependable so work does not stall at the moment someone needs to update it.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A planning project can quietly become inaccessible to the people doing the work, causing avoidable coordination delays.
- Protects planning continuity
- Finds access surprises early
- Reduces coordination delays
Setup
Build it in a few focused steps.
- 1Connect DeepSeek and GitHub to Notis once.
- 2In Automations, create a new automation.
- 3Write a prompt naming the teams and organization projects DeepSeek should check for expected permissions.
- 4Choose a recurring schedule and report channel.
- 5Test with one project and team.
Questions about this workflow
Does it modify project access?
No. The action checks whether a team has read, write, or admin project permission.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link DeepSeek to GitHub. A trigger fires from one place; an action lands in another.
DeepSeek 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.
DeepSeek 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.