Check GitHub collaborator access in a recurring routine
Replace the nagging question of access with a small scheduled confirmation.
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 gaps often surface only when someone is blocked and asking for help.
- Finds access gaps early
- Avoids emergency access requests
Setup
Build it in a few focused steps.
- 1Connect Habitica and GitHub to Notis once.
- 2Create a new automation in the portal.
- 3Write a prompt to check collaborator access for the specified repository and person.
- 4Choose a recurring trigger and reporting channel.
- 5Test with a collaborator whose access is known.
Questions about this workflow
Can I check more than one person?
Describe the people and repositories you want Notis to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Habitica to GitHub. A trigger fires from one place; an action lands in another.
Habitica 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 Habitica 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.