PagerDuty

Infrastructure

Neotask turns PagerDuty into an autonomous incident command center — manage incidents, schedules, escalation policies, and status pages through OpenClaw agents.

What You Can Do

With 68 actions, PagerDuty is one of the deepest integrations available. Here is how the capabilities break down:

| Area | What You Can Do |

|------|----------------|

| Incidents | Create, list, get, manage, add notes, add responders, find related/past/outlier incidents, list alerts |

| Incident Workflows | List, get, and start automated incident workflows |

| Schedules | List, get, create, update schedules; list schedule users; create overrides |

| Escalation Policies | List and get escalation policies |

| Services | List, get, create, and update services |

| Event Orchestration | List, get, update routers; append rules; inspect global and service-level orchestrations |

| Alert Grouping | Create, list, get, update, and delete alert grouping settings |

| Change Events | List and get change events; list by incident or service |

| Status Pages | List status pages; create and update posts; list impacts, severities, and statuses |

| Teams | List, get, create, update, delete teams; add/remove members |

| On-Call | List on-call schedules and users |

| Logs | List and get log entries |

| Users | List users and get user data |

Every action runs autonomously or requires your approval — you decide.

Try Asking

  • "Create a P1 incident for the checkout service with title 'Payment gateway timeout'"
  • "Who is on-call for the platform team right now?"
  • "Add a note to incident 4521 saying the root cause was a misconfigured DNS record"
  • "Show me all open incidents from the last 24 hours"
  • "Create a schedule override for Maria to cover tonight's on-call shift"
  • "Start the 'Major Incident Response' workflow for incident 8832"
  • "Post a status page update saying payments are restored"
  • "What escalation policy is assigned to the API service?"

    • Pro Tips

  • Use incident workflows to trigger standardized response playbooks — agents can start them automatically when specific conditions are met.
  • Schedule on-call roster reviews weekly so agents flag gaps or overloaded team members before they become problems.
  • Combine PagerDuty with your monitoring tool in an app group so agents can correlate alerts with metric spikes in one conversation.
  • Event orchestration rules let you route and transform alerts before they page anyone — manage these conversationally instead of clicking through the UI.
  • Approval gates on incident creation prevent accidental P1 declarations — useful when agents are processing automated alert data.
  • Multi-agent teams can handle incident response across multiple services simultaneously during major outages.

    • Works Well With