Integrations · New Relic
Guild agents run NerdGraph queries against your New Relic observability and monitoring data. You control which agents can reach which operations through credential policies, and Guild injects the API key server-side so agent code never sees it. Every credential use is subject to Guild’s audit trail.
Book a demo
See how teams govern agents that use New Relic.
Start free
Connect New Relic and scope your first agent.
What the New Relic integration exposes
The@guildai-services/guildai~newrelic package adds New Relic tools to any Guild agent. The current published version includes newrelic_query, which runs a GraphQL (NerdGraph) query against New Relic. The tools table on this page reflects the latest published version and updates automatically.
How it works
1
Open Credentials in Guild
Go to Credentials in Guild under Access & setup. This is where all third-party service credentials are managed.
2
Connect your New Relic API key
Click New Relic and enter your New Relic API key. Guild stores it and injects it server-side on every agent request.
3
Add the tools to an agent
Import
newrelicTools from @guildai-services/guildai~newrelic and spread it into your agent’s tools object. The agent can then call New Relic tools without handling the credential directly.Why New Relic access needs governing in an agent context
Agents that can run arbitrary NerdGraph queries can read sensitive observability data across your stack. Guild’s credential proxy enforces credential policies before any request leaves Guild, letting you write ALLOW and DENY rules scoped to specific operations, agents, or workspaces. A DENY rule always wins, so you can block destructive or sensitive query patterns while leaving routine monitoring queries open. Guild stores the New Relic API key as a server-side credential and injects it at request time. Agent code, containers, prompts, and state never see it. You can scope a credential to one workspace, one agent, or one member, and revoke access without touching agent code. Unscoped credentials fall back to account-wide access, making explicit scoping the safer default.About the New Relic integration
The@guildai-services/guildai~newrelic package provides agents with access to New Relic observability and monitoring data through Guild’s integration.
Authentication
- Type: API key
Setup
1
Open Credentials
Go to Credentials in Guild.
2
Connect New Relic
Click New Relic and enter your New Relic API key.
Usage
Tools
Tools in the latest published version ofguildai~newrelic:
Frequently asked questions
Can I limit which agents can query New Relic?
Can I limit which agents can query New Relic?
Yes. Credential policies support an
agents field that scopes rules to specific agents. You can also dedicate a credential to a single agent from the installed agent’s page, so no other agent uses it.Does the agent ever see my New Relic API key?
Does the agent ever see my New Relic API key?
No. Guild’s credential proxy injects the API key server-side after the policy check passes. The key never enters the agent’s code, container, prompt, or state.
Can I get notified when New Relic sends a webhook event?
Can I get notified when New Relic sends a webhook event?
Not yet. The New Relic catalog entry lists no webhook events, so event-triggered runs from New Relic are not currently supported through this integration.
Can one New Relic credential serve multiple workspaces?
Can one New Relic credential serve multiple workspaces?
Yes. An account-scoped credential serves every workspace the account owns by default. You can also scope it to a single workspace, a single member, or a single agent if you need tighter separation.
Put a governed agent on New Relic this week
Book a demo
See how teams govern agents that use New Relic.
Start free
Connect New Relic and scope your first agent.