Bring alert-policy configuration into release follow-up
Publishing a release is a useful point to remember monitoring configuration. Notis can list existing New Relic alert policies when GitHub records that the release is published.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Get Alert Policies
Tool to retrieve a list of alert policies. use when you need to list existing alert policies with optional filtering and pagination.
Why this helps
Alert configuration can be overlooked when release work and monitoring setup live in separate tools.
- Surface configured alert policies in a release-related report.
- Create a lightweight reminder to review monitoring configuration.
- Keep the action read-only; it does not evaluate policy coverage or alert status.
Setup
Build it in a few focused steps.
- 1Connect GitHub and New Relic to Notis once in the portal.
- 2Create an automation with one plain-language instruction: when the release is no longer a draft and its published timestamp is set. retrieve the configured New Relic alert-policy list and include the returned configuration context in the run report.
- 3Select the GitHub release-state-changed trigger and choose where Notis should send run reports.
- 4Test with one matching GitHub event and confirm the report shows only the returned New Relic configuration data; it does not retrieve alert firings, metric data, or release coverage..
Questions about this workflow
Does this tell me whether a New Relic alert fired for this release?
No. It retrieves configured alert policies only. It does not return incidents, alert events, metric values, or evidence that a policy covers the released application.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to New relic. A trigger fires from one place; an action lands in another.
GitHub triggers
New relic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Notification Channel
Tool to create an alert notification channel. use when you need to register a new endpoint (email, webhook, etc.) for alert notifications.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Policy
Tool to create an alert policy. use when you need to programmatically set up a new alert policy in new relic.
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.
Delete alert policy
Tool to delete an existing alert policy via rest api. use when you have the policy id and want to remove it via new relic's rest api. use after confirming the policy id exists.
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 Alert Channels
Tool to retrieve a list of alert notification channels. use when you need to list all configured channels after verifying your api key.
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 Alert Conditions
Tool to retrieve alert conditions for a specified policy. use after you have the policy id.
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 Alert Policies
Tool to retrieve a list of alert policies. use when you need to list existing alert policies with optional filtering and 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.
Get Applications
Tool to retrieve a list of new relic applications. use when you need to list all applications or filter by name, host, or ids after authenticating your api key.
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.
Get Browser Applications
Tool to list new relic browser applications. use when you need to retrieve all browser applications or filter by name after authenticating your api key.
Connect any two apps with Notis in the middle.
GitHub and New relic, 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 New relic.