Catch GitHub security gaps before technical follow-up
A recurring check keeps security readiness from depending on a founder's memory.
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 often reviewed only when a prospect asks, creating avoidable last-minute work.
- Creates an early warning for security gaps
- Supports more confident technical conversations
- Turns an occasional audit into a routine
Setup
Build it in a few focused steps.
- 1Connect Lemlist and GitHub to Notis once through the portal.
- 2Create a recurring automation in the portal or ask Notis in plain language.
- 3Tell Notis: For repositories associated with active Lemlist technical prospects, check private vulnerability reporting and report any repository where it is disabled.
- 4Choose notis_cron, set a cadence, and select the reporting channel.
- 5Test with one repository tied to a real prospect.
Questions about this workflow
Does this enable the setting?
No. It checks the status and reports repositories that need review.
Why connect this to Lemlist?
It focuses the audit on repositories relevant to active technical conversations.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Lemlist to GitHub. A trigger fires from one place; an action lands in another.
Lemlist 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 Lemlist and GitHub. Any 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.