Turn API alerts into clearly labeled GitHub issues
Send an API alert to Notis and have the matching GitHub issue labeled for quick 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
Alerts can arrive in one place while the issue that needs attention stays buried in GitHub.
- Make incoming API alerts visible in issue triage.
- Reduce manual copying between alert context and GitHub.
- Create labels when the requested label does not already exist.
Setup
Build it in a few focused steps.
- 1Connect Apiverve and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to identify the relevant GitHub issue from each incoming alert and add appropriate labels, using only information in the request.
- 4Choose the webhook trigger and select where Notis should send run reports.
- 5Test with one real alert and review the resulting GitHub issue.
Questions about this workflow
Does Apiverve provide the trigger for this automation?
Apiverve has no listed trigger events here. A Notis webhook starts the automation when an HTTP request arrives.
Can this create a label that is missing?
The GitHub action creates labels that do not already exist when adding them to an issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiverve to GitHub. A trigger fires from one place; an action lands in another.
Apiverve 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.
Apiverve 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.