Turn approved Botpress onboarding into GitHub access
Once your Botpress flow confirms an approved contributor, Notis adds that GitHub user to the intended repository with the permission described in your instruction.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Approved contributors can wait for hours or days because the final repository invitation is a small administrative task buried among higher-priority work.
- Completes approved onboarding while the decision is still fresh
- Reduces forgotten repository invitations
- Keeps permission intent documented in a reusable automation prompt
Setup
Build it in a few focused steps.
- 1Connect the approved Botpress workspace and GitHub account to Notis.
- 2Create an automation that tells Notis to add only approved requesters to the repository and permission level named by your onboarding policy.
- 3Select an incoming webhook trigger and a channel where access changes will be reported.
- 4Test with a controlled repository and an approved test contributor.
Questions about this workflow
Can this update an existing collaborator's permission?
Yes. GitHub's action can add a new collaborator or update the permission of an existing collaborator where repository ownership supports it.
Will every request be accepted automatically?
Only if it matches the approval condition you state in the prompt. Design the Botpress webhook so it is sent after your required approval step.
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.