Keep Botpress bug reports visible in GitHub
When your bot flags a real product problem, Notis adds the right GitHub labels to the matching issue so it does not disappear into a chat transcript.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Important bugs surfaced in Botpress conversations are easy to forget once the conversation closes, leaving founders to re-read transcripts and repeat triage.
- Makes customer-reported bugs instantly recognizable in the backlog
- Preserves urgency and product area context from the Botpress escalation
- Removes a repetitive handoff between support conversations and engineering
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis once in the portal.
- 2Create an automation and tell Notis in plain language which Botpress bug escalations should add labels to the matching GitHub issue.
- 3Choose an incoming webhook as the trigger and select the channel where Notis should report each run.
- 4Send one real Botpress bug escalation through the webhook and confirm the expected labels appear in GitHub.
Questions about this workflow
Does this create a new GitHub issue?
No. This workflow adds labels to an existing matching issue, such as one referenced by the Botpress escalation or identified by your plain-language instruction.
Can the labels reflect severity or product area?
Yes. Describe the labeling logic in the automation prompt, and Notis can interpret the Botpress context and apply existing or newly created GitHub labels.
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.