List open PagerDuty incidents by priority
See the open incidents right now, with priority, service, time open and who has each one, so you know where to start.
Ask “What’s open, and who is on call tonight?” Manus lists open PagerDuty incidents by priority, service and time open, plus who is on call for each. Open one to see its alerts, notes, recent changes and similar past incidents in one timeline. It also drafts status page updates, on-call handoff notes and postmortems. Ask it to list changes first, and it waits for your OK.
Manus lists open PagerDuty incidents by priority, service and time open, so PagerDuty incident management starts from one list. Pick one, and it lines up the alerts, notes, change events and similar past incidents in order.
See the open incidents right now, with priority, service, time open and who has each one, so you know where to start.
Get the alerts, notes and change events for one incident in order, with what changed right before it started.
See how a similar incident was fixed last time and how long it took.
Ask who is on call tonight, who takes over next or who covers each day this week. For PagerDuty on-call management, Manus also drafts schedule overrides when someone is out. Ask to see them first, and it waits for your OK.
Get tonight’s on-call person for each service, when their shift ends and who takes over next.
See who covers each day on a schedule, and spot any hours when nobody is on call.
When someone is out, Manus drafts the override for the right hours. Ask to see it first, and it waits for your OK.
Tell Manus what to add: a note, a responder, an incident workflow or a status page update. Ask it to list the changes first, and it waits for your OK before anything is added or posted.
Say what to add, and Manus lists the note and the person it will page. Ask to see them first, and it waits for your OK.
See which incident workflows you can start for an incident. Ask it to suggest one first, and it waits for your OK before starting it.
Get the update in plain words: what customers notice, what you’re doing and when the next update comes.
PagerDuty on-call handoff notifications tell you when a shift starts or ends. Manus writes what to pass on: what was handled, what’s still open and what the next person should know.
Before you go on call, get a shift handoff summary: what the last shift handled, what’s still open and the notes left on each incident.
Set it up once as an automation and get last week’s incident count, average time to resolve and the services with the most incidents.
See how automations workManus drafts the postmortem from the incident’s timeline and notes, then lists the follow-ups for Linear or GitHub. Ask to see them first, and it waits for your OK before filing anything.
Start from your team’s template or the PagerDuty postmortem template, and Manus fills in the summary, impact, timeline and follow-ups.
Get one Linear issue per follow-up, with a link back to the incident. Ask to see the list first, and it waits for your OK.
See the Linear connectorGet a GitHub issue with what broke, how to test the fix and a link to the PagerDuty incident.
See the GitHub connectorPagerDuty is already in Manus Connectors. Connect your account once, and any task can work with the incidents, schedules and services you have access to.
In Manus, open Connectors, choose PagerDuty and select Connect.
Follow the steps to connect your account. Manus then works with the incidents, schedules and services your PagerDuty account can already use.
Mention PagerDuty and the incident, service or schedule. Before any change, ask Manus to list what it will change and wait for your OK.
Open Connectors in Manus, choose PagerDuty and select Connect. Follow the steps to connect your PagerDuty account. After that, mention PagerDuty in any task, for example “Which incidents are open right now, and who is on call?”
No. Manus changes things in PagerDuty only when you ask. Ask it to show the change first, and it waits for your OK before it adds a note, adds a responder, starts a workflow, changes a schedule or posts a status update. Every example on this page does this.
Yes. Ask it to look things up or write drafts, and it won’t change anything in PagerDuty. It can only do what your PagerDuty account is allowed to do, so if you connect an account whose role can only view, it stays read-only.
Manus works with what your PagerDuty account can see and change. To add notes, responders, schedule overrides or status updates, your PagerDuty role needs permission for those actions. PagerDuty’s own MCP setup guide also asks for an account with Advanced Permissions.
It can build the incident’s timeline, find similar past incidents, check who is on call and draft the status page update while you work on the fix. It doesn’t answer pages or calls for you, and it doesn’t replace PagerDuty notifications.
No. AIOps, the AI agents and other PagerDuty AI features are PagerDuty’s own, and you use them inside PagerDuty. Manus works with your PagerDuty data through the connector and carries an incident into status updates, postmortems or tasks, together with work in the other tools you’ve connected.
Both use MCP. A PagerDuty Claude integration connects Claude to PagerDuty’s MCP server, and PagerDuty in Manus is an MCP connector too. Connect it once in Manus Connectors, and any task can use it alongside the other tools you’ve connected.
No. Your PagerDuty integration with Datadog still sends alerts, and the one with Slack still posts to your channels. If you’ve also connected Slack or Datadog in Manus, one task can read a PagerDuty incident, check the related Datadog monitor and draft a Slack update for your OK.
Yes. Ask once and say when to run it, for example every Monday at 9 AM. Manus runs it as an automation, and each time you get last week’s incident count, average time to resolve and the services with the most incidents.
No. PagerDuty is already in Manus Connectors, so there are no PagerDuty MCP tools to install. Connect your account once and ask for what you need in plain words.