Give recurring web review findings an owner
Keep scheduled checks from ending as unclaimed notes by routing matching GitHub issues to an owner.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Regular monitoring creates follow-up, but ownership can be unclear once the review is over.
- Connect monitoring to issue ownership.
- Apply team routing rules consistently.
- Keep follow-up tied to recurring reviews.
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and GitHub to Notis once.
- 2Create an automation describing the pages, issue matching criteria, and ownership rules.
- 3Choose a recurring schedule trigger in Notis.
- 4Select where run reports should be delivered.
- 5Test with one review and confirm the expected issue assignment.
Questions about this workflow
Does this make an issue when a new finding appears?
No. The available GitHub action assigns users to existing issues. Include issue creation as a manual follow-up if needed.
Can I use a different owner for different findings?
Yes. Describe the decision rules in the automation prompt, and ensure the finding has enough information to apply them.
What if the run cannot match a finding to an issue?
Tell Notis to report unmatched findings for review rather than assigning an unrelated issue.
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.