Connect PagerDuty to Xitoring

Both apps 44PagerDuty 28Xitoring 16

• Trigger
  List Maintenance Windows

  Gets a list of maintenance windows (GET /maintenance_windows).

• Trigger
  New Incidents

  Polls for new incidents in PagerDuty (GET /incidents, newest first).

• Action
  Add Responders

  Request additional responders (a user or escalation policy) to help with an incident.

• Action
  Add Team Member

  Add a user to a team with a given role.

• Action
  Create Incident

  Creates an incident in PagerDuty (POST /incidents).

• Action
  Create Note on Incident

  Creates a note on a given incident.

• Action
  Delete or End a Maintenance Window

  Deletes a maintenance window that hasn't started yet, or ends one that is ongoing.

• Action
  Get Escalation Policy

  Retrieve a single escalation policy by its ID.

• Action
  Get Incident

  Retrieve a single PagerDuty incident by id.

• Action
  Get Schedule

  Retrieve a single on-call schedule by its ID.

• Action
  Get Service

  Retrieve a single PagerDuty service by id.

• Action
  Get Team

  Retrieve a single team by its ID.

• Action
  Get User Information

  Gets a user's information based on provided ID.

• Action
  List Escalation Policies

  List PagerDuty escalation policies (GET /escalation_policies).

• Action
  List Incident Notes

  List all notes attached to an incident.

• Action
  List Incidents

  List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range) (GET /incidents).

• Action
  List On-Calls

  List current on-call entries — who is on call now, by escalation policy/schedule/user/time window (GET /oncalls).

• Action
  List Schedule Overrides

  List overrides on a schedule within a required since/until time window.

• Action
  List Schedules

  List PagerDuty on-call schedules (GET /schedules).

• Action
  List Services

  List PagerDuty services (GET /services).

• Action
  List Teams

  List all teams in the account.

• Action
  List Users

  List PagerDuty users (GET /users).

• Action
  Manage Incidents

  Bulk acknowledge or resolve multiple incidents in a single call.

• Action
  Snooze Incident

  Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.

• Action
  Two-way sync add a maintenance window

  Creates a maintenance window for use with two-way sync triggers (POST /maintenance_windows). Does not update. Use only with two-way sync triggers.

• Action
  Two-way sync add or update an incident

  Creates or updates an incident for use with two-way sync triggers (POST /incidents; incident_key dedups). Use only with two-way sync triggers.

• Action
  Update Incident

  Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.

• Action
  Update Maintenance Window

  Updates a maintenance window.

• Action
  Add check

  Create a new uptime/website/server check. POST /api/v2/check

• Action
  Add group

  Store a new check/server group. POST /api/v2/groups

• Action
  Add heartbeat

  Create a new heartbeat check. POST /api/v2/heartbeat/add

• Action
  Add maintenance schedule

  Create a new maintenance window. POST /api/v2/maintenance-schedules/add

• Action
  Add ticket

  Create a new support ticket. POST /api/v2/tickets

• Action
  Delete check

  Delete a check. DELETE /api/v2/checks/{id}

• Action
  Delete server

  Remove a server from monitoring. DELETE /api/v2/servers/{id}

• Action
  Get check

  Retrieve a single check by id. GET /api/v2/check/{id}

• Action
  Get incident

  Get a single incident's data. GET /api/v2/incidents/{id}

• Action
  Get server

  Retrieve a single server by id. GET /api/v2/servers/{id}

• Action
  List checks

  List all checks. GET /api/v2/check/

• Action
  List groups

  List all groups. GET /api/v2/groups

• Action
  List maintenance schedules

  List maintenance schedules. GET /api/v2/maintenance-schedules

• Action
  List servers

  List all monitored servers. GET /api/v2/servers

• Action
  Resolve incident

  Resolve an open incident. POST /api/v2/incidents/{id}/resolve

• Action
  Update check

  Update an existing check. PUT /api/v2/check/{id}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.