Refresh launch context after a pull request changes
Keep the project picture aligned when a PR is renamed, relabeled, redirected, merged, or reopened.
Trigger
Pull Request Updated
Triggers when an existing pull request is updated in a GitHub repository. Updates include title edits, description changes, label changes, assignee changes, reviewer requests, draft status changes, base branch changes, being closed, merged, or reopened. Only pre-existing PRs that receive an update will fire the trigger; newly created PRs are excluded. Supports optional filters: state, base branch, head branch, author, label, and draft status.
Action
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.
Why this helps
A pull request can change meaning during review, while the project context people remember is based on an older title, scope, or target branch.
- Refreshes project context after meaningful PR changes
- Reduces decisions based on stale delivery assumptions
Setup
Build it in a few focused steps.
- 1Connect GitHub and Project bubble to Notis once.
- 2Tell Notis in plain language to retrieve current launch and dependency objects after an existing pull request changes.
- 3Choose Pull Request Updated as the trigger, select where run reports should arrive, and test with one PR update.
Questions about this workflow
Will newly opened pull requests trigger this workflow?
No. This GitHub event is for updates to existing pull requests; use the New Pull Request Created trigger for first-time context.
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.