Keep incident-linked GitHub issues labeled during a scheduled review
A recurring Notis review can surface incident-linked issues that need labels, helping prevent follow-up from disappearing after the first alert.
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
Issues tied to ongoing incidents can stay unlabeled when the initial alert arrives during a busy stretch.
- Catch unlabeled incident issues during a routine review.
- Apply consistent triage labels using your instructions.
- Keep a report of changes and items that need attention.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and GitHub once in Notis.
- 2Create an automation in the portal or tell Notis to create one from any channel.
- 3In one instruction, define which incident information to review, the label rules, and how to handle issues without a confirmed repository and issue reference.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real incident and its linked GitHub issue.
Questions about this workflow
Does the schedule create a Bugsnag event?
No. A Notis cron trigger starts the automation on a recurring schedule; Bugsnag exposes no trigger events in this package.
Can Notis review an incident history or baseline that Bugsnag does not return?
Only if that information is available through the connected source or supplied in your instruction. Specify any required history or baseline rather than assuming it exists.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to GitHub. A trigger fires from one place; an action lands in another.
Bugsnag 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.
Bugsnag 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.