Confirm repository access for people found in public research
Use public partner or contributor research to prompt a quick check of collaborator status in the relevant repository.
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
Public contributor information and repository access lists can diverge, leaving access reviews dependent on memory.
- Check repository collaborator status without a manual lookup
- Support a consistent partner access review
- Keep findings and status in the same run report
Setup
Build it in a few focused steps.
- 1Connect Bright Data MCP and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the collaborator review.
- 3Tell Notis how to identify the GitHub username and repository from each finding, and to check collaborator status for those pairs.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real finding and a repository and user you can verify.
Questions about this workflow
Will this add or remove repository access?
No. The GitHub event checks whether a user is a collaborator; it does not change repository access.
What if a source uses a display name instead of a GitHub username?
Provide a matching rule or include the username in the webhook request. A display name alone may not identify the correct GitHub account.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bright Data MCP to GitHub. A trigger fires from one place; an action lands in another.
Bright Data MCP 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.
Bright Data MCP 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.