Review lead feeds after a secret scanning alert
Add a short business-context check to your incident response rhythm.
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 Custom Feeds
Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.
Why this helps
An urgent alert can scatter attention across tools and leave follow-up incomplete.
- Creates a consistent incident companion
- Keeps review work bounded
Setup
Build it in a few focused steps.
- 1Connect GitHub and Leadfeeder to Notis.
- 2Create a new automation from the portal.
- 3Write one instruction to retrieve Leadfeeder feeds after a new secret alert.
- 4Choose the secret-scanning alert trigger and a channel.
- 5Use a safe test event to confirm reporting.
Questions about this workflow
Will Notis expose the secret?
The workflow is for Leadfeeder feed retrieval; handle sensitive alert details using your security process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Leadfeeder. A trigger fires from one place; an action lands in another.
GitHub triggers
Leadfeeder actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Accounts
Tool to retrieve a list of accounts the user has access to. use when you need to discover all available leadfeeder accounts after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
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.
Get Company Info by IP
Tool to retrieve company information based on an ip address. use when you need to enrich an ip and obtain its company profile. returns 404 if no match is found.
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.
Get Custom Feeds
Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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 Leadfeeder, 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 Leadfeeder.