Create a deployment feedback intake form
Make validation part of shipping, not an afterthought.
Trigger
New Deployment Created
Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.
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
Founders often deploy first and remember feedback collection only after the release has gone quiet.
- Creates a feedback channel alongside deployment.
- Makes validation questions consistent.
- Protects post-launch learning from being forgotten.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cabinpanda to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use this instruction: When a new GitHub deployment is created, create a Cabinpanda feedback form for validating that deployment with the relevant testers or users.
- 4Select the new-deployment trigger, choose where run reports should go, and test with one deployment.
Questions about this workflow
Can this apply only to staging?
Yes. Specify the target environment in the instruction.
Can the form include deployment details?
Yes. Ask Notis to include the deployment context in the form.
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.