What PagerDuty access does the connected account need?

It follows the actions you want in reach. Retrieve oncall list, Get schedules, and Fetch incident list are read-only calls. Create incident record, Post incident status update, and Create schedule overrides configuration write to PagerDuty, so a read-scoped connection will not be able to make them.

Can Lyro arrange an on-call override?

Yes. Create schedule overrides configuration puts a replacement on the schedule, Preview schedule object shows what the rota looks like before the change is committed, and Delete schedule override by id removes it again once cover is no longer needed.

What does Lyro do when the same incident is reported twice?

Fetch related incidents by id surfaces what is already open against that service, and Merge source incidents into target incident folds the second report into the first so the timeline and the responders stay on one record. Snooze incident by duration handles a repeat alert that does not warrant its own incident.

How is this different from a PagerDuty webhook or a Zapier trigger?

A webhook fires one predefined step when a matching event arrives. Lyro decides which PagerDuty calls to make while the report is being described to it - checking who is on call, opening the incident, merging it into an existing one, or paging a responder - and can do several of those in one exchange.

PagerDuty Integration - Lyro AI Agent

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Fetch user contact method
Lyro retrieves contact methods for a PagerDuty user to reach them during an incident. Teams reach the right person immediately instead of searching contact lists.
Update change event by ID
Lyro updates an existing change event in PagerDuty to reflect completed actions or status changes. Teams keep incident records current without manual PagerDuty navigation.
Add service to incident workflow trigger
Lyro adds a service to an incident workflow trigger so that service's incidents automatically invoke the workflow. Teams ensure critical services follow response procedures without manual setup on each incident.

See all 363 actions

How businesses use Pagerduty + Lyro

Each card is one request a support team gets, and the Pagerduty actions Lyro runs to close it.

Say who is on call right now
Lyro reads the live on-call list and the schedule behind it, so the question of who to wake up is answered from PagerDuty rather than from a rota someone pasted into a channel last quarter.
Retrieve Oncall ListGet SchedulesRetrieve Schedule By ID
Open an incident from a report
Lyro files the incident against the right service, attaches the reporter's own account of what happened as a note, and posts the first status update so subscribers are informed immediately.
Create Incident RecordPost Incident NotePost Incident Status Update
Keep one incident, not five
Lyro checks what is already open for the same service, folds duplicate reports into the incident of record, and snoozes the noise, so responders see one thread instead of a pile.
Fetch Related IncidentsMerge Source IncidentsSnooze Incident By Duration
Pull in the right responder
Lyro runs the response play attached to the service, requests the specific responders it names, and puts a schedule override in place when the person on call cannot take it.
Execute Response PlaySend Responder RequestsCreate Schedule Override

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Pagerduty actions it has and picks the ones a request needs.

01
Connect Pagerduty
Authorize the Pagerduty account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Pagerduty actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Pagerduty · Lyro

Everything else about Pagerduty

Setup, permissions, and the limits of what Lyro can do inside Pagerduty.

It follows the actions you want in reach. Retrieve oncall list, Get schedules, and Fetch incident list are read-only calls. Create incident record, Post incident status update, and Create schedule overrides configuration write to PagerDuty, so a read-scoped connection will not be able to make them.

Every action available in Pagerduty

All 363 actions your agent can call on Pagerduty, straight from the live MCP connection.

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
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty.
Aggregate incident metrics with filters
Retrieves and aggregates metrics for incidents across all services in 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
This endpoint associates a specific team with an automation action in PagerDuty.
Audit escalation policy records
Retrieves the audit records for a specific escalation policy in PagerDuty.
Convert service rule by ID
Converts a service's Event Rules to Event Orchestration rules.
Count paused incident reports
Retrieves the count of paused incident reports in the PagerDuty system.
Create a custom field for an incident type
Create a Custom Field for an Incident Type.
Create a field option for a custom field
Creates a new field option for a custom field on an incident type.
Create and manage custom incident fields
Creates a new custom field for incidents in PagerDuty.
Create an incident type
Create a new incident type.
Create a ruleset
Creates a new Ruleset in PagerDuty for managing incident routing and notification rules.
Create incident workflow trigger
Creates a new incident workflow trigger in PagerDuty.
Create automation runner endpoint
Creates a new Runbook Automation runner in PagerDuty's Automation Actions.
Create business service
This endpoint creates a new Business Service in PagerDuty, which represents a specific service or application that can be monitored and managed within the incident management platform.
Create escalation policy
Creates a new escalation policy in PagerDuty, defining how incidents are escalated to different responders or teams.
Create event orchestration
Creates a new Event Orchestration in PagerDuty, which defines how incoming events are processed and routed to appropriate services.
Create event rule in ruleset
Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system.
Create extension object
Creates a new extension in PagerDuty, allowing for additional functionality or integrations to be added to your services.
Create handoff notification rule
Creates a new on-call handoff notification rule for a specific user in PagerDuty.
Create incident field option
Creates a new field option for a specific custom field in PagerDuty's incident management system.
Create incident record
Creates a new incident in PagerDuty with specified details and assignments.
Create incident workflow
This endpoint creates a new Incident Workflow in PagerDuty, allowing users to define a series of automated steps to be executed during incident response.
Create incident workflow instance
Creates a new instance of an incident workflow for a specific incident in PagerDuty.
Create integration for orchestration
Creates a new integration for an existing event orchestration in PagerDuty.
Create integration for service
Creates a new integration for a PagerDuty service to enable incident creation from external monitoring tools and systems.
Create maintenance window object
Creates a new maintenance window in PagerDuty, allowing you to schedule periods of planned maintenance for specific services.
Create new schedule layer
Creates a new on-call schedule in PagerDuty with one or more rotation layers.
Create new service
Creates a new service in PagerDuty, which is a key component for managing incidents and alerts.

The tools Pagerduty sits next to

Same connection, same setup. Pick the next one your team already uses.

Browse every integration

Pagerduty MCP integration

Three actions you can hand over today

Fetch user contact method

Update change event by ID

Add service to incident workflow trigger

How businesses use Pagerduty + Lyro

Say who is on call right now

Open an incident from a report

Keep one incident, not five

Pull in the right responder

Get started in 3 steps

Connect Pagerduty

Tell your agent what you need

Watch it work

Everything else about Pagerduty

Every action available in Pagerduty

Add service to incident workflow trigger

Aggregate escalation policy incident metrics

Aggregate incident metrics with filters

Associate service dependencies

Associate team with automation action

Audit escalation policy records

Convert service rule by ID

Count paused incident reports

Create a custom field for an incident type

Create a field option for a custom field

Create and manage custom incident fields

Create an incident type

Create a ruleset

Create incident workflow trigger

Create automation runner endpoint

Create business service

Create escalation policy

Create event orchestration

Create event rule in ruleset

Create extension object

Create handoff notification rule

Create incident field option

Create incident record

Create incident workflow

Create incident workflow instance

Create integration for orchestration

Create integration for service

Create maintenance window object

Create new schedule layer

Create new service

The tools Pagerduty sits next to

Appcircle

Cloudflare

Doppler

Jumpcloud

Railway

Svix

Ready to connect Pagerduty?