Connect Sorry and Wachete

Both apps 25Sorry 16Wachete 9

• Trigger
  New notice

  Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

• Action
  Add component

  Creates a new component on a Sorry status page, optionally nested under a parent component.

• Action
  Add notice

  Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

• Action
  Add notice update

  Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

• Action
  Add subscriber

  Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

• Action
  Delete notice

  Deletes a notice (incident, maintenance or general) from a Sorry status page.

• Action
  Delete subscriber

  Permanently removes a subscriber from a status page.

• Action
  Get notice

  Returns a single notice from a status page, including its type, state, subject, synopsis and link.

• Action
  Get status page

  Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

• Action
  List components

  Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

• Action
  List notices

  Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

• Action
  List notice updates

  Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

• Action
  List status pages

  Returns all status pages in your Sorry account, optionally filtered by name or creation date.

• Action
  List subscribers

  Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

• Action
  Update component

  Updates a component on a Sorry status page, such as its name, description, position or parent component.

• Action
  Update notice

  Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

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