Turn secret alerts into an immediate Addresszen key check
When GitHub flags a possible secret, get a fast signal on whether Addresszen is still available for your delivery workflows.
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
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
Why this helps
A security alert can derail your day while you manually figure out whether connected address operations are still safe to run.
- Reduce urgent context switching after a secret alert.
- Know whether Addresszen remains usable before troubleshooting downstream workflows.
- Create a consistent first response for security incidents.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Addresszen to Notis once through the portal.
- 2Create an automation in Automations or ask Notis in plain language to check Addresszen key availability whenever GitHub detects a new secret scanning alert.
- 3Select the GitHub secret scanning alert trigger and choose a channel for run reports.
- 4Test with one real or safe GitHub secret scanning alert example.
Questions about this workflow
Does this resolve an address?
No. It checks whether the Addresszen key is currently usable.
Can I use it for active secrets only?
Yes. State in the plain-language instruction that the workflow should focus on active or unknown secret validity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Addresszen. A trigger fires from one place; an action lands in another.
GitHub triggers
Addresszen 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.
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
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.
Resolve Address USA
Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.
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.
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.
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 Addresszen. Any 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 Addresszen.