Meet deployment failure with a practical recovery window
Notis turns a failed deployment status into a current solar outlook, helping you decide when a non-urgent rebuild or retry best fits local PV output.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
PV Generation Forecast
Tool to get solar energy production forecasts (hourly output and loss estimates) for a specific location. use when you need hourly pv generation data to optimize energy scheduling.
Why this helps
A failed rollout creates urgency and scattered attention, making it difficult to distinguish an immediate fix from compute that can wait.
- Adds timing context without another tab or reminder
- Supports a deliberate recovery plan for deferrable work
- Keeps successful deployments from generating unnecessary reports
Setup
Build it in a few focused steps.
- 1Connect GitHub and Corrently to Notis.
- 2Create an automation and write: “When GitHub creates a failed or error deployment status, fetch the Corrently PV forecast and suggest a strong-solar window for any non-urgent rebuild or retry.”
- 3Pick New Deployment Status Created and your run-report channel.
- 4Use a real test deployment failure to confirm the forecast arrives.
Questions about this workflow
Will this recommend delaying incident recovery?
No. The prompt explicitly applies the forecast only to non-urgent rebuilds or retries; urgent restoration stays immediate.
Can queued statuses be ignored?
Yes. Tell Notis to act only when the new status state is failure or error.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Corrently. A trigger fires from one place; an action lands in another.
GitHub triggers
Corrently actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
CO₂ Meter Update
Tool to create or update a co₂ meter reading for emissions tracking. use when sending new or updated electricity consumption readings to corrently.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
PV Generation Forecast
Tool to get solar energy production forecasts (hourly output and loss estimates) for a specific location. use when you need hourly pv generation data to optimize energy scheduling.
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 Corrently, 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 Corrently.