Watch Botpress issues as pull request commits arrive
Rapid PR iteration can outpace your mental checklist. Notis runs the same Botpress issue check after every newly added commit.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
LIST_BOT_ISSUES
Tool to list issues associated with a specific bot. use when you need to discover errors or configuration problems tied to a bot, optionally paginating through results.
Why this helps
During fast review cycles, it is difficult to remember which commit was followed by a Botpress check and which was not.
- Makes the bot-health check consistent across PR iterations
- Helps connect new diagnostic signals to a smaller change window
- Removes a repetitive follow-up from the review loop
Setup
Build it in a few focused steps.
- 1Connect GitHub and Botpress to Notis.
- 2Tell Notis in one automation prompt to list issues for the bot whenever a new commit is added to the selected pull request.
- 3Choose New Commit Added to Pull Request as the trigger and select your reporting channel.
- 4Push a test commit to the pull request and verify the Botpress issue report arrives.
Questions about this workflow
Does this detect commits after a force-push?
Yes. The GitHub trigger monitors newly added pull request commits, including force-push scenarios.
Will this comment on the pull request?
No. Notis reports the Botpress issue results through the channel selected for automation runs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Botpress. A trigger fires from one place; an action lands in another.
GitHub triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete File
Tool to delete a file by its id or key. use after confirming the file exists.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to get details of the authenticated account. use after confirming valid credentials.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
LIST_BOT_ISSUES
Tool to list issues associated with a specific bot. use when you need to discover errors or configuration problems tied to a bot, optionally paginating through results.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
LIST_CONVERSATIONS
Tool to list all conversations. use when you need to retrieve and page through chat threads.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
LIST_FILE_TAGS
Tool to list all tags used across all bot files. use when you need to retrieve or display file tag metadata; supports pagination via nexttoken.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
LIST_FILE_TAG_VALUES
Tool to list all values for a given file tag across all files. use after determining the tag name; supports pagination via nexttoken.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
LIST_PUBLIC_WORKSPACES
Tool to retrieve a list of public workspaces. use when browsing publicly available workspaces before selection.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
LIST_WORKSPACES
Tool to retrieve a list of workspaces. use when you need to list and page through your botpress workspaces, optionally filtering by handle.
Connect any two apps with Notis in the middle.
GitHub and Botpress, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botpress.