Daily

Get a morning list of open alert issues

Each day starts with an email of the New Relic alert issues still open, sorted by priority.

Runs: Daily
Apps: New Relic
AI: Not needed
Access: user key (read)

Send this to your assistant

Create a ClickRuntime automation: every weekday at 8am email me all open New Relic alert issues with their priority and how long they've been open.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

New Relic groups related alert conditions into issues, and a busy account can have a dozen open at once: a slow checkout service, a database CPU warning, a synthetic monitor flapping. The notifications arrive throughout the week, and people acknowledge them in the moment and move on. A month later nobody can say which issues are still open, and a degraded service has been quietly running with a red flag that everyone learned to ignore.

Each morning ClickRuntime queries New Relic's NerdGraph API for issues that are still open, collects their titles, priority, affected entities and how long they have been open, and emails one list. When the list is empty the email can be skipped, so every message means something needs a decision from you.

Engineering managers and on-call leads use it as a daily handover note they never have to write.

What you get out of it

Issues that nobody closed are visible daily
An issue open for nine days appears with its age every morning. Pressure builds naturally to either fix the cause or tune the condition, so the account stops carrying permanent red flags.
A shared starting point for standup
The team begins the day with one list of what is currently broken or degraded. Standup spends time deciding who owns each issue, not on collecting the list from three dashboards.
Handovers between on-call shifts improve
The person starting a rotation sees every open issue with its priority and age. They do not depend on a chat message from the previous engineer who was busy fixing something.
Noisy conditions get tuned
If the same issue opens and closes every few days, it shows up repeatedly in the email. That is evidence for raising a threshold or adding a condition rule, instead of tolerating alert fatigue.
Leadership gets a view without dashboards
A manager who does not log in to New Relic can still read which services have open problems. Conversations about reliability are based on a real list rather than anecdotes.

How it works

What happens, step by step

Every morning, ClickRuntime asks New Relic for the alert issues that are still open.
It sorts them by priority, critical first, and notes how long each has been open.
You get one email with a line per issue, such as "[CRITICAL] checkout-api error rate above 2% (open 14h)".

Before it runs live

Connect New Relic

What you get

RunsDaily

Get a morning list of open alert issuestoday, 9:00Succeeded

Email · Open New Relic issues[CRITICAL] checkout-api error rate above 2% (open 14h) [HIGH] Northwind sync latency above 3s (open 3h)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other New Relic steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_a_daily_digest_of_open_issues.pyexample

from datetime import datetime, timezone
from clickruntime import on_trigger, credentials, http, notify

ACCOUNT_ID = 1234567
QUERY = """{ actor { account(id: %d) { aiIssues { issues(filter: {states: [ACTIVATED, CREATED]}) {
  issues { title priority activatedAt } } } } } }""" % ACCOUNT_ID

@on_trigger
def run(event):
    resp = http.post("https://api.newrelic.com/graphql", json={"query": QUERY},
                     headers={"API-Key": credentials.secret("NEW_RELIC_USER_KEY")})
    resp.raise_for_status()
    issues = resp.json()["data"]["actor"]["account"]["aiIssues"]["issues"]["issues"]
    now = datetime.now(timezone.utc).timestamp() * 1000
    lines = []
    for i in sorted(issues, key=lambda i: i["activatedAt"] or now):
        hours = (now - (i["activatedAt"] or now)) / 3_600_000
        lines.append(f"[{i['priority']}] {i['title'][0]} (open {hours:.0f}h)")
    notify.email_me(f"{len(issues)} open New Relic issues", "\n".join(lines) or "No open issues.")
    return {"open": len(issues)}

FAQ

Common questions

What is an issue in New Relic?

An issue is New Relic's grouping of related incidents and alert events, so several conditions firing on one problem appear as one item. The digest reads these through the aiIssues query in NerdGraph. Related alert events are merged, so the digest lists problems rather than raw alerts.

Which New Relic key does it need?

A user API key, stored as a secret in ClickRuntime, from a user who can see the accounts you want to cover. The automation only reads issues and cannot acknowledge or close them. Anything you do not name is skipped, so the list stays short.

Can I limit the digest to critical issues?

Yes. Issues carry a priority such as CRITICAL or HIGH, and the query can filter on it, or on specific entities or accounts. Name the priority levels you want and the digest will list only those.

What permissions does it need?

user key (read). Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Weekly