Check Zyte components after GitHub content changes
Give changes to scraper-adjacent code a dependency snapshot automatically.
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
Zyte API Components
Tool to fetch the list of zyte api service components and their statuses. use when you need a current snapshot of component health from the zyte status page.
Why this helps
A focused file change can lead to broad, distracting status checks before validation begins.
- Keeps checks tied to relevant changes
- Makes dependency status easy to scan
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zyte api once in Notis.
- 2Create a new portal automation.
- 3Write: When monitored repository content changes, fetch Zyte API component statuses and report them.
- 4Choose Repository Content Changed and a channel.
- 5Test with a change in the monitored path.
Questions about this workflow
Can it watch a directory?
Yes, use the repository content trigger for a configured file or directory.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Zyte api. A trigger fires from one place; an action lands in another.
GitHub triggers
Zyte api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Fetch Active Scheduled Maintenances
Tool to fetch currently active scheduled maintenances. use when you need to know ongoing maintenance events.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get scheduled maintenances
Tool to get the 50 most recent scheduled maintenances (upcoming and completed) from zyte status api. use after confirming you need the latest maintenance schedule for monitoring.
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.
Zyte API: Get Unresolved Incidents
Tool to retrieve unresolved incidents from zyte status api. use when you need to check currently open incidents.
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.
List Zyte API status incidents
Tool to list the 50 most recent incidents on the zyte api status page. use after needing current api health or incident summaries.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Zyte Status Summary
Tool to get a summary of status indicators, component statuses, unresolved incidents, and scheduled maintenances. use when you need an overview of the current zyte service health.
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.
Upcoming Scheduled Maintenances
Tool to retrieve upcoming scheduled maintenance windows. use when you need to list upcoming maintenance events from the zyte api status page.
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.
Zyte API Components
Tool to fetch the list of zyte api service components and their statuses. use when you need a current snapshot of component health from the zyte status page.
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.
Get Zyte API Status Rollup
Tool to retrieve the overall status rollup for the zyte api. use when you need a current summary of service health before proceeding.
Connect any two apps with Notis in the middle.
GitHub and Zyte api, 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 Zyte api.