+
Connect GitHub to New relic
Automate GitHub and New relic with AI
A spike in New Relic often starts with a commit nobody remembers. On Operator.io, an OpenClaw agent reads the alert, pulls recent deploys and merged pull requests from GitHub, and posts a short timeline in chat with the likely change set. Hand it an error fingerprint and it opens a GitHub issue with stack context from New Relic attached.
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 GitHub and New relic
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
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 GitHub 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 GitHub, 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 GitHub and New relic
- How do I connect GitHub and New relic to Operator?
- You authorize GitHub 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 GitHub and New relic?
- Tell it the job and it moves between GitHub 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 GitHub and New relic in sync?
- Yes. It can watch GitHub 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.
GitHub and New relic integrations
Put your agent on GitHub 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