Pair security research with a repository readiness check
Let Autom gather useful security context on a schedule, then check GitHub's private vulnerability reporting status for the repository under review.
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 research and repository settings live in different places, making a simple readiness check easy to postpone.
- Bring security research and a repository check into one routine
- See reporting status alongside a concise research summary
- Keep a repeatable review moving without manual context switching
Setup
Build it in a few focused steps.
- 1Connect Autom and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the security review.
- 3In one instruction, describe the research topic and specify the repository whose private vulnerability reporting status should be checked.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real research topic and repository.
Questions about this workflow
What repository information is needed?
Specify the repository owner and name so GitHub can check its private vulnerability reporting status.
Does this turn reporting on or off?
No. The listed GitHub action checks whether the feature is enabled; it does not change the setting.
Can the research replace a security review?
No. Autom can provide web research and GitHub can report the setting status. The workflow does not conduct a full security audit.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Autom to GitHub. A trigger fires from one place; an action lands in another.
Autom 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.
Autom 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.