Connect PagerDuty and Wachete

Both apps 37PagerDuty 28Wachete 9

• Trigger
  List Maintenance Windows

  Gets a list of maintenance windows.

• Trigger
  New Incidents

  Polls for new incidents in PagerDuty.

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

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

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

• Action
  List On-Calls

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

• Action
  List Schedule Overrides

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

• Action
  List Schedules

  List PagerDuty on-call schedules.

• Action
  List Services

  List PagerDuty services.

• Action
  List Teams

  List all teams in the account.

• Action
  List Users

  List PagerDuty 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. 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. 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.

• Trigger
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

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