Connect Statuspage and Wachete

Both apps 27Statuspage 18Wachete 9

• Trigger
  New incident

  Polling trigger for new incidents.

• Action
  Add component

  Create a component.

• Action
  Add incident

  Create an incident (realtime/scheduled).

• Action
  Add metric data

  Add data points to a metric.

• Action
  Add subscriber

  Create a subscriber.

• Action
  Delete component

  Delete a component.

• Action
  Delete incident

  Delete an incident.

• Action
  Delete subscriber

  Unsubscribe/delete a subscriber.

• Action
  Get component

  Get a component.

• Action
  Get incident

  Get an incident by id.

• Action
  Get metric

  returns one metric including most_recent_data_at and backfilled.

• Action
  List components

  List components.

• Action
  List incidents

  List incidents for a page.

• Action
  List pages

  List status pages.

• Action
  List subscribers

  List subscribers.

• Action
  List unresolved incidents

  List unresolved incidents.

• Action
  Update component

  Update a component (e.g. status).

• Action
  Update incident

  Update an incident (status, message, components).

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