Verify important content changes automatically
When a watched file or directory changes, the related page gets captured for a quick visual review.
Trigger
Repository Content Changed
Triggers when the content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires ``content_changed`` when the file is modified. For a directory, fires ``content_changed``, ``content_added``, or ``content_removed`` for modified, new, or deleted entries respectively. content.
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
Content changes can affect live pages without looking like traditional code changes, making manual verification easy to skip.
- Connect repository edits to visible outcomes
- Catch content regressions sooner
- Reduce repetitive manual page checks
Setup
Build it in a few focused steps.
- 1Connect GitHub and Serpdog to Notis once through the portal.
- 2Create the automation in Automations or ask Notis conversationally.
- 3Write one instruction telling Notis to screenshot the affected webpage whenever the watched repository content changes.
- 4Choose the GitHub repository content changed trigger and select a reporting channel.
- 5Change one test file or directory entry and confirm the screenshot.
Questions about this workflow
Can this watch a whole directory?
Yes. The GitHub trigger supports a configured file or directory path.
What kind of content works well?
Use it for content-backed pages, landing pages, documentation, or other visible outputs.
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.