Understand what changed in your issue backlog
Important issue changes come with a quick impact summary, so you can adjust attention before work drifts.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
Why this helps
Backlog changes can quietly alter priorities, ownership, or commitments without creating a clear moment of review.
- See the impact of backlog changes
- Catch ownership shifts
- Reduce silent priority drift
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ai ml api to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis to create it.
- 3Use this instruction: When a GitHub issue changes state, title, body, assignee, label, milestone, or other tracked property, ask Ai ml api to explain what changed and its likely impact on priority, ownership, or next steps, then send me the summary.
- 4Pick the issue state or properties changed trigger and choose the channel for run reports.
- 5Test it with one updated issue.
Questions about this workflow
Will every small edit run it?
The GitHub trigger monitors tracked properties, and the instruction can tell Ai ml api to focus on meaningful changes.
Can it highlight ownership changes?
Yes. The prompt explicitly asks it to evaluate ownership and priority impact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ai ml api. A trigger fires from one place; an action lands in another.
GitHub triggers
Ai ml api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Moderation Completion
Tool to classify input text or image for safety using a moderation model. use after receiving user-generated content to filter out unsafe material.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
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 Ai ml 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 Ai ml api.