Guard LaunchDarkly rollouts after GitHub production deployments
Let a production deployment status start the rollout safeguard work while your attention stays on the release.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
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.
Why this helps
Release steps scattered across tools make it easy to forget the feature flag follow-up at the busiest moment.
- Keeps rollout safeguards tied to real deployments
- Reduces release-day context switching
- Creates an auditable handoff
Setup
Build it in a few focused steps.
- 1Connect GitHub and LaunchDarkly to Notis once in the portal.
- 2Open Automations and choose New Automation.
- 3Describe the deployment safeguard outcome in one plain-language prompt.
- 4Pick the GitHub deployment status trigger and a channel for run reports.
- 5Test it with one real production deployment status.
Questions about this workflow
Does this need field mapping?
No. Describe the deployment outcome in plain language and Notis handles the details.
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
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.
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.
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.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 Environments
Tool to retrieve a list of all environments within a project. use after confirming the project key; supports pagination.
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 Code Reference Repositories
Tool to list code reference repositories. use when retrieving repositories for a specific project; includes pagination.
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.
List Projects
Tool to retrieve a list of all projects. use after confirming credentials to enumerate project keys and metadata.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
List Teams
Tool to list all teams in launchdarkly. use after confirming credentials; supports pagination internally.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Launch darkly. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Launch darkly.