Turn browser test failures into labeled GitHub issues
Send a Browserbase failure report to Notis and label the related GitHub issue for your next focused triage pass.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Browser failures get lost when test results and GitHub issues live in separate workflows.
- Make reported browser failures easier to find in GitHub.
- Reduce manual copying between browser reports and issue triage.
- Use labels that already fit your repository, or create new ones when needed.
Setup
Build it in a few focused steps.
- 1Connect Browserbase and GitHub once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to review each Browserbase failure report and add relevant labels to its matching GitHub issue.
- 4Choose the Notis webhook as the trigger and have the Browserbase report start it with an HTTP request.
- 5Choose a run report destination, then test with one real failure report and issue.
Questions about this workflow
Does this create a GitHub issue?
No. The available GitHub action adds labels to an existing issue. Include the matching issue details in the Browserbase report or your instruction.
Can GitHub create a label if it does not exist?
Yes. This action creates labels that do not already exist in the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase tool to GitHub. A trigger fires from one place; an action lands in another.
Browserbase tool 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 tool 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.