Turn vendor security advisories into a clear GitHub review queue
Airtop checks the security pages you name, then GitHub marks the issue you chose when a relevant advisory appears.
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
Security updates can be easy to miss when they live outside the tools where engineering work is tracked.
- Notice relevant vendor advisories without repeatedly checking sites
- Give the specified issue a consistent review label
- Keep the review task close to the engineering work
Setup
Build it in a few focused steps.
- 1Connect Airtop and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3In one instruction, name the vendor pages and the GitHub repository, issue, and existing or new label to use when an advisory is relevant.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real advisory page and confirm the issue label is appropriate.
Questions about this workflow
Can it decide which issue to label from a repository search?
This workflow labels the issue you specify in the instruction. Name the issue or provide clear criteria and details that Airtop can actually find on the pages it checks.
What if the page has no new advisory?
Tell Notis to take no GitHub action when the page contains no relevant advisory, and review the run report for the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtop to GitHub. A trigger fires from one place; an action lands in another.
Airtop 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.
Airtop 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.