Route Bug Recorder errors into GitHub issue triage
Send an error report to Notis and have the related GitHub issue labeled for the next step.
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
Error reports can sit beside GitHub issues without a clear signal about what needs attention.
- Make incoming error reports easier to scan alongside related issues.
- Apply labels only when the report provides enough context to identify the repository and issue.
- Reduce repeated manual triage.
Setup
Build it in a few focused steps.
- 1Connect Bug Recorder and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe how to use report details to label the related GitHub issue in one instruction.
- 4Choose the Notis webhook trigger and select a channel for run reports.
- 5Test with one real report that identifies a GitHub repository and issue.
Questions about this workflow
Does Bug Recorder provide a built-in trigger event?
No trigger events are listed for Bug Recorder. Start this automation with a Notis webhook and send it a report when one is ready.
Will this create a GitHub issue?
No. The selected action adds labels to an existing issue. The report must identify the repository and issue, and the label should already exist or be appropriate to create.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bug Recorder to GitHub. A trigger fires from one place; an action lands in another.
Bug Recorder 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.
Bug Recorder 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.