Skip to main content
Integrations · PagerDuty
A Guild agent can manage the full PagerDuty incident lifecycle, on-call schedules, escalation policies, services, event orchestrations, status pages, and teams through the PagerDuty REST API. Guild stores the REST API key server-side and injects it into every request, so agent code never sees the credential. Credential policies let you restrict which operations each agent may call, and every request is auditable through Guild’s credential proxy.

Book a demo

See how teams govern agents that use PagerDuty.

Talk to sales

Get access to Guild, then connect PagerDuty to your first agent.

What the PagerDuty integration exposes

The integration is guildai~pagerduty-openapi and its tools cover incidents, services, escalation policies, on-call schedules, event orchestrations, automation actions, status page posts, analytics, and team and user management. Tools follow the pagerduty_openapi_ prefix convention. Use pick() from the SDK to include only the tools your agent needs. The table below lists every tool in the latest published version and updates when a new version is published.

How it works

1

Open credentials in Guild

Go to Access & setup > Credentials in your Guild account or organization. Click Connect and search for pagerduty-openapi.
2

Paste your API key

Paste your PagerDuty REST API key into the API Key field. Guild sends it as Authorization: Token token=<key> on every request.
3

Import tools into your agent

Import PagerdutyOpenapiTools from @guildai-services/guildai~pagerduty-openapi and spread it into your agent’s tools object. See Tool sets for how to select a subset with pick().

Why PagerDuty access needs governing

PagerDuty tools can create and resolve incidents, modify escalation policies, add or remove users, and publish status page posts. A credential scoped to the account grants those abilities to every agent in every workspace by default. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild, limiting specific agents or workspaces to only the operations they require. Credentials can be scoped to a single workspace, a single member, or a single agent, so a staging workspace never shares the same key as production. See Credentials for the full scoping model. The credential proxy injects the API key server-side after the policy check passes, so agent code never sees the secret. Agents that have not been granted access are denied at the proxy, not at PagerDuty.

About the PagerDuty integration

Agents can create, update, and resolve incidents, manage on-call schedules and escalation policies, and configure services and event orchestrations. They can also handle automation actions, status page posts, and team or user management. All actions use the PagerDuty REST API authenticated with a REST API key. The integration is guildai~pagerduty-openapi.

Authentication

  • Type: API key
  • Header: Guild sends the key as Authorization: Token token=<key>

Setup

1

Connect PagerDuty

In Guild, go to Access & setup > Credentials, click Connect, select pagerduty-openapi, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the pagerduty_openapi_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~pagerduty-openapi:

Frequently asked questions

No. The catalog entry for guildai~pagerduty-openapi lists no webhook events, so the integration does not receive inbound events from PagerDuty. Agents can only call outbound PagerDuty REST API tools.
Write a DENY rule in the credential policy for that agent targeting the relevant operation, such as pagerduty_openapi_resolve_incident. Guild’s credential proxy enforces the rule before the request reaches PagerDuty. See Credential policies for rule syntax.
Yes. Connect a workspace-scoped credential in each workspace pointing to the account you want. Guild resolves credentials in order, and a workspace credential takes precedence over the account default. See Credentials for the full resolution order.
Use pick() from the Guild Agent SDK to select specific tools by name from PagerdutyOpenapiTools. All tools carry the pagerduty_openapi_ prefix. See Tool sets for usage examples.

Put a governed agent on PagerDuty this week

Book a demo

See how teams govern agents that use PagerDuty.

Talk to sales

Get access to Guild, then connect PagerDuty to your first agent.
Also runs on Guild: AWS CloudWatch · Datadog · Google Logging · New Relic Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026