Bring up the release checklist after GitHub release changes
Put the current launch checklist next to every meaningful release edit, publication change, or asset update.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Get Record By ID
Tool to retrieve a specific record by id from the bubble data api. use after confirming the data type and record id. example: request type='teams', id='a1b2c3d4'.
Why this helps
Release changes often happen quickly, while the checklist that defines launch completeness remains in another tool and can be overlooked.
- Keeps launch requirements visible during release changes
- Removes a repeat checklist lookup
Setup
Build it in a few focused steps.
- 1Connect GitHub and Project bubble to Notis once.
- 2Create an automation that tells Notis where the Project bubble checklist ID appears in the release and to retrieve that record after changes.
- 3Choose GitHub Release State Changed as the trigger, select a channel for reports, and test with a non-critical release.
Questions about this workflow
Which release changes can start the lookup?
The trigger can detect changes to release notes, title, draft or prerelease state, target reference, publication time, and attached assets.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Project bubble. A trigger fires from one place; an action lands in another.
GitHub triggers
Project bubble actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Data API Get Data Type Fields
Tool to get the fields of a specific data type. use after discovering a data type to inspect its fields.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Data API Get Objects
Tool to retrieve a list of objects for a specified data type. use when you need to list items with optional filters, sorting, and pagination.
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.
Get Record By ID
Tool to retrieve a specific record by id from the bubble data api. use after confirming the data type and record id. example: request type='teams', id='a1b2c3d4'.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Project bubble, 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 Project bubble.