+
Connect Pagerduty to Supabase
Automate Pagerduty and Supabase with AI
Supabase edge functions and auth spikes should page with context, not a bare alert in PagerDuty. On Operator.io, an OpenClaw agent reads the PagerDuty incident, pulls recent Supabase logs and error rates for the project you name, adds that summary to the incident timeline, and can run the health checks you keep in chat when the on call asks. Resolve from PagerDuty and it logs what changed in Supabase alongside the resolution note.
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 Pagerduty and Supabase
What your agent does in Pagerduty
Add service to incident workflow trigger
Adds a service to an existing incident workflow trigger in PagerDuty, enabling the trigger to fire for incidents on that service. Associates a specific service with an incident workflow trigger to automate incident management for that se...
Aggregate escalation policy incident metrics
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response time...
Aggregate incident metrics with filters
Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly us...
Associate service dependencies
Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effectiv...
Associate team with automation action
This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response proce...
Audit escalation policy records
Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services...
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 Pagerduty 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 Pagerduty, 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 Pagerduty and Supabase
- How do I connect Pagerduty and Supabase to Operator?
- You authorize Pagerduty 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 Pagerduty and Supabase?
- Tell it the job and it moves between Pagerduty and Supabase 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 Pagerduty and Supabase in sync?
- Yes. It can watch Pagerduty 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.
Pagerduty and Supabase integrations
Put your agent on Pagerduty 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