Connect Roam and Sorry

Both apps 29Roam 12Sorry 17

• Trigger
  Lobby Booked

  Triggers when a lobby is booked.

• Trigger
  New Recording

  Triggers when a new meeting recording is saved in your Roam.

• Trigger
  New Transcript

  Triggers when a new transcript is saved in your Roam.

• Trigger
  On-Air: Event Created

  Triggers when a new On-Air event is created.

• Trigger
  On-Air: Guest Added

  Triggers when a guest is added to an On-Air event.

• Trigger
  On-Air: Guest RSVP Changed

  Triggers when a guest changes their RSVP status on an On-Air event.

• Action
  Create Meeting Link

  Creates a new Roam meeting link and returns its ID and shareable URL. Optionally set the host's email and the meeting's start and end times.

• Action
  Find User by Email

  Looks up a member of your Roam organization by their email address and returns their profile, including user ID, name, photo and admin status.

• Action
  On-Air: Add Guest

  Adds a guest to a Roam On-Air event by email, optionally setting their name, phone and RSVP status, and returns the created guest.

• Action
  On-Air: Find Event

  Returns the On-Air events whose title contains the text you search for, taken from your most recent events. Returns an empty list when nothing matches.

• Action
  Send Channel Message

  Posts a message to a Roam channel and returns the message's timestamp, which you can reuse to reply in the same thread.

• Action
  Send Direct Message

  Sends a direct message to one person in Roam and returns the conversation ID plus the message's timestamp, which you can reuse to reply in the same thread.

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