Connect Hume AI and Sorry

Both apps 34Hume AI 17Sorry 17

• Trigger
  Chat ended (instant)

  Fires when an EVI chat session ends (chat_ended webhook event).

• Trigger
  Chat started (instant)

  Fires when a new EVI chat session begins (chat_started webhook event).

• Trigger
  New Voice

  Triggers when a new voice is created.

• Trigger
  Tool call (instant)

  Fires when EVI calls a registered tool during a conversation (tool_call webhook event).

• Action
  Add config

  Create a new EVI configuration (voice assistant setup).

• Action
  Add prompt

  Create a new system prompt for use in an EVI configuration.

• Action
  Add tool

  Create a new tool definition that EVI can call during a conversation.

• Action
  Add voice

  Save a new custom voice to the account from a TTS generation ID, for reuse in later speech requests.

• Action
  Convert voice

  Convert the speech in an uploaded audio file into a different saved voice.

• Action
  Delete config

  Delete an EVI configuration from the account.

• Action
  Delete voice

  Delete a saved custom voice from the account.

• Action
  Generate Text to Speech

  Convert text to speech using Hume AI's expressive text-to-speech technology.

• Action
  List configs

  List the EVI configurations saved to the account.

• Action
  List prompts

  List the prompts saved to the account.

• Action
  List tools

  List the tool definitions saved to the account.

• Action
  List voices

  List the custom voices saved to the account.

• Action
  Update config

  Update an EVI configuration's name or description.

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