Give browser discoveries a clear GitHub owner
Move from finding to follow-up by assigning the relevant issue while the context is fresh.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A research finding without an owner can become another task nobody picks up.
- Turn findings into owned follow-up.
- Reduce the gap between research and action.
- Apply ownership rules through a plain language instruction.
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and GitHub to Notis once.
- 2Create an automation and explain how to match a finding to an issue and choose an assignee.
- 3Select a Notis webhook trigger.
- 4Choose where run reports should go.
- 5Test with one real finding and verify the assignment.
Questions about this workflow
Does this create an issue from a browser finding?
No. This workflow assigns an existing GitHub issue. Use an existing issue identifier or enough context to find it.
Can it remove an assignee?
The action supports adding or removing assignees. Describe the intended ownership change clearly.
What if the user cannot be assigned?
GitHub may silently ignore changes if the authenticated user lacks push access. Check repository permissions if no change appears.
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.