See what failed when CI breaks
A failed workflow becomes easier to investigate when the affected page is captured automatically.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
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
When CI fails, the diagnosis gets delayed by reconstructing which environment, route, or build state needs inspection.
- Preserve the page state near the failure
- Shorten the path from alert to investigation
- Reduce the need to reconstruct failed contexts
Setup
Build it in a few focused steps.
- 1Connect GitHub and Serpdog once in the Notis portal.
- 2Start a new automation in the portal or ask Notis to build it.
- 3Write one instruction asking Notis to screenshot the affected webpage when a workflow run concludes with failure.
- 4Choose the GitHub workflow run state trigger and a reporting channel.
- 5Trigger one controlled workflow failure and inspect the result.
Questions about this workflow
What should the screenshot URL be?
Include the relevant staging, preview, or diagnostic webpage in your plain-language instruction.
Can the workflow run on every failure?
Yes, or you can describe a specific workflow in the instruction.
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
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.
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.
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.
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 Serpdog. 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 Serpdog.