Make reviewer ownership obvious
Everyone should know who is waiting on whom.
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
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Why this helps
Reviewer requests can change quietly, leaving follow-up dependent on memory and repeated checking.
- Highlights reviewer additions and removals
- Clarifies the next follow-up
- Reduces coordination messages
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mural to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to add reviewer-list changes to a Mural coordination mural with the pull request link and current reviewers.
- 3Pick the GitHub Pull Request Reviewers Changed trigger.
- 4Choose a run-report channel and test with one reviewer change.
Questions about this workflow
Can it show removed reviewers too?
Yes. Ask Notis to summarize both added and removed reviewers.
Is this useful for small teams?
Yes. It makes handoffs explicit even when only a few people share review responsibility.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mural. A trigger fires from one place; an action lands in another.
GitHub triggers
Mural actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get current user
Tool to retrieve information about the currently authenticated user. use when you need current user details after authentication.
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.
Get files for a mural
Tool to retrieve a list of file widgets in a mural. use after confirming the mural id when listing file attachments.
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 Mural Widgets
Tool to retrieve all widgets within a specified mural. use after confirming the mural id is correct.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
MURAL Authorization Request
Tool to initiate the oauth 2.0 authorization process. use when you need to redirect a user to mural to obtain an authorization code.
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.
Not just GitHub and Mural. Any 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 Mural.