Check repository vulnerability reporting when a web signal arrives
Use the incoming signal as a prompt to check a repository setting and send the status to your chosen report channel.
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
A relevant site signal can prompt a security follow-up, but the repository setting is often buried in another tool.
- Turn an HTTP request into a focused repository status check
- Include the signal context in the run report
- Check only repositories identified in the request or instruction
Setup
Build it in a few focused steps.
- 1Connect Browseai and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, then name it and describe the status check in one instruction.
- 3Tell Notis to identify the repository from the incoming context and check its private vulnerability reporting status.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one actual signal containing a repository and confirm the reported status.
Questions about this workflow
Is there a Browseai trigger event?
No. Browseai exposes no trigger events in this workflow package, so use a Notis webhook and send it the HTTP request.
Will the workflow turn reporting on if it is disabled?
No. The available action checks reporting status; it does not enable or change the setting.
What must the incoming request include?
It should identify the repository to check, or the automation must have another explicit way to obtain it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browseai to GitHub. A trigger fires from one place; an action lands in another.
Browseai 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.
Browseai 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.