+
Connect Linear to New relic
Automate Linear and New relic with AI
New Relic alerts and Linear issue queues stay separate until someone manually copies trace details. Your Operator agent on OpenClaw opens a Linear issue when a New Relic alert crosses thresholds you define, attaches APM and error metadata to the description, and marks Linear done when New Relic shows recovery. Ask for open alerts tied to the API team and it merges New Relic incidents with Linear 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 Linear and New relic
What your agent does in Linear
Create attachment
Creates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to comment
Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
Create a comment
Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
Create linear issue
Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, assignee_id, cycle...
Create issue relation
Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
Create a label
Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and exis...
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 Linear 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 Linear, 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 Linear and New relic
- How do I connect Linear and New relic to Operator?
- You authorize Linear 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 Linear and New relic?
- Tell it the job and it moves between Linear and New relic as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Linear and New relic in sync?
- Yes. It can watch Linear 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.
Linear and New relic integrations
Put your agent on Linear 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