Check Botpress conversations as deployments change state
Give every release a lightweight customer-signal check. Notis lists recent Botpress conversations when GitHub posts a deployment status, keeping feedback close to the release moment.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
LIST_CONVERSATIONS
Tool to list all conversations. use when you need to retrieve and page through chat threads.
Why this helps
Release work consumes attention, so founders often miss the first chatbot conversations that reveal confusion or regressions.
- Places customer conversations next to deployment context
- Makes post-release review a repeatable habit
- Reduces the need to remember a separate Botpress check
Setup
Build it in a few focused steps.
- 1Connect GitHub and Botpress to Notis once.
- 2In Automations, write one instruction asking Notis to list Botpress conversations when GitHub creates a deployment status and summarize the review queue.
- 3Choose New Deployment Status Created as the trigger and select your preferred reporting channel.
- 4Test with one staging deployment status and confirm that Notis retrieves the conversation list.
Questions about this workflow
Can I focus this on production deployments?
Yes. Identify the production deployment in the trigger setup and make the desired production-only outcome explicit in the prompt.
Does this analyze every conversation automatically?
The Botpress action retrieves conversation records. Your prompt can ask Notis to present the most useful review queue from the returned data.
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
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.
Delete File
Tool to delete a file by its id or key. use after confirming the file exists.
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.
Get Account
Tool to get details of the authenticated account. use after confirming valid credentials.
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_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.
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_CONVERSATIONS
Tool to list all conversations. use when you need to retrieve and page through chat threads.
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_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.
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_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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
LIST_PUBLIC_WORKSPACES
Tool to retrieve a list of public workspaces. use when browsing publicly available workspaces before selection.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Botpress. 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 Botpress.