Keep domain scope aligned with deployment changes
A changed environment or ref can alter what is being shipped, making a fresh domain-coverage check worthwhile.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
List Monitored Domains
Tool to list all monitored domains. use when you need to audit or review the domains currently monitored by cert spotter.
Why this helps
Deployment edits can quietly change scope after the original release plan was reviewed.
- Catches scope drift earlier
- Keeps environment changes visible
- Reduces rechecking effort during releases
Setup
Build it in a few focused steps.
- 1Connect GitHub and Sslmate cert spotter api to Notis once.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When the watched GitHub deployment environment, ref, task, or production flag changes, list CertSpotter monitored domains and report the updated domain-scope review.
- 4Select the deployment state changed trigger, choose a run-report channel, and test with one real deployment change.
Questions about this workflow
Which deployment fields can matter?
Environment, ref, task, description, SHA, transient environment, and production environment can all be useful context.
Does this change deployment settings?
No. It only retrieves monitored domains and reports the review context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Sslmate cert spotter api. A trigger fires from one place; an action lands in another.
GitHub triggers
Sslmate cert spotter api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CertSpotter Event
Tool to retrieve detailed information about a specific certspotter event. use when you need to inspect event metadata after confirming an event id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Monitored Domains
Tool to list all monitored domains. use when you need to audit or review the domains currently monitored by cert spotter.
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.
Retrieve Webhook Settings
Tool to retrieve webhook settings. use when you need to view the currently configured cert spotter webhook.
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.
Not just GitHub and Sslmate cert spotter api. 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 Sslmate cert spotter api.