Find LaunchDarkly team context after GitHub secret alerts
A sensitive alert should not require a memory search for the people who own the rollout response.
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
List Teams
Tool to list all teams in launchdarkly. use after confirming credentials; supports pagination internally.
Why this helps
During a secret alert, figuring out the right owners can consume the attention needed for containment.
- Surfaces team context quickly
- Reduces ownership guesswork
- Supports steadier incident coordination
Setup
Build it in a few focused steps.
- 1Connect GitHub and LaunchDarkly to Notis once in the portal.
- 2Create a new automation.
- 3Describe in plain language that a secret alert should retrieve LaunchDarkly team context.
- 4Select the new secret scanning alert trigger and a reporting channel.
- 5Test with one real alert scenario.
Questions about this workflow
Does this change team permissions?
No. This workflow retrieves team information for coordination context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Launch darkly. A trigger fires from one place; an action lands in another.
GitHub triggers
Launch darkly 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 Flag Trigger Workflow
Tool to create a flag trigger workflow. use when setting up an automated trigger to toggle a flag in a specific environment.
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 Trigger Workflow
Tool to delete a specific flag trigger workflow. use after confirming the project key, feature flag key, environment key, and trigger workflow id.
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 Custom Roles
Tool to retrieve a list of all custom roles. use when you need to list roles for permissions audits or configuration reviews. note: results are paginated.
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 Environments
Tool to retrieve a list of all environments within a project. use after confirming the project key; supports pagination.
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 Code Reference Repositories
Tool to list code reference repositories. use when retrieving repositories for a specific project; includes pagination.
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 Projects
Tool to retrieve a list of all projects. use after confirming credentials to enumerate project keys and metadata.
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 launchdarkly. use after confirming credentials; supports pagination internally.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Launch darkly. 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 Launch darkly.