New Relic Automation
Automate New Relic observability workflows -- manage alert policies, notification channels, alert conditions, and monitor applications and browser apps via the Composio MCP integration.
Get the complete skill folder, including its scripts and reference files.
This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.
When to use this skill
Use New Relic Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate New Relic observability workflows -- manage alert policies, notification channels, alert conditions, and monitor applications and browser apps via the Composio MCP integration.
When not to use it
Skip New Relic Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/new-relic-automation # Save SKILL.md to ~/.claude/skills/new-relic-automation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/new-relic-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/new-relic-automation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the New Relic Automation skill for this task: Use New Relic Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 80/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# New Relic Automation
Automate your New Relic observability workflows -- create and manage alert policies, configure notification channels (email, Slack, webhook, PagerDuty), monitor APM applications, inspect alert conditions, and integrate New Relic alerting into cross-app pipelines.
**Toolkit docs:** [composio.dev/toolkits/new_relic](https://composio.dev/toolkits/new_relic)
---
## Setup
1. Add the Composio MCP server to your client: `https://rube.app/mcp` 2. Connect your New Relic account when prompted (API key authentication) 3. Start using the workflows below
---
## Core Workflows
### 1. List Alert Policies
Use `NEW_RELIC_GET_ALERT_POLICIES` to discover existing alert policies with optional filtering.
``` Tool: NEW_RELIC_GET_ALERT_POLICIES Inputs: - name: string (optional, partial match supported) - incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET" - page: integer (1-indexed pagination) ```
### 2. Create an Alert Policy
Use `NEW_RELIC_CREATE_ALERT_POLICY` to set up a new policy container for alert conditions.
``` Tool: NEW_RELIC_CREATE_ALERT_POLICY Inputs: - name: string (required) -- must be unique within the account - incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET" (default: PER_POLICY) ```
**Incident preferences explained:** - `PER_POLICY` -- one issue per policy (recommended for most use cases) - `PER_CONDITION` -- one issue per alert condition - `PER_CONDITION_AND_TARGET` -- one issue per condition and signal/target
### 3. Create Alert Notification Channels
Use `NEW_RELIC_CREATE_ALERT_CHANNEL` to register notification endpoints for alert delivery.
``` Tool: NEW_RELIC_CREATE_ALERT_CHANNEL Inputs: - type: "email" | "slack" | "webhook" | "pagerduty" | "opsgenie" | "victorops" (required) - name: string (required) -- human-readable channel name - configuration: object (required) -- varies by type: Email: { recipients: "[email protected],[email protected]" } Slack: { url: "<slack_webhook_url>", channel: "alerts" } Webhook: { url: "https://hooks.example.com/alerts", auth_username, auth_password } PagerDuty: { service_key: "<integration_key>" } OpsGenie: { api_key, recipients, tags, teams } VictorOps: { key: "<api_key>", route_key: "<routing_key>" } ```
### 4. Get Alert Conditions for a Policy
Use `NEW_RELIC_GET_ALERT_CONDITIONS` to inspect the conditions attached to a specific policy.
``` Tool: NEW_RELIC_GET_ALERT_CONDITIONS Inputs: - policy_id: integer (required) ```
### 5. Monitor Applications
Use `NEW_RELIC_GET_APPLICATIONS` and `NEW_RELIC_GET_BROWSER_APPLICATIONS` to list APM and browser-monitored apps.
``` Tool: NEW_RELIC_GET_APPLICATIONS Inputs: - name: string (optional, case-insensitive partial match) - host: string (optional, case-insensitive partial match) - ids: string (optional, comma-separated list of app IDs) - page: integer (1-indexed)
Tool: NEW_RELIC_GET_BROWSER_APPLICATIONS Inputs: - filter[name]: string (optional, case-insensitive partial match) - page: integer (1-indexed) ```
### 6. Manage Channels and Policies
Use `NEW_RELIC_UPDATE_ALERT_CHANNEL` to modify existing channels and `NEW_RELIC_DELETE_ALERT_POLICY` to remove policies.
``` Tool: NEW_RELIC_UPDATE_ALERT_CHANNEL Inputs: - alert_channel_id: integer (required) - name: string (optional) - type: string (optional, only to change type) - configuration: object (optional, fields vary by type)
Tool: NEW_RELIC_DELETE_ALERT_POLICY Inputs: - policy_id: string (required) -- ID of the policy to delete ```
---
## Known Pitfalls
| Pitfall | Detail | |---------|--------| | Unique policy names | `NEW_RELIC_CREATE_ALERT_POLICY` requires the name to be unique within the account. | | Channel config varies by type | The `configuration` object for `NEW_RELIC_CREATE_ALERT_CHANNEL` has different required fields per channel type (e.g., `recipients` for email, `service_key` for PagerDuty). | | Pagination required | All list endpoints return paginated results. Iterate pages until results are exhausted. | | Policy ID type mismatch | `NEW_RELIC_GET_ALERT_CONDITIONS` expects `policy_id` as an integer, while `NEW_RELIC_DELETE_ALERT_POLICY` expects it as a string. | | Channel-policy linking | After creating a channel, you must separately associate it with a policy for alerts to flow to that channel. |
---
## Quick Reference
| Tool Slug | Description | |-----------|-------------| | `NEW_RELIC_GET_ALERT_POLICIES` | List alert policies with optional filtering | | `NEW_RELIC_CREATE_ALERT_POLICY` | Create a new alert policy | | `NEW_RELIC_DELETE_ALERT_POLICY` | Delete an alert policy by ID | | `NEW_RELIC_CREATE_ALERT_CHANNEL` | Create a notification channel (email, Slack, webhook, etc.) | | `NEW_RELIC_GET_ALERT_CHANNELS` | List all configured alert channels | | `NEW_RELIC_UPDATE_ALERT_CHANNEL` | Update an existing alert channel | | `NEW_RELIC_GET_ALERT_CONDITIONS` | Get alert conditions for a policy | | `NEW_RELIC_GET_APPLICATIONS` | List APM applications | | `NEW_RELIC_GET_BROWSER_APPLICATIONS` | List browser-monitored applications |
---
*Powered by [Composio](https://composio.dev)*
Intended uses
- Use New Relic Automation when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.