Respond to GitHub Secret Alerts Without Delay
A possible credential leak should trigger a response routine, not a memory test.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
Action
Create Meeting Event
Tool to create a new meeting event in Leexi with timing, participants, and recording preferences. Use when scheduling a meeting that needs to be tracked and potentially recorded in the Leexi system.
Why this helps
Secret exposure requires fast coordination, but the right people and steps are easy to lose under pressure.
- Creates an immediate containment checkpoint.
- Puts secret type, validity, and repository context in one place.
- Helps founders coordinate rotation and follow-up consistently.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Leexi to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When GitHub detects a new secret scanning alert, create a Leexi meeting event for containment and include the secret type, validity status, repository, and alert link.
- 4Select the secret scanning trigger, choose the channel for run reports, and test with one example.
Questions about this workflow
Can this focus on active secrets only?
Yes. Ask Notis to act only when the alert reports an active or unknown validity status.
Is the secret value copied into Leexi?
The instruction should explicitly avoid copying secret values and include only safe alert metadata.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Leexi. A trigger fires from one place; an action lands in another.
GitHub triggers
Leexi actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Meeting Event
Tool to create a new meeting event in Leexi with timing, participants, and recording preferences. Use when scheduling a meeting that needs to be tracked and potentially recorded in the Leexi system.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete Meeting Event
Tool to delete a specific meeting event by UUID. Use when you need to permanently remove a meeting event record from the Leexi system. This is a destructive operation that cannot be undone.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Call
Tool to get details of a specific call or meeting by UUID from Leexi. Use when you need to retrieve call details including topics and transcripts. The simple_transcript provides paragraph-level timestamps, while the transcript includes word-level timestamps.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Meeting Event
Tool to retrieve a specific meeting event by UUID from Leexi. Use when you need to fetch details of a particular meeting event including timing, participants, and recording preferences.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
List Calls
Tool to list all calls and meetings in your Leexi workspace with pagination support. Use when you need to retrieve call records. Note: AI-generated content like summaries and chapters may not be immediately available for newly created calls.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
List Meeting Events
Tool to list all meeting events in your Leexi workspace with pagination support. Use when you need to retrieve meeting events from the workspace.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
List Teams
Tool to list all teams in your Leexi workspace with pagination support. Use when you need to retrieve team information or iterate through all teams in the organization.
Commit Event
Triggered when a new commit is pushed to a repository.
List Users
Tool to list all users in your Leexi workspace. Use when you need to retrieve information about workspace members. Supports pagination with configurable page size (1-100 items per page, default 10).
Connect any two apps with Notis in the middle.
Not just GitHub and Leexi. 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 Leexi.