Check private vulnerability reporting for integration code
When an integration review comes in, have Notis check whether its linked GitHub repository has private vulnerability reporting enabled.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check private vulnerability reporting status
Checks if private vulnerability reporting is enabled for the specified repository.
Why this helps
Security readiness checks are easy to overlook when reviewing affiliate integration work across separate systems.
- Make a repository security setting part of integration review.
- Get a clear status in your chosen run report channel.
- Avoid repeating a manual settings check.
Setup
Build it in a few focused steps.
- 1Connect Adtraction and GitHub once in the Notis portal.
- 2Create an automation in the portal or from any channel.
- 3Tell Notis to check private vulnerability reporting for the GitHub repository associated with the incoming integration review.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real review that identifies a GitHub repository.
Questions about this workflow
Does this enable private vulnerability reporting if it is off?
No. The available action checks the setting's status. Use the run report to follow up if it is not enabled.
What if the review does not identify a repository?
Include the repository owner and name with the webhook information, or specify how Notis can identify the repository in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adtraction to GitHub. A trigger fires from one place; an action lands in another.
Adtraction 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.
Adtraction 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.