Analyze deployment configuration changes
Make deployment changes legible before they become surprises.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
/api/x402/research
AI-powered Token Deep Research API
Why this helps
Small deployment metadata changes can alter release behavior without being obvious in the moment.
- Understand which deployment changes deserve attention.
- Surface environment and release implications.
- Reduce the need to manually compare deployment details.
Setup
Build it in a few focused steps.
- 1Connect GitHub and www.capminal.ai to Notis once through the portal.
- 2Create the automation in Automations or ask Notis to set it up by message.
- 3Use this instruction: Research each meaningful GitHub deployment state change and explain the changed fields, their likely release implications, and any follow-up checks worth considering.
- 4Choose the GitHub deployment state changed trigger and a channel for reports.
- 5Test with one changed deployment.
Questions about this workflow
What fields can trigger it?
The trigger monitors fields such as environment, task, SHA, ref, description, and production status.
Can it prioritize production changes?
Yes. Ask the instruction to focus first on changes affecting production environments.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to www.capminal.ai. A trigger fires from one place; an action lands in another.
GitHub triggers
www.capminal.ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
/api/x402/research
AI-powered Token Deep Research API
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 www.capminal.ai, 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 www.capminal.ai.