Keep Operational Capacity Visible During Security Work
When security work interrupts the day, let Notis handle one background check for you.
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 Usage
Tool to get usage information and remaining credits for your piloterr account. use when you need to check account usage and credit details.
Why this helps
Security incidents consume attention, so routine capacity checks are easy to forget until they become another problem.
- Reduce cognitive load during security response.
- Keep Piloterr capacity visible without another dashboard.
- Prevent unrelated research failures after an incident.
- Create a small but useful operational safety net.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Piloterr to Notis once.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a new secret scanning alert is detected, check Piloterr usage and report remaining credits so I can see whether any research workflows need attention.
- 4Select the secret scanning alert trigger and choose the run-report channel.
- 5Test with a safe test alert if available.
Questions about this workflow
Does this expose the detected secret?
The instruction should request usage information only and should not include secret values.
Can it focus on active secrets?
Use the secret validity filters available on the GitHub trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Piloterr. A trigger fires from one place; an action lands in another.
GitHub triggers
Piloterr actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Auchan Product
Tool to retrieve detailed auchan product information. use when you have a product id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Auchan Product Search
Tool to search for products on auchan by query or search url. use when you need product listings and details from auchan.
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.
Piloterr Get Product Info
Tool to retrieve detailed product information by product id. use when you need full product details including company info.
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.
Bestbuy Product Search
Tool to search for products on bestbuy by query. use when you need to retrieve bestbuy items by keywords with optional pagination and price filters.
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 Usage
Tool to get usage information and remaining credits for your piloterr account. use when you need to check account usage and credit 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.
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 Piloterr, 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 Piloterr.