Keep reviewer ownership from going stale
When the reviewer list changes, the coordination around the pull request can update with it.
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
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
Why this helps
Reviewer requests are easy to miss or forget after reassignment, especially across several active pull requests.
- Surface added, removed, and re-requested reviewers.
- Keep reviewer ownership connected to downstream processes.
- Reduce manual follow-up around code review requests.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Nango to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to create it.
- 3Tell Notis: When the requested reviewers for a GitHub pull request change, trigger my Nango reviewer-coordination action with the current, added, removed, and previous reviewer lists.
- 4Select the reviewer-change trigger, choose the channel for run reports, and test with one reviewer update.
Questions about this workflow
Does it include teams as well as individuals?
Yes. The GitHub payload includes both requested users and teams.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Nango. A trigger fires from one place; an action lands in another.
GitHub triggers
Nango actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Connections
Tool to list all connections. use when you need to retrieve existing connections.
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.
List Connections
Tool to list all connections without credentials. use when you need connection metadata across your account without exposing credentials.
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.
Get Provider Details
Tool to retrieve details for a specific provider. use when you need to fetch provider configuration details by name (e.g., 'salesforce'). use after selecting the provider.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Providers
Tool to retrieve a list of all available providers. use when you need to display or iterate through every provider before creating connections.
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.
Get Scripts Configuration
Tool to fetch the nango scripts configuration. use when you need to get the available scripts and their triggers.
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.
Trigger Sync
Tool to trigger a sync process manually. use after establishing a connection and defining a sync.
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 Nango, 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 Nango.