Turn GitHub secret alerts into a clear Gist incident log
Notis updates the designated comment in your incident Gist with the alert, exposure context, and next owner, giving the team one calm place to respond.
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
Update Gist Comment
Tool to update a Gist comment. Use when you need to modify an existing comment after confirming the gist_id and comment_id.
Why this helps
A high-priority credential alert can disappear among notifications before someone records who is handling it.
- Creates an immediate shared record
- Reduces security-alert context switching
- Makes ownership and next steps easier to see
Setup
Build it in a few focused steps.
- 1Connect GitHub and Gist to Notis once in the portal.
- 2Create a new automation and name it Secret Alert Incident Log.
- 3Write one instruction asking Notis to update the chosen incident Gist comment with each alert, its urgency, and the next response step.
- 4Select New Secret Scanning Alert Detected as the trigger, choose a run-report channel, and test with one authorized alert.
Questions about this workflow
Does this create a new Gist for every alert?
No. It updates the existing Gist comment you identify in the plain-language instruction.
Can Notis highlight active tokens?
Yes. Ask it to prioritize active or publicly exposed secrets using the details GitHub provides.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Gist. A trigger fires from one place; an action lands in another.
GitHub triggers
Gist 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.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
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 Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
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 Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
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 Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
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.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
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 Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
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 Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
Commit Event
Triggered when a new commit is pushed to a repository.
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Not just GitHub and Gist. 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 Gist.