Get LaunchDarkly team context when GitHub reviewers change
A reviewer change can be the cue to bring ownership context into the conversation.
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
List Teams
Tool to list all teams in launchdarkly. use after confirming credentials; supports pagination internally.
Why this helps
Changing reviewers can make responsibility feel fuzzy, especially on a fast-moving release.
- Makes ownership easier to inspect
- Reduces coordination churn
- Keeps review work moving
Setup
Build it in a few focused steps.
- 1Connect the GitHub and LaunchDarkly integrations once.
- 2Create the automation in the portal or ask Notis to set it up.
- 3Write a single prompt describing the team context to retrieve after reviewer changes.
- 4Choose the reviewer-change trigger and a reporting channel.
- 5Update reviewers on one real pull request to test it.
Questions about this workflow
Does this assign reviewers?
No. It retrieves LaunchDarkly team context after GitHub reviewer changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Launch darkly. A trigger fires from one place; an action lands in another.
GitHub triggers
Launch darkly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Flag Trigger Workflow
Tool to create a flag trigger workflow. use when setting up an automated trigger to toggle a flag in a specific environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Trigger Workflow
Tool to delete a specific flag trigger workflow. use after confirming the project key, feature flag key, environment key, and trigger workflow id.
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 Custom Roles
Tool to retrieve a list of all custom roles. use when you need to list roles for permissions audits or configuration reviews. note: results are paginated.
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 Environments
Tool to retrieve a list of all environments within a project. use after confirming the project key; supports pagination.
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 Code Reference Repositories
Tool to list code reference repositories. use when retrieving repositories for a specific project; includes pagination.
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.
List Projects
Tool to retrieve a list of all projects. use after confirming credentials to enumerate project keys and metadata.
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.
List Teams
Tool to list all teams in launchdarkly. use after confirming credentials; supports pagination internally.
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 Launch darkly, 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 Launch darkly.