Analyze pull request changes
Understand the meaning behind a changing pull request.
Trigger
Pull Request State / Properties Changed
Triggers when a specific GitHub pull request changes any of these tracked properties: state (open/closed), title, body, draft status, lock status, merge status, assignees, labels, requested reviewers, or milestone. The payload includes the full current PR details, the list of changed field names, and their previous values.
Action
/api/x402/research
AI-powered Token Deep Research API
Why this helps
A PR can shift from draft to ready, change reviewers, or alter scope without a clear handoff to everyone involved.
- Highlight changes that affect review coordination.
- Keep ownership and readiness visible.
- Avoid acting on an outdated understanding of the PR.
Setup
Build it in a few focused steps.
- 1Connect GitHub and www.capminal.ai to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it by chat.
- 3Use this instruction: Research each meaningful GitHub pull request property change and explain what changed, its likely impact on review or merge readiness, and the next coordination step.
- 4Select the pull request state or properties changed trigger and choose a run-report channel.
- 5Test with one changed pull request.
Questions about this workflow
Which changes can it monitor?
The trigger covers fields such as state, title, body, draft status, merge status, assignees, labels, reviewers, and milestone.
Can it focus on ready-for-review changes?
Yes. Ask the instruction to prioritize draft status and review readiness changes.
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.