Mirror hotfix PR milestones into the incident
Notis turns meaningful pull request changes into a clean incident update, giving responders progress without another status meeting.
Trigger
Pull Request Updated
Triggers when an existing pull request is updated in a GitHub repository. Updates include title edits, description changes, label changes, assignee changes, reviewer requests, draft status changes, base branch changes, being closed, merged, or reopened. Only pre-existing PRs that receive an update will fire the trigger; newly created PRs are excluded. Supports optional filters: state, base branch, head branch, author, label, and draft status.
Action
Edit Incident V2
Tool to edit an existing incident in incident.io. Use when you need to update incident details like name, summary, severity, status, custom fields, or role assignments.
Why this helps
The response team cannot tell whether a fix is still drafting, ready for review, merged, or reopened without jumping into GitHub.
- Makes merge and reopen events visible to responders
- Reduces status questions to engineers
- Keeps incident details aligned with remediation state
Setup
Build it in a few focused steps.
- 1Connect GitHub and incident.io in Notis once.
- 2Ask Notis to update the matching incident when the hotfix PR becomes ready, merges, closes without merge, or reopens.
- 3Pick Pull Request Updated as the trigger and choose a run-report channel.
- 4Change the state of a linked test PR and review the incident update.
Questions about this workflow
Can description-only edits be ignored?
Yes. List only the milestone changes that matter in the automation prompt.
Can a merge move the incident toward resolution?
Yes. Tell Notis how a merged hotfix should change the incident summary or status while keeping final verification explicit.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to incident.io. A trigger fires from one place; an action lands in another.
GitHub triggers
incident.io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Attribute V2
Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract and organize information from incoming alerts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Route V2
Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and templates.
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.
Create Alert Source V2
Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
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.
Create Catalog Entry V2
Tool to create a catalog entry in incident.io. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Catalog Entry V3
Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
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.
Create Catalog Type V3
Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.
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.
Create Custom Field Option
Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
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.
Create Custom Field V2
Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
Connect any two apps with Notis in the middle.
GitHub and incident.io, 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 incident.io.