Refresh voice options when reviewers change
Keep your review communication setup ready as ownership and reviewers shift.
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
Get Voices List
Gets a list of voices in lmnt.
Why this helps
Changing reviewers can expose gaps in the way review updates are communicated and heard.
- Keep review communication options current.
- Reduce setup work when responsibilities move.
- Support a consistent team update format.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Lmnt to Notis once through the portal.
- 2Create the automation with one plain-language outcome instruction.
- 3Use this instruction: When the requested reviewers on a GitHub pull request change, retrieve the current Lmnt voice list and report the best available voice option for review updates.
- 4Select the reviewer-change trigger and choose a reporting channel.
- 5Test it by adding or removing one reviewer.
Questions about this workflow
Why connect reviewer changes to voices?
Teams can use the event to refresh the voice configuration behind spoken review updates.
Can the workflow choose a voice automatically?
Ask Notis to recommend a voice based on the current Lmnt list and your stated preference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Lmnt. A trigger fires from one place; an action lands in another.
GitHub triggers
Lmnt actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Voice
Creates a voice in lmnt.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Voice Info
Deletes information about a specific voice in lmnt.
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 Account
Gets an account in lmnt.
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 Voice Info
Gets information about a specific voice in lmnt.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Voices List
Gets a list of voices in lmnt.
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 Synthesize Speech
Synthesizes speech from text using a specific voice in lmnt.
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.
Update Voice Info
Updates information about a specific voice in lmnt.
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 Lmnt, 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 Lmnt.