Answer repository access questions without digging
When someone asks your Botpress assistant for repository access, Notis checks their current GitHub collaborator status and reports the answer.
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
Founders lose time bouncing between access conversations and repository settings just to determine whether a requester already has access.
- Prevents duplicate or unnecessary access changes
- Returns a concrete collaborator status to your chosen channel
- Keeps access triage moving without opening repository settings
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis once.
- 2Ask Notis to check GitHub collaborator status whenever the Botpress access-request webhook provides a repository and username.
- 3Choose an incoming webhook trigger and the channel that should receive the result.
- 4Try one known collaborator and verify that the workflow reports the expected status.
Questions about this workflow
Does this grant repository access?
No. It performs a read-only collaborator check so you can make a deliberate access decision afterward.
What does a not-found result mean?
It can mean the user is not a collaborator or that the repository or username could not be found, so the run report should be reviewed before follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress 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 Botpress 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.