Make recurring browser reviews easier to triage
Schedule a focused web review and keep related GitHub issues organized as new findings emerge.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Recurring checks are easy to postpone, and their results are hard to connect to existing work.
- Give recurring review a consistent cadence.
- Keep related issues easier to scan.
- Reduce the handoff from web review to GitHub.
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and GitHub to Notis once.
- 2Create an automation with the pages to review and the criteria for matching GitHub issues.
- 3Pick a recurring Notis schedule as the trigger.
- 4Choose where run reports should go.
- 5Test with one review and inspect the issues and labels.
Questions about this workflow
Can Browserbase tell Notis when a page changes?
No Browserbase trigger events are listed here. This workflow starts on a Notis schedule and asks Browserbase to review pages.
What pages should the automation review?
Name the public or accessible pages and the changes or findings that matter in your automation instruction.
Will labels be created automatically?
The GitHub action creates labels that do not already exist. Specify suitable labels in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase MCP to GitHub. A trigger fires from one place; an action lands in another.
Browserbase MCP 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.
Browserbase MCP 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.