Route bot builds to the right GitHub runner
When a new Botpress workload needs specific runner capabilities, Notis adds the approved custom labels to the active repository runner.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add runner labels
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Why this helps
Specialized bot builds fail or queue on the wrong machine when runner labels are missing, yet updating them is an easy infrastructure task to forget.
- Makes approved bot workloads discover the intended runner
- Appends labels without removing the runner's existing labels
- Reduces setup gaps between workload approval and CI execution
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis, and confirm the repository runner is registered and active.
- 2Tell Notis which approved Botpress workload signals should add which custom labels to the named runner.
- 3Choose an incoming webhook trigger and a channel for infrastructure reports.
- 4Test with a non-critical custom label and confirm it appears on the runner.
Questions about this workflow
Will this remove existing runner labels?
No. The GitHub action appends new custom labels and leaves current labels in place.
Can it label an offline runner?
The target repository runner must be registered and active for the operation to work reliably.
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.