Skip to content
Notis

Research pull request reviewer changes

Keep review ownership clear as the reviewer list shifts.

Trigger

GitHub Pull Request Reviewers Changed

Triggers when the list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the full current reviewer list (users and teams with details), which reviewers were added, which were removed, and the previous reviewer list for reference.

Action

/api/x402/research

AI-powered Token Deep Research API

Why this helps

Reviewer changes can create uncertainty about who is waiting, who owns the next move, and what expertise is needed.

  • Clarify the significance of a reviewer change.
  • Reduce coordination messages and repeated checking.
  • Keep the next review handoff visible.

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 create it conversationally.
  • 3Use this instruction: Research each GitHub pull request reviewer change and summarize what changed, why the reviewer mix may matter, and what coordination or follow-up is advisable.
  • 4Pick the pull request reviewers changed trigger and a reporting channel.
  • 5Test with one reviewer change.

Questions about this workflow

Does it contact reviewers?

No. It provides research and coordination guidance through Notis.

Can it explain team reviewer changes?

Yes. The event includes the current reviewer list and changes, which the instruction can ask it to interpret.

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.

TriggerScheduled

/api/x402/research

AI-powered Token Deep Research API

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

TriggerPolling

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.

TriggerPolling

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.