Check GitHub collaborator access from a Gist request
Get a quick answer on access status before turning a simple question into a support thread.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 requests often create extra back-and-forth when nobody knows whether permission already exists.
- Avoids duplicate invitations
- Speeds up access triage
- Keeps decisions documented
Setup
Build it in a few focused steps.
- 1Connect Gist and GitHub to Notis once.
- 2Open Automations and create a new one.
- 3Write a prompt asking Notis to check whether the user and repository named in an incoming Gist request are already collaborators.
- 4Choose Incoming webhook and a report channel, create it, and test a real access request.
Questions about this workflow
Will it grant access?
No. This workflow only checks collaborator status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gist to GitHub. A trigger fires from one place; an action lands in another.
Gist 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 Gist 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.