Give recurring error review a GitHub outcome
Use a recurring Notis run to review available error reports and label related issues when the evidence is there.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Periodic error review often gets postponed, leaving related issues without a consistent triage signal.
- Create a recurring checkpoint for available error reports.
- Apply labels only when a report clearly identifies an existing issue.
- Keep report runs visible in a chosen channel.
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 name it for scheduled triage.
- 3Describe how to review error reports available to Notis and label only clearly matched GitHub issues.
- 4Choose a Notis cron schedule and select a channel for run reports.
- 5Test with one real report and confirm the schedule fits your review cadence.
Questions about this workflow
Does the schedule itself fetch Bug Recorder data?
A schedule starts the automation. The data available to Notis depends on the connected app and the prompt context; do not assume reports are available unless the integration supplies them.
Can it label an issue when the report has no issue reference?
Only if your instruction provides a reliable way to identify the matching issue. Otherwise, it should leave the issue unchanged.
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.