Keep Bubble-linked pull requests from slipping out of view
See which tracked pull requests have merged when your team reviews Bubble work on a schedule.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
Open pull requests linked to app work can disappear from attention when no one remembers to revisit them.
- Bring open and merged work back into view on a regular cadence.
- Reduce manual checking across Bubble records and GitHub.
- Make follow-up easier with a focused status report.
Setup
Build it in a few focused steps.
- 1Connect Bubble and GitHub once in the Notis portal.
- 2Create an automation and describe how to find pull request references in Bubble and summarize their merge status.
- 3Choose a Notis cron trigger and set a useful review schedule.
- 4Choose where run reports should go.
- 5Test with one real Bubble record linked to a GitHub pull request.
Questions about this workflow
Will this merge any pull requests?
No. It only checks whether a specified GitHub pull request has merged.
What if a Bubble record does not include a pull request reference?
The workflow needs that reference to check status. Ask Notis to report missing references for follow-up.
Can I use it for a release review?
Yes. A recurring report can surface the merge state of the pull requests your Bubble data associates with planned work.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bubble to GitHub. A trigger fires from one place; an action lands in another.
Bubble triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Bubble and GitHub, 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 GitHub.