Check security readiness before your event
A small pre-event check can prevent awkward security gaps later.
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 readiness is easy to overlook when event preparation already fills the calendar.
- Add a lightweight security checkpoint
- Reduce last-minute uncertainty
- Keep responsible disclosure readiness visible
Setup
Build it in a few focused steps.
- 1Connect Eventbrite and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Instruct Notis to check private vulnerability reporting for the repository linked to the upcoming technical event and report the result.
- 4Choose a recurring schedule, select the reporting channel, and test before one real event.
Questions about this workflow
Does this enable vulnerability reporting?
No. The available GitHub action checks its status and reports the result.
When should it run?
Choose a schedule that gives you enough time to address a gap before the event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Eventbrite to GitHub. A trigger fires from one place; an action lands in another.
Eventbrite triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Eventbrite and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.