Verify the safe path for Botpress security reports
Before sensitive details move any further, Notis checks whether the target GitHub repository accepts private vulnerability reports and tells you the result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
A security-related Botpress conversation creates immediate pressure, and manually checking repository settings adds uncertainty at the worst moment.
- Confirms the repository's private disclosure path quickly
- Reduces risky improvisation during a security escalation
- Provides a clear run report before sensitive follow-up
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis.
- 2Create an automation with a plain-language instruction to check private vulnerability reporting for the repository named in a Botpress security webhook.
- 3Choose the webhook trigger and a restricted channel for run reports.
- 4Test with a repository you control and verify the reported status.
Questions about this workflow
Does this submit the vulnerability report?
No. It only checks whether private vulnerability reporting is enabled for the specified repository.
Should the webhook include sensitive exploit details?
Keep the trigger payload minimal. The workflow only needs enough context to identify the repository and the requested readiness check.
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.