Bring chatbot questions into pull request follow-up
A pull request's opening, updates, or closure can be a useful moment to review questions users have already asked your chatbot.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Get All Conversations
Tool to retrieve all conversations related to the bot. use after authentication when you need a paginated list of conversation threads for review or analytics.
Why this helps
Code changes can move quickly while customer questions remain buried in a separate conversation list.
- Make customer question review part of pull request follow-up.
- Keep user context close to development activity.
- Use a read-only action to gather conversation signals.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Botsonic once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what result you want in plain language.
- 3In one instruction, ask Notis to retrieve Botsonic conversations and summarize any questions that could relate to the pull request event.
- 4Pick the Pull Request Event trigger and choose where run reports should go.
- 5Test with one real pull request event and review the resulting summary.
Questions about this workflow
Which pull request changes can start this?
The event covers a pull request being opened, closed, or synchronized.
Can it tell whether a conversation is definitely about the pull request?
The action retrieves bot conversations. Notis can compare their content with the pull request context, but an exact relationship may not be available in the source data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Botsonic. A trigger fires from one place; an action lands in another.
GitHub triggers
Botsonic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Upload Bot URLs
Tool to bulk upload urls for bot training. use when you need to upsert multiple document urls into a bot in one request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Bot Data
Tool to delete specific bot data using its id. use when you need to remove outdated or irrelevant data after confirming the data identifier.
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 Starter Question
Tool to delete a specific starter question by its unique identifier. use after confirming the id of the starter question you want to remove.
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.
Delete Uploaded File
Tool to delete a specific uploaded file by its id. use when you need to remove a file from the bot's data repository after confirming the file id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get All Bot Data
Tool to retrieve all data associated with the bot, including files and resources. use when you need a comprehensive export of bot assets for backup or inspection.
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.
Get All Bots
Tool to retrieve all bots associated with the account. use when you need to list existing bots after authentication.
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.
Get All Conversations
Tool to retrieve all conversations related to the bot. use after authentication when you need a paginated list of conversation threads for review or analytics.
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.
Get All FAQs
Tool to retrieve all frequently asked questions associated with the bot. use after authenticating the bot and when you need to list or manage its faq entries.
Connect any two apps with Notis in the middle.
GitHub and Botsonic, 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 Botsonic.