The PagerDuty node lets your agents trigger, acknowledge, and resolve incidents, and find who’s on call.
Standard OAuth. No special setup required.
| Tool | Description |
|---|
create_incident | Create a new incident |
get_incident | Get incident details |
list_incidents | List incidents with filters |
manage_incidents | Update status, urgency, or assignments |
add_note_to_incident | Add a note to an incident |
add_responders | Add responders to an incident |
get_related_incidents | Find related incidents |
get_past_incidents | Retrieve similar past incidents |
| Tool | Description |
|---|
list_oncalls | List who’s on call |
list_schedules | List all schedules |
get_schedule | Get schedule details |
create_schedule_override | Create a schedule override |
| Tool | Description |
|---|
list_services | List all services |
get_service | Get service details |
list_escalation_policies | List escalation policies |
| Tool | Description |
|---|
list_event_orchestrations | List orchestration rules |
get_event_orchestration_router | Get routing config |
| Tool | Description |
|---|
list_teams | List all teams |
list_users | List all users |
get_user_data | Get current user info |
| Tool | Description |
|---|
create_status_page_post | Create a status page post |
list_status_pages | List all status pages |
- Find Oncall User is useful for agents that need to route alerts or escalations to the right person.
- Trigger Incident requires a service ID — this loads dynamically from your PagerDuty account.
