Check repository collaboration during access reviews
Notis can check the collaborator status of a user and repository you specify, then report the result alongside your Brex review context.
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 reviews take extra effort when repository membership must be checked one person at a time.
- Check whether a specified user collaborates on a repository.
- Review the result alongside Brex context you provide.
- Reduce manual repository-by-repository checking.
Setup
Build it in a few focused steps.
- 1Connect Brex and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe the Brex review context and GitHub users and repositories to check.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one real user and repository.
Questions about this workflow
Does this remove access when a user is a collaborator?
No. The available action checks collaborator status and does not remove access.
What information must I provide?
Specify the GitHub repository and username. Brex does not list a native trigger, so the review context must come from your instruction or webhook data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Brex to GitHub. A trigger fires from one place; an action lands in another.
Brex 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.
Brex 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.