Connect deployment status to certificate events
A deployment status change is a natural moment to inspect the certificate event behind an operational concern.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
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.
Why this helps
Release investigations become scattered when deployment state and certificate-event details live in separate workflows.
- Shortens release investigation time
- Connects deployment context with certificate detail
- Reduces manual cross-tool searching
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 by asking naturally.
- 3Use this instruction: When the watched GitHub deployment receives a new status, retrieve the detailed CertSpotter event when its event id is available and report both contexts together.
- 4Choose the new deployment status trigger, select the report channel, and test with one real deployment status.
Questions about this workflow
Which statuses are useful?
Pending, in progress, success, failure, error, inactive, and queued statuses can all provide useful investigation checkpoints.
What happens without an event id?
Notis can report the deployment status while noting that no detailed CertSpotter event was available.
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.