Keep security review issues labeled from recurring reports
On your chosen schedule, Notis can ask Aryn to review a security report and label the referenced GitHub issues by finding type.
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
Recurring security reports can introduce follow-ups that are easy to miss when issue labels are updated manually.
- Keep issue triage aligned with recurring review findings.
- Reduce repeated reading and labeling effort.
- Use issue references and finding types that appear in the report.
Setup
Build it in a few focused steps.
- 1Connect Aryn and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to use Aryn to review the designated security report and add suitable labels to explicitly referenced GitHub issues.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real security report that names the repository and issue references.
Questions about this workflow
Will it create labels for new finding types?
The GitHub action can create labels that do not already exist. The instruction should use clear, consistent label names.
Can it label an issue that the report does not reference?
The workflow should only update issues explicitly referenced in the report. It needs enough repository and issue details to identify each target.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Aryn to GitHub. A trigger fires from one place; an action lands in another.
Aryn 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.
Aryn 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.