Skip to content
ClickRuntime

Automate New Relic

Watch your New Relic apps from your inbox or Slack: a morning list of open alert issues, a weekly comparison of error rate and response time, a ping when errors cross your threshold, and a warning when a synthetic monitor starts failing. You explain the check to your AI assistant, confirm the steps it proposes, and ClickRuntime runs it from then on.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

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.

Ideas

What you can automate in New Relic

Daily open-issue lists, week-over-week performance numbers, and quick alerts on error spikes and failing synthetic checks. These are ready-made starting points. Anything else you can describe works too.
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.

See how it works
Weekly

Get a weekly performance report for your apps

Every Monday you see throughput, error rate and response time per app, next to the week before.

See how it works
Every 5 minutes

Get a Slack alert when error rate passes 2%

If your app's error rate climbs above your limit, #ops hears once, and again only after it recovers and spikes again.

See how it works
Every 5 minutes

Hear when a synthetic monitor starts failing

When one of your New Relic synthetic checks fails, you get one Slack message per monitor until it passes again.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with New Relic, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any New Relic automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what New Relic should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every hour, check New Relic for any application whose error rate is above 2% and send me the app name and top error.

Every morning, post yesterday's New Relic Apdex and response time per app to Slack.

Every week, pull the slowest New Relic transactions, write them to Google Sheets, and create Jira tickets for any slower than 2 seconds.

Beyond chat

Have New Relic work when you're not in the chat

Connecting New Relic to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect New Relic

New Relic connects with a User key (it starts with `NRAK-`) that you create yourself. It queries NerdGraph with the same permissions as the person who made it.

New Relic

Developer / Observability

  1. In New Relic, open the user menu, then API keys, and choose Create a key.
  2. Set Key type to User, pick the account, give the key a name and create it.
  3. Copy the full key now; afterwards New Relic only shows its first 8 characters.
  4. In the ClickRuntime dashboard, save the key as a secret on Connections & secrets and choose your region (US or EU).

Good to know

New Relic limits that affect automations

  • A User key has the permissions of the user who created it, so make it with someone who can see the apps and monitors you want to watch.
  • US and EU accounts use different API hosts, so the region you choose must match your account.
  • License keys are for sending data into New Relic and won't work here; use a User key.
  • The complete key is shown only when it is created.

FAQ

Questions about automating New Relic

What does ClickRuntime do with my New Relic key?
It runs read queries through NerdGraph, such as NRQL queries for error rate and synthetic results and lookups of open alert issues. The ready automations don't change alert policies or settings.
How does the error-rate alert avoid spamming me?
It checks every 5 minutes, alerts once when the rate passes your threshold, and resets when the rate drops back, so you get one message per spike.
Can alerts arrive in real time?
The daily issue digest runs on a schedule. For instant delivery, a New Relic workflow with a Webhook destination can send issues to ClickRuntime as they open.
My account is in the EU. Does that work?
Yes. Choose the EU region when you add the key, and requests go to New Relic's EU API instead of the US one.
Do these automations use AI?
No, they are queries and comparisons. If you add a summary step later, AI is part of every ClickRuntime plan, so no separate AI key is needed.
Is this a New Relic connector for ChatGPT or Claude?
Not for chatting with New Relic data. A chat connector lets your assistant read and change New Relic while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each New Relic event.

Related pages

Keep exploring

Tell your assistant what New Relic should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude