Create context for secret-scanning alerts
Make a high-stakes alert immediately understandable.
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
Get Pre-recorded Transcription Result
Tool to retrieve metadata for a pre-recorded transcription job. Use when checking the status or retrieving results of a specific job ID.
Why this helps
A possible exposed secret demands attention, but the response path can become fragmented and delayed.
- Create a clear first response checkpoint.
- Keep alert details and urgency together.
- Reduce delay caused by searching across security screens.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Gladia to Notis once.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Use this instruction: When GitHub detects a new secret-scanning alert, retrieve the matching Gladia transcription result and report the secret type, validity status, exposure context, and immediate response steps.
- 4Choose New Secret Scanning Alert Detected, select the reporting channel, and test with one alert.
Questions about this workflow
Can active secrets be prioritized?
Yes. Ask Notis to prioritize alerts based on the validity status included by GitHub.
Should I include credentials in the prompt?
No. The workflow should use event context without placing secrets in automation instructions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Gladia. A trigger fires from one place; an action lands in another.
GitHub triggers
Gladia actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get live transcription result
Tool to retrieve metadata and results of a live transcription job. Use when you need detailed status or results for a specific live transcription session.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Pre-recorded Transcription Result
Tool to retrieve metadata for a pre-recorded transcription job. Use when checking the status or retrieving results of a specific job ID.
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.
Initiate Live Transcription Session
Tool to initiate a live transcription session. Use before streaming audio to get a WebSocket URL.
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.
Initiate Pre-Recorded Transcription
Tool to initiate a pre-recorded transcription job. Use when you have an audio URL and need asynchronous transcription results.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List live transcription jobs
Tool to list live transcription jobs. Use when you need an overview of live transcription sessions with optional filtering and pagination. Use after setting up live transcription.
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.
Gladia List Pre-Recorded Transcriptions
Tool to list pre-recorded transcription jobs with optional filters. Use after submitting or querying jobs to retrieve paginated results.
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.
Upload Audio/Video File
Tool to upload an audio or video file to Gladia's servers. Use when preparing a file for transcription.
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.
Connect any two apps with Notis in the middle.
GitHub and Gladia, 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 Gladia.