Keep alert response operationally ready
When attention shifts to a security alert, know whether your accessibility tooling is ready for the next step.
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 Account
Tool to retrieve account settings and usage information. use when you need to check your alttext.ai account configuration and usage limits before generating alt text.
Why this helps
A security incident can interrupt normal workflows and leave teams unsure which connected tools are available.
- Makes tool readiness visible during incidents
- Reduces extra checking across dashboards
- Supports deliberate follow-up planning
- Keeps operational context in one report
Setup
Build it in a few focused steps.
- 1Connect GitHub and Alttext ai to Notis once through the portal.
- 2Create the automation in Automations -> New Automation or ask Notis to create it.
- 3Use this instruction: When a new GitHub secret scanning alert is detected, retrieve Alttext ai account settings and usage information, then report whether the account is ready for planned image review.
- 4Select New Secret Scanning Alert Detected as the trigger and choose a secure report channel.
- 5Test in a non-production repository.
Questions about this workflow
Does this expose the detected secret?
The instruction should request account readiness only, not secret values or credentials.
Why check usage here?
It prevents a later accessibility follow-up from being delayed by an unexpected account limit.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Alttext ai. A trigger fires from one place; an action lands in another.
GitHub triggers
Alttext ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account
Tool to retrieve account settings and usage information. use when you need to check your alttext.ai account configuration and usage limits before generating alt text.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to retrieve account settings and usage information. use when you need to check your alttext.ai account configuration and usage limits before generating alt text.
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 Images
Tool to retrieve a paginated list of images in your library, including their alt text and metadata. use when you need to browse or filter images programmatically after authentication.
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.
Search Images
Tool to search for images and their alt text. use after specifying search keywords to retrieve matching images.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Update Account
Tool to update account settings (e.g., webhook url, name). use after confirming current account details to modify settings.
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 Alttext ai, 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 Alttext ai.