Keep pull request ownership clear
Reviewer changes come with the exact PR link to revisit.
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
Shorten URL with L2S
Tool to shorten a given long url. use when you need a concise link representation.
Why this helps
Reviewer assignments can change quietly, leaving founders unsure who is expected to act next.
- Clarify review ownership
- Reduce coordination messages
- Keep the next action visible
Setup
Build it in a few focused steps.
- 1Connect GitHub and L2s to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use this instruction: When requested reviewers change on a GitHub pull request, shorten the pull request URL with L2s and report the added and removed reviewers with the compact link.
- 4Pick the reviewer changed trigger and a channel for reports.
- 5Test it with one real reviewer change.
Questions about this workflow
Can it report both additions and removals?
Yes. The trigger provides the current, added, and removed reviewer lists.
Does it modify GitHub reviewers?
No. It reports the change and creates a shareable link.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to L2s. A trigger fires from one place; an action lands in another.
GitHub triggers
L2s actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get URL Details
Tool to retrieve details of a shortened url. use when you need metadata about a specific shortened link. use after obtaining a valid url id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Settings
Tool to retrieve current user's settings. use after authentication to fetch email, notification, and appearance preferences.
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 Shortened URLs
Tool to list all shortened urls. use after user authentication to retrieve the user's urls with pagination details.
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.
Shorten URL with L2S
Tool to shorten a given long url. use when you need a concise link representation.
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 L2s, 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 L2s.