+
Connect Jira to New relic
Automate Jira and New relic with AI
Performance regressions in New Relic need a Jira ticket with the right trace context before the same alert fires twice. Your Operator agent on OpenClaw opens or updates Jira issues when New Relic alerts cross thresholds you define, attaches APM and error details to the description, and can close the Jira item when New Relic shows recovery. Ask for open alerts tied to the checkout service and it merges New Relic incidents with Jira issue status.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Jira and New relic
What your agent does in Jira
Add Attachment
Uploads and attaches a file to a Jira issue.
Add Comment
Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.
Add Users to Project Role
Adds users and optionally groups to a project role.
Add User to Group
Adds a user to a Jira group.
Add Watcher to Issue
Adds a user to an issue's watcher list by account ID. Requires the authenticated user to have permission to view the issue and manage watchers; insufficient permissions may result in silent failure or an error response.
Add Worklog
Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.
What your agent does in New relic
Add Notification Channels to Policy
Tool to add notification channels to an alert policy using the NerdGraph GraphQL API. Use when you need to associate existing notification channels with an alert policy to receive notifications when alerts trigger.
Add Tags to Entity
Tool to add tags with values to a specific New Relic entity via NerdGraph GraphQL API. Use when you need to organize and categorize entities for filtering and organization. Note: For APM agents, a restart may be required after adding new...
Add Widgets to Dashboard Page
Tool to add widgets to an existing New Relic dashboard page via NerdGraph GraphQL API. Use when you need to programmatically add visualizations (line charts, area charts, bar charts, tables, etc.) to a dashboard page. Requires the dashbo...
Configure Cloud Integration
Tool to enable and configure cloud integrations for monitoring in New Relic. Use this to set up monitoring for AWS, Azure, or GCP services. The cloud account must be linked to New Relic before configuring integrations.
Create AI Notifications Channel
Tool to create a New Relic AI Notifications channel via NerdGraph GraphQL API. Use when setting up notification channels for Applied Intelligence alerts. Requires a pre-existing destination (created via aiNotificationsCreateDestination).
Create AI Notifications Destination
Tool to create an AI notifications destination in New Relic for services like Jira or ServiceNow. Use when you need to configure a new notification endpoint for AI-powered alerts.
How it works
Tell the agent what you want to happen between Jira and New relic, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Jira, works out what to do, and runs the matching action in New relic without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Jira and New relic
- How do I connect Jira and New relic to Operator?
- You authorize Jira and New relic once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Jira and New relic?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Jira and New relic actions on its own, so you do not map fields or pick triggers.
- Can my agent keep Jira and New relic in sync?
- Yes. It can watch Jira and act in New relic, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Jira and New relic integrations
Put your agent on Jira and New relic
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free