# How to connect PagerDuty to OpenClaw (no API keys) > Connect PagerDuty to OpenClaw with ClawLink in one click — 363 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/pagerduty The usual route to PagerDuty access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical PagerDuty setup: install one ClawHub skill, connect PagerDuty in the browser, and OpenClaw can call real PagerDuty actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/pagerduty ## Setup It takes three steps to connect OpenClaw to PagerDuty. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PagerDuty** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect pagerduty # connect PagerDuty (browser OAuth) npx -y @useclawlink/cli actions pagerduty # list available actions npx -y @useclawlink/cli run pagerduty --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect PagerDuty in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use PagerDuty to add service to incident workflow trigger and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PagerDuty is connected in the dashboard, that agent calls the same 363 PagerDuty tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## PagerDuty MCP for OpenClaw Looking for a PagerDuty MCP server for OpenClaw? ClawLink connects PagerDuty to OpenClaw and exposes 363 PagerDuty tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) works the same way. ## What the OpenClaw PagerDuty integration can do 363 PagerDuty tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 363. ### 30 of 363 PagerDuty tools for OpenClaw | Tool | What it does | |---|---| | **Add service to incident workflow trigger** `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. | | **Aggregate escalation policy incident metrics** `pagerduty_aggregate_escalation_policy_incident_metrics` | This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. | | **Aggregate incident metrics with filters** `pagerduty_aggregate_incident_metrics_with_filters` | Retrieves and aggregates metrics for incidents across all services in PagerDuty. | | **Associate service dependencies** `pagerduty_associate_service_dependencies` | Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. | | **Associate team with automation action** `pagerduty_associate_team_with_automation_action` | This endpoint associates a specific team with an automation action in PagerDuty. | | **Audit escalation policy records** `pagerduty_audit_escalation_policy_records` | Retrieves the audit records for a specific escalation policy in PagerDuty. | | **Convert service rule by ID** `pagerduty_convert_service_rule_by_id` | Converts a service's Event Rules to Event Orchestration rules. | | **Count paused incident reports** `pagerduty_count_paused_incident_reports` | Retrieves the count of paused incident reports in the PagerDuty system. | | **Create a custom field for an incident type** `pagerduty_create_a_custom_field_for_an_incident_type` | Create a Custom Field for an Incident Type. | | **Create a field option for a custom field** `pagerduty_create_a_field_option_for_a_custom_field` | Creates a new field option for a custom field on an incident type. Field options represent the allowed values for multi-value or dropdown custom fields. Before using this action: 1. | | **Create a ruleset** `pagerduty_create_a_ruleset` | Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. | | **Create a trigger** `pagerduty_create_a_trigger` | Creates a new incident workflow trigger in PagerDuty. Triggers define when and how incident workflows are activated - either automatically based on conditions or manually by responders. | | **Fetch cache variable for event orchestration** `pagerduty_fetch_cache_variable_for_event_orchestration` | Retrieves detailed information about a specific cache variable in a PagerDuty event | | **Fetch custom incident field by ID** `pagerduty_fetch_custom_incident_field_by_id` | Retrieves detailed information about a specific custom field associated with incidents in | | **Fetch escalation polices list** `pagerduty_fetch_escalation_polices_list` | Retrieves a list of escalation policies configured in the PagerDuty account | | **Fetch event orchestrations** `pagerduty_fetch_event_orchestrations` | Retrieves a list of event orchestrations configured in the PagerDuty account | | **Fetch incident analytics by ID** `pagerduty_fetch_incident_analytics_by_id` | Retrieves raw analytics data for a specific incident in PagerDuty | | **Fetch incident list** `pagerduty_fetch_incident_list` | Retrieves a list of incidents from PagerDuty based on specified criteria | | **Fetch outlier incident by ID** `pagerduty_fetch_outlier_incident_by_id` | Retrieves detailed information about an outlier incident associated with a specific incident in | | **Fetch post update status** `pagerduty_fetch_post_update_status` | Retrieves detailed information about a specific post update on a PagerDuty status page | | **Fetch priorities list** `pagerduty_fetch_priorities_list` | Retrieves a list of existing priorities in the PagerDuty system, ordered from most severe to | | **Fetch related change events for incident** `pagerduty_fetch_related_change_events_for_incident` | Retrieves change events correlated with a specific incident, along with the reasons for | | **Fetch related incidents by ID** `pagerduty_fetch_related_incidents_by_id` | Retrieves a list of incidents that are potentially related to a specified incident in PagerDuty | | **Fetch runner teams integration** `pagerduty_fetch_runner_teams_integration` | Retrieves a list of teams associated with a specific Automation Action Runner in PagerDuty | | **Fetch status pages** `pagerduty_fetch_status_pages` | Retrieves a list of all status pages configured in the PagerDuty account | | **Fetch user contact method** `pagerduty_fetch_user_contact_method` | Retrieves detailed information about a specific contact method for a particular user in | | **Fetch vendor list** `pagerduty_fetch_vendor_list` | Retrieves a list of vendors or third-party integrations available in the PagerDuty platform | | **Filter and aggregate incident metrics** `pagerduty_filter_and_aggregate_incident_metrics` | Analyzes and aggregates incident metrics across teams in PagerDuty, allowing for detailed | | **Get a field option on a custom field** `pagerduty_get_a_field_option_on_a_custom_field` | Retrieves a specific field option from a custom field on an incident type | | **Get a trigger** `pagerduty_get_a_trigger` | Retrieves details of a specific incident workflow trigger by ID | ## Example prompts **Add Service To Incident Workflow Trigger** > Use PagerDuty to add service to incident workflow trigger and walk me through the result in plain English. **Aggregate Escalation Policy Incident Metrics** > Use PagerDuty to aggregate escalation policy incident metrics and walk me through the result in plain English. **Aggregate Incident Metrics With Filters** > Use PagerDuty to aggregate incident metrics with filters and walk me through the result in plain English. **Associate Service Dependencies** > Use PagerDuty to associate service dependencies and walk me through the result in plain English. ## ClawLink vs. building it yourself 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. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a PagerDuty app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect PagerDuty through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for PagerDuty. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right PagerDuty actions to the runtime in a format your agent can reliably use. | 363 tools for PagerDuty are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PagerDuty to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect PagerDuty in the browser, and the 363 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the PagerDuty skill but can't call the tools The ClawHub skill teaches OpenClaw about PagerDuty, but the calls run through the ClawLink plugin and your connected account. Make sure PagerDuty is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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. ### "Tool schema not loaded yet" error when calling PagerDuty tools PagerDuty tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every PagerDuty call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### PagerDuty returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, 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. ### Is there a OpenClaw PagerDuty integration? Yes. ClawLink is the fastest way to connect OpenClaw to PagerDuty: link your PagerDuty account once in the browser and OpenClaw can call the PagerDuty API through 363 ready-made tools — no custom code or token handling. ### How do I add PagerDuty to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PagerDuty skill from ClawHub, then you click Connect in the dashboard to authorize PagerDuty. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect PagerDuty to OpenClaw? About two minutes. Sign in, click Connect next to PagerDuty in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PagerDuty up myself? 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. ### OpenClaw installed the PagerDuty skill but can't call the tools The ClawHub skill teaches OpenClaw about PagerDuty, but the calls run through the ClawLink plugin and your connected account. Make sure PagerDuty is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications. - [Connect LaunchDarkly](https://claw-link.dev/openclaw/launch-darkly) — A feature management platform that helps teams build better software faster using feature flags.