Connect Sally and Sorry

Both apps 35Sally 18Sorry 17

• Trigger
  New Recording

  Triggers when a new recording appears in a Sally directory.

• Trigger
  New Summary for Appointment Created

  Triggers when Sally finishes a new meeting summary.

• Trigger
  New Task

  Triggers when a new task is created in a Sally directory.

• Action
  Create Recording from URL

  Creates a Sally recording from an audio or video file URL and starts transcription.

• Action
  Create Tag

  Creates a tag in the Sally tag catalog (admins and owners only).

• Action
  Create Task

  Creates a task in Sally.

• Action
  Create Vocabulary Entry

  Adds a vocabulary phrase that improves Sally transcription.

• Action
  Delete Task

  Deletes a Sally task.

• Action
  Find Summaries

  Searches Sally recording summaries by words in their content.

• Action
  Find Tasks

  Searches Sally tasks by text.

• Action
  Get Recording

  Returns one Sally recording by id.

• Action
  Get Recording Transcript

  Returns the transcript of a Sally recording with its time-coded segments and speakers.

• Action
  Get Summary

  Returns one Sally recording summary with its sections.

• Action
  Get Task

  Returns one Sally task by id.

• Action
  List Directories

  Returns the Sally company accounts (directories) your token can access.

• Action
  List Recording Summaries

  Returns the AI summaries of a Sally recording, one per language.

• Action
  Toggle Task Done

  Marks a Sally task done, or reopens it.

• Action
  Update Task

  Updates the fields you supply on a Sally task.

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

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