Route BrowserAct findings into GitHub issue labels
Send a BrowserAct report to Notis and have the related GitHub issues labeled for easier triage.
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 research can surface actionable issues, but translating findings into GitHub labels creates another manual pass.
- Convert report findings into a clear issue triage signal.
- Reduce manual issue updates after browser research.
- Keep labels tied to evidence in the submitted report.
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and GitHub once in Notis.
- 2Create an automation in Notis from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to identify GitHub issues in each submitted BrowserAct report and add only labels justified by the findings.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real report to the webhook and review the GitHub labels and run report.
Questions about this workflow
Does this start automatically when a BrowserAct task finishes?
The trigger is a Notis webhook. Use it when a report is submitted to that webhook; an automatic BrowserAct completion trigger is not listed here.
Can it create labels that do not exist?
The GitHub action supports adding labels and creates labels that do not already exist.
What should the report include?
Include enough detail to identify the repository and issue, plus the BrowserAct finding that supports each label.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BrowserAct to GitHub. A trigger fires from one place; an action lands in another.
BrowserAct 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.
BrowserAct 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.