Create feedback forms for important repository changes
Collect focused feedback when the product changes materially.
Trigger
Repository Content Changed
Triggers when the content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires ``content_changed`` when the file is modified. For a directory, fires ``content_changed``, ``content_added``, or ``content_removed`` for modified, new, or deleted entries respectively. content.
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
Small code changes can have large user consequences, but there is no automatic cue to validate them.
- Links important product changes to validation.
- Keeps feedback requests focused on the change.
- Reduces the chance of shipping assumptions unchecked.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cabinpanda once in the Notis portal.
- 2Create the automation in the portal or ask Notis to build it conversationally.
- 3Use this instruction: When the monitored GitHub file or directory changes, create a Cabinpanda feedback form that validates the user-facing impact of the change.
- 4Choose the repository-content trigger, select a report channel, and test with one real change.
Questions about this workflow
Can I monitor a specific directory?
Yes. Configure the monitored path for the relevant product area.
Can this ignore internal-only changes?
Yes. Describe the user-facing change condition in the instruction.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Form
Tool to create a new form with specified fields and settings. use before collecting submissions to define form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a specific form by its id. use after confirming the target form exists and is safe to remove.
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 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.
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 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.
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 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.
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 Profile
Tool to retrieve the authenticated user's profile information. use after obtaining valid api credentials to access user details.
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 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.
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 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.
GitHub and Cabinpanda, 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 Cabinpanda.