+
Connect New relic to Supabase
Automate New relic and Supabase with AI
Slow queries in Supabase often show up in New Relic before anyone checks the database dashboard. OpenClaw on Operator ties alerts to the Supabase project and tables involved, posts a short timeline with trace links into the channel you use for incidents, and opens a follow up task when error rate crosses the threshold you name. Hand it a spike time range and it correlates New Relic transactions with Supabase performance data.
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 New relic and Supabase
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.
What your agent does in Supabase
Create project api key
Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
Delete an API key from the project
Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
Delete third party auth config
Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
Get a third-party integration
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
List third-party auth integrations for project
Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
Update an API key for the project
Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.
How it works
Tell the agent what you want to happen between New relic and Supabase, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from New relic, works out what to do, and runs the matching action in Supabase 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 New relic and Supabase
- How do I connect New relic and Supabase to Operator?
- You authorize New relic and Supabase 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 New relic and Supabase?
- 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 New relic and Supabase actions on its own, so you do not map fields or pick triggers.
- Can my agent keep New relic and Supabase in sync?
- Yes. It can watch New relic and act in Supabase, 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.
New relic and Supabase integrations
Put your agent on New relic and Supabase
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