Review Zyte maintenance after GitHub release changes
Keep release updates grounded in recent maintenance activity.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
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.
Why this helps
Release edits and publication changes often happen under pressure, leaving little room to check vendor history.
- Adds context to release changes
- Avoids separate status-page research
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zyte api to Notis once.
- 2Create a new automation in the portal.
- 3Write: When a GitHub release changes, get recent Zyte scheduled maintenances and report them.
- 4Select GitHub Release State Changed and a channel.
- 5Test with a release update.
Questions about this workflow
Does this monitor release assets too?
The selected release trigger detects the documented release changes.
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.