Stay oriented when deployments change
Important deployment changes create a fresh visual checkpoint instead of another detail to remember.
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
Screenshot API
Tool to capture a screenshot of a webpage. use when you need a visual snapshot of a page; supports full-page, device emulation, delays, and dark mode.
Why this helps
Deployment details can shift while you are handling other work, leaving you to reconstruct what changed before taking action.
- Make deployment changes easier to notice
- Preserve context around environment shifts
- Reduce mental bookkeeping during releases
Setup
Build it in a few focused steps.
- 1Connect GitHub and Serpdog to Notis once via the portal.
- 2Create the automation in Automations or ask Notis to create it.
- 3Tell Notis to capture the relevant deployment or environment page whenever monitored deployment details change.
- 4Choose the GitHub deployment state changed trigger and select a reporting channel.
- 5Change one non-sensitive deployment detail in a test environment and verify the capture.
Questions about this workflow
Which changes should matter?
Mention environment, ref, description, or another relevant deployment detail in the instruction.
Can this support temporary environments?
Yes. Include preview or temporary environments in the instruction when needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Serpdog. A trigger fires from one place; an action lands in another.
GitHub triggers
Serpdog actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Screenshot API
Tool to capture a screenshot of a webpage. use when you need a visual snapshot of a page; supports full-page, device emulation, delays, and dark mode.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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 Serpdog, 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 Serpdog.