Start a QA form for every pull request
Make review steps visible before code gets merged.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
Create Form
Tool to create a new form with specified fields and settings. use before collecting submissions to define form structure.
Why this helps
Pull requests can be approved without a shared testing checklist or clear evidence of what was verified.
- Creates a repeatable QA starting point.
- Keeps test questions close to the code change.
- Reduces reliance on memory during reviews.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cabinpanda to Notis once through the portal.
- 2Create a new automation or ask Notis to build it conversationally.
- 3Use this instruction: When a new GitHub pull request opens, create a Cabinpanda QA form based on the change description and include the checks reviewers should complete.
- 4Select the pull-request-created trigger, choose where run reports should arrive, and test with one open pull request.
Questions about this workflow
Can this target only pull requests into main?
Yes. State the target branch in the instruction.
Can reviewers use the form together?
Yes. Share the resulting Cabinpanda form with the people involved.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cabinpanda. A trigger fires from one place; an action lands in another.
GitHub triggers
Cabinpanda 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.
Create Form
Tool to create a new form with specified fields and settings. use before collecting submissions to define form structure.
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 Form
Tool to delete a specific form by its id. use after confirming the target form exists and is safe to remove.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Integration
Tool to delete a specific integration by its id. use when you need to remove or disable an existing integration (e.g., webhook) after confirming the integration id.
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 Form Details
Tool to retrieve details of a specific form by its id. use when you need form metadata (fields, labels, timestamps) before processing or submitting data.
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 Integration Details
Tool to retrieve details of a specific integration by its id. use when you need to inspect integration settings or status after obtaining its id.
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 Profile
Tool to retrieve the authenticated user's profile information. use after obtaining valid api credentials to access user details.
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 Forms
Tool to retrieve a list of all forms associated with the account. use when you need to fetch form details for management or analysis.
Commit Event
Triggered when a new commit is pushed to a repository.
List Integrations
Tool to retrieve a list of all integrations for the account. use when you need to inspect available or active integrations before managing them.
Connect any two apps with Notis in the middle.
Not just GitHub and Cabinpanda. Any 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 Cabinpanda.