Check market timing after a secret scanning alert
A secret alert needs focus. Notis gathers the nearby crypto dates while you handle the incident.
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 Cryptocurrency Events
Tool to retrieve list of cryptocurrency events. Use when you need to fetch upcoming or past crypto events filtered by date range, coins, categories, or other criteria. Note: Cannot retrieve events before 25/11/2017. The can_occur_before field is important as some events may happen before their stated date.
Why this helps
Incident response consumes attention, making it easy to miss market events that affect disclosure, rotation, or launch plans.
- Reduces research burden during incidents
- Surfaces dates that may affect communications
- Keeps incident follow-up connected to market context
Setup
Build it in a few focused steps.
- 1Connect GitHub and CoinMarketCal to Notis once through the portal.
- 2Create a new automation in Automations or ask Notis through your usual channel.
- 3Use this instruction: When a new GitHub secret scanning alert is detected, retrieve relevant CoinMarketCal events and summarize any timing considerations for incident response or communication.
- 4Select the new secret scanning alert trigger and choose a private reporting channel.
- 5Test with a controlled alert in a test repository.
Questions about this workflow
Is sensitive secret content sent to CoinMarketCal?
The workflow should request event information using project context without exposing secret values.
Can it support active-token alerts?
Yes. Configure the trigger and instruction to prioritize active or unknown validity statuses.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Coinmarketcal. A trigger fires from one place; an action lands in another.
GitHub triggers
Coinmarketcal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Coins
Tool to retrieve list of all available coins/cryptocurrencies in CoinMarketCal database. Use when you need to fetch coin information including IDs, names, symbols, and event counts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Event Categories
Tool to list all event categories. Use when you need to fetch available event categories.
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.
List Cryptocurrency Events
Tool to retrieve list of cryptocurrency events. Use when you need to fetch upcoming or past crypto events filtered by date range, coins, categories, or other criteria. Note: Cannot retrieve events before 25/11/2017. The can_occur_before field is important as some events may happen before their stated date.
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.
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 Coinmarketcal, 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 Coinmarketcal.