Make a security handoff actionable in GitHub
A security conversation can trigger a direct check of the repository's private vulnerability reporting status, with the result sent back through Notis.
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 details shared in chat do not answer whether a repository has private vulnerability reporting enabled.
- Check the relevant repository setting at handoff time
- Keep security follow-up connected to its source discussion
- Report the status without manual navigation
Setup
Build it in a few focused steps.
- 1Connect Botbaba and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to check private vulnerability reporting for the repository identified in the submitted security handoff and summarize the result.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real security handoff and repository.
Questions about this workflow
Does this turn on private reporting?
No. It checks the status for the specified repository.
What repository is checked?
The repository identified in the security handoff or in the automation instruction.
Where can I receive the result?
Choose a report channel as part of automation setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botbaba to GitHub. A trigger fires from one place; an action lands in another.
Botbaba 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.
Botbaba 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.