Connect Sorry and Vyte

Both apps 33Sorry 17Vyte 16

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

• Action
  Update status page

  Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

• Trigger
  Event Cancelled

  Triggers when an event is cancelled.

• Trigger
  Event Confirmed

  Triggers when an event is confirmed.

• Trigger
  Event Created

  Fires when a Vyte event is created (including events created already confirmed).

• Action
  Add appointment type

  Create a new appointment type on a Vyteme booking page.

• Action
  Add invitee

  Add one or more invitees to an existing event.

• Action
  Add user

  Creates a user in your Vyte organization.

• Action
  Cancel Event

  Cancels a Vyte event. Vyte has no delete for events; cancelling is how an event is removed from scheduling.

• Action
  Confirm Event

  Confirms a Vyte event on a chosen date and place.

• Action
  Create Event

  Creates an event

• Action
  Delete user

  Removes a user from your Vyte organization so you are no longer billed for them. This does not delete the person's Vyte account.

• Action
  Find available slots by user

  Returns the free time slots at which the specified Vyte users (by email or user id) or team are all available, for a given appointment duration and date range.

• Action
  Get Event

  Retrieve a single Vyte event by its id.

• Action
  List Users

  Lists all users linked to your Vyte organization.

• Action
  Update appointment type

  Update an existing appointment type's settings.

• Action
  Update Event

  Updates an existing Vyte event's title, proposed dates or proposed places.

• Action
  Update user

  Update a user's profile (name, timezone, language, etc).

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