Turn release lessons into required GitHub checks
When a Botpress release review confirms a missing safeguard, Notis adds the already reported check context to the protected GitHub branch.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add status check contexts
Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.
Why this helps
Teams identify a necessary release check during a conversation, then forget to make it part of branch protection before the next release.
- Converts an approved release lesson into an enforceable guardrail
- Reduces reliance on someone remembering a settings change
- Keeps the policy update tied to a documented review outcome
Setup
Build it in a few focused steps.
- 1Connect Botpress and the GitHub repository to Notis.
- 2Create an automation that tells Notis to add only previously reported check contexts approved by the Botpress release-policy webhook.
- 3Select the incoming webhook trigger and a channel for branch-protection change reports.
- 4Test on a non-production protected branch with a context that has already reported.
Questions about this workflow
Can this require a brand-new check context?
The context must have been reported previously in GitHub before it can be added to protected branch requirements.
Does this replace existing required checks?
This action adds status-check contexts to the branch's protected configuration; your prompt should identify the exact approved contexts.
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.