Collect release readiness feedback with Basin
Give your team a consistent intake point for release readiness input tied to pull request activity.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Create Form
Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Why this helps
Release readiness questions often live in disconnected conversations with no clear intake point.
- Create a repeatable place to gather readiness feedback.
- Connect the form creation moment to GitHub pull request activity.
- Make release preparation easier to coordinate.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Basin once in the Notis portal.
- 2Create an automation that creates a Basin form for release readiness input when a pull request is opened, closed, or synchronized.
- 3Pick the Pull Request Event trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real pull request event.
Questions about this workflow
Does this trigger on every pull request update?
It starts on the pull request event types supported by the selected trigger: opened, closed, or synchronized.
Does GitHub provide release readiness answers?
No. The form collects answers from respondents; the GitHub event only starts the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Basin. A trigger fires from one place; an action lands in another.
GitHub triggers
Basin 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 in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
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 Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
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.
Create Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
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 Form
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
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.
Delete Integration
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
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.
Delete Project
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
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.
Delete Webhook
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
Connect any two apps with Notis in the middle.
GitHub and Basin, 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 Basin.