• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

Pagerduty

Pagerduty MCP integration

Reports who is on call, opens incidents and posts status updates, merges duplicates, and pages responders through a response play.

Connect PagerdutySee all integrations

363actions available

  1. Home/
  2. Integrations/
  3. Pagerduty

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.

  • schedule

    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
  • notifications

    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
  • checklist

    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
  • group

    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.

  1. 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.

  2. 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.

  3. 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

What can you do in Pagerduty without me setting anything up?

These, right away:

  • Add service to incident workflow trigger
  • Fetch cache variable for event orchestration
  • Delete account subscription by ID

Great, let's start with the first one.

Ask Lyro anything...

FAQ

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.

  • 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.

  • 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.

  • 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.

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.

  • Appcirclearrow_outward

    Appcircle

    Triggers builds through Git webhooks, reports what shipped and to whom, and serves Enterprise App Store in-app updates.

  • Cloudflarearrow_outward

    Cloudflare

    Finds, creates, and updates DNS records, reports a zone's firewall and bot settings, and maps tunnels, pools, and account roles.

  • Dopplerarrow_outward

    Doppler

    Reads secret values from the right config, generates end-to-end encrypted share links, rotates and annotates values, and answers who changed what.

  • Jumpcloudarrow_outward

    Jumpcloud

    Validates API credentials, returns the real device-enrollment steps with Connect key guidance, and permanently removes a custom role by ID.

  • Railwayarrow_outward

    Railway

    Pulls the runtime logs behind a failing deploy, reports environment status, changes build and deploy settings, and audits tokens and integrations.

  • Svixarrow_outward

    Svix

    Traces a webhook through its delivery attempts, registers applications and endpoints, replays what failed, and rotates endpoint signing secrets.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect Pagerduty?

Authorize the account and your agent has all 363 actions from the first conversation.

Connect PagerdutyTalk to sales
Connect PagerdutyTalk to sales
Support agent working at a laptop next to the Lyro mascot