Connect 100+ apps with one-click OAuthRead the docs
OpenClawOpenClaw×PagerDuty

Connect OpenClaw to PagerDuty

ClawLink connects OpenClaw to PagerDuty in one click with hosted OAuth, no manual app setup, and 12 tools your agent can call from chat.

ClawLink gives OpenClaw a more practical PagerDuty setup than rolling your own integration. Instead of building auth, token refresh, and tool wiring yourself, you connect once and start using real PagerDuty actions from chat.

  • One-click OAuth — no API keys
  • 12 tools available immediately.
  • First integration free.
OpenClaw
+
OpenClaw connected to PagerDuty through ClawLink

How to connect OpenClaw to PagerDuty

Three steps. No developer needed.

1

Install ClawLink

Add the ClawLink plugin to OpenClaw once. Takes under a minute.

2

Connect PagerDuty

Click Connect next to PagerDuty in the ClawLink dashboard. Authenticate in a single click.

3

Use from chat

Ask OpenClaw to use PagerDuty in plain English. ClawLink routes the call.

Why teams connect PagerDuty to OpenClaw

These use cases change by integration category, available tools, and setup model. This page is not just a cloned template with the logo swapped.

Use case

Resolve engineering work without switching tabs

Use PagerDuty through OpenClaw to inspect issues, repos, tasks, logs, or alerts while staying in the same conversation.

Use case

Ship routine updates faster

OpenClaw can pull the relevant context from PagerDuty, draft the next step, and execute common maintenance actions.

Use case

Keep debugging grounded in source data

Instead of relying on memory, ask OpenClaw to fetch the latest state from PagerDuty before it recommends a fix.

What OpenClaw can do with PagerDuty

12 PagerDuty tools available the moment you connect. Every action is one chat message away.

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 service. Prerequisites: - The incident workflow trigger must already exist (create with CREATE_A_TRIGGER) - The service must already exist in your account - The trigger must not be subscribed to all services Use when expanding automated workflows to additional services or incrementally rolling out workflows. This is an additive operation - use DELETE_INCIDENT_WORKFLOW_TRIGGER_SERVICE to remove services. Requires incident_workflows:write OAuth scope.

pagerduty_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 times, and escalation effectiveness. The endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. It provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting.

pagerduty_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 useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. The endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. However, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data.

pagerduty_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 effective incident management and impact analysis. It enables you to create multiple dependencies in a single API call, improving efficiency when setting up complex service relationships. Use this endpoint when you need to define or update the dependency structure of your services in PagerDuty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow.

pagerduty_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 processes. Use this endpoint when you need to assign responsibility for an automation action to a particular team or when restructuring your automation workflows. The association helps in tracking, auditing, and managing permissions for automation actions across different teams in your organization. Note that this endpoint only creates the association; it does not create new teams or automation actions.

pagerduty_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, and on-call schedules. It's particularly useful for compliance tracking, troubleshooting, and understanding how the incident response process has been adjusted over time. The audit records provide transparency into who made changes, what was changed, and when the changes occurred, helping teams maintain accountability and optimize their incident management workflows.

+ 6 more PagerDuty tools available after you connect.

Example prompts for OpenClaw + PagerDuty

Real examples based on the actual PagerDuty tools exposed through ClawLink.

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 service. Prerequisites: - The incident workflow trigger must already exist (create with CREATE_A_TRIGGER) - The service must already exist in your account - The trigger must not be subscribed to all services Use when expanding automated workflows to additional services or incrementally rolling out workflows. This is an additive operation - use DELETE_INCIDENT_WORKFLOW_TRIGGER_SERVICE to remove services. Requires incident_workflows:write OAuth scope

Use PagerDuty to 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 service. prerequisites: - the incident workflow trigger must already exist (create with create_a_trigger) - the service must already exist in your account - the trigger must not be subscribed to all services use when expanding automated workflows to additional services or incrementally rolling out workflows. this is an additive operation - use delete_incident_workflow_trigger_service to remove services. requires incident_workflows:write oauth scope and walk me through the result in plain English.

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 times, and escalation effectiveness. The endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. It provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting

Use PagerDuty to 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 times, and escalation effectiveness. the endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. it provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting and walk me through the result in plain English.

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 useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. The endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. However, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data

Use PagerDuty to 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 useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. the endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. however, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data and walk me through the result in plain English.

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 effective incident management and impact analysis. It enables you to create multiple dependencies in a single API call, improving efficiency when setting up complex service relationships. Use this endpoint when you need to define or update the dependency structure of your services in PagerDuty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow

Use PagerDuty to 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 effective incident management and impact analysis. it enables you to create multiple dependencies in a single api call, improving efficiency when setting up complex service relationships. use this endpoint when you need to define or update the dependency structure of your services in pagerduty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow and walk me through the result in plain English.

How ClawLink compares to manual PagerDuty setup

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want PagerDuty working from chat.

Connection flow

Manual setup

Register a PagerDuty app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift.

With ClawLink

Users connect PagerDuty through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code.

Ongoing maintenance

Manual setup

You own refresh logic, permission debugging, environment config, and every provider-specific edge case for PagerDuty.

With ClawLink

ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.

Agent usability

Manual setup

You still need to expose the right PagerDuty actions to the runtime in a format your agent can reliably use.

With ClawLink

12 tools for PagerDuty are already exposed through ClawLink, so the agent can read and act from chat immediately.

More Developer Tools connections for OpenClaw

If PagerDuty is only one part of the workflow, these nearby integrations are the next places to look.

What setup looks like for PagerDuty

Connect pagerduty through ClawLink's hosted Composio setup.

PagerDuty uses hosted oauth, so users connect once in the browser and ClawLink handles the token lifecycle after that.

OpenClaw works best when the request is concrete. Ask for a specific outcome in PagerDuty instead of a vague "check this" instruction.

Common connection issues

Connection succeeds but no tools appear

Reconnect PagerDuty from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

The PagerDuty account is connected but the action fails

Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, not ClawLink bugs.

OAuth finished in the browser but the account is still missing

Try reconnecting PagerDuty and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Using Hermes Agent?

Also available for Hermes Agent

Connect PagerDuty

Ready to connect PagerDuty?

Your first integration is free. Get OpenClaw talking to PagerDuty in under two minutes.

Connect PagerDuty to OpenClaw

No credit card required for the first integration.

ClawLink is the simplest way to connect OpenClaw to PagerDuty. Page canonical: https://claw-link.dev/openclaw/pagerduty.