Triage shift incidents in GitHub
Send an incident report to Notis and keep its GitHub issue easier to scan and route.
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
Operational incidents can get buried in GitHub when reports arrive without consistent labels.
- Apply relevant labels to the issue named in the report.
- Make incident follow-up easier to spot during a busy shift.
- Avoid manually reopening GitHub just to categorize a report.
Setup
Build it in a few focused steps.
- 1Connect 7shifts and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and give it a clear name.
- 3Tell Notis to read the incoming incident report and add suitable existing or new labels to the GitHub issue it identifies.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real example report to test the workflow.
Questions about this workflow
Does 7shifts trigger this automatically?
No. 7shifts has no trigger events in this setup. An HTTP request sent to the Notis webhook starts the automation.
What information should the report include?
Include the GitHub repository and issue to update, plus enough incident context for Notis to select useful labels.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 7shifts to GitHub. A trigger fires from one place; an action lands in another.
7shifts 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.
7shifts 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.