Track vulnerability reporting settings for portfolio repositories
Use a recurring Notis check to review the private vulnerability reporting status of repositories named in Affinity.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
Security setting reviews are easy to postpone when portfolio repository details and GitHub checks live in different places.
- Review a specific GitHub security setting across referenced repositories.
- Receive one scheduled summary instead of checking repositories one by one.
- Identify missing or invalid repository references for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Affinity and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to check private vulnerability reporting only for GitHub repositories explicitly identified in Affinity records and summarize each result.
- 4Pick the notis_cron trigger and choose its schedule and where run reports should go.
- 5Test with one real Affinity record that names a GitHub repository.
Questions about this workflow
Does this enable private vulnerability reporting?
No. This workflow checks the setting's status and reports it. It does not change the repository setting.
What if an Affinity record has no repository reference?
The automation should report that the repository is missing and skip the check until the record includes a valid repository reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinity to GitHub. A trigger fires from one place; an action lands in another.
Affinity 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.
Affinity 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.